
Do not expect Krita AutoSave to preserve work after you close normally without saving. The manual states that normal closure removes AutoSave files and unsaved work is lost. Save a real .kra master before stopping; AutoSave is a recovery aid, not a named revision you can assume will remain.
Key Takeaways
- A normal close without saving and a crash have different recovery behavior.
- AutoSave files are removed during normal closure.
- A recovered document still needs an intentional save to preserve the recovered work.
Check what exists before closing
Imagine finishing a portrait collage and seeing an AutoSave notification. You are about to discard changes because you assume that notification created a permanent alternate version. That assumption is the dangerous part: the notification does not establish a separately saved checkpoint.
The Krita Saving, AutoSave and Backup Files manual says Krita does not permanently store your images without your intervention. Save the working document in its native .kra format when its Krita features must remain available.
Check the actual filename and destination. If you have never deliberately saved the document, do so before closing rather than relying on an unnamed recovery file.
Separate normal closure from recovery
| Event | Documented consequence |
|---|---|
| Close normally without saving | Unsaved work is lost and AutoSave files are removed. |
| Crash with an unsaved document | Krita can offer recovery on the next start if the AutoSave remains. |
| Crash with a previously saved document | Opening the original can prompt for its AutoSave. |
| Accept recovered work but later discard it | The recovery is not a substitute for saving that work. |
These are documented lifecycle differences, not a promise that a particular missing file can be recovered now.
If Krita offers a recovery you need, inspect it and save the useful result deliberately. Use a distinct name where preserving the earlier saved state matters. Do not dismiss the recovery prompt on the assumption that you can retrieve the same temporary state indefinitely.
Establish a durable stopping point
Before ending the session, save the intended master and open that saved file independently when practical. Check a meaningful recent change, such as the revised crop or corrected title, rather than confirming only that a filename exists.
Keep that file's role separate from an exported proof. A proof can look correct without preserving the editable structure needed for tomorrow's revision.
Session Undo is another separate mechanism. The saved-structure versus Undo guide and Krita cumulative-Undo guide explain why visible history is not a durable saved-version plan. Accept the stopping point when the intended .kra contains the current work, rather than when AutoSave last displayed a notification.
Related tasks
- Does Deleting a Phone Photo Also Delete the iCloud Original?
- Why Can I Edit My Saved Layers but Not Undo Yesterday’s Steps?
- Why Krita Groups Brush Strokes, and How to Control Undo Batches
Sources and scope
- Saving, AutoSave and Backup Files: Normal closure removes Krita AutoSave files and closing without saving loses unsaved work. AutoSave recovery is offered after a crash; an accepted recovery still needs to be saved. Native .kra supports Krita features.
Official documentation synthesis; no hands-on test, search-volume or measured citation-rate claim. Scenarios and comparisons are proposed editorial examples, not reported experiments.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.