
Krita Incremental Backup copies the previously saved disk state into the numbered backup, then saves your current work under the original filename. Incremental Version instead saves the current document as a new numbered file. An older-looking backup can therefore be the expected result of the command you chose.
Key Takeaways
- Incremental Backup preserves the state that was already on disk.
- Incremental Version makes a new numbered file from the current working state.
- Inspect the actual checkpoint contents instead of treating the highest number as proof of the newest edit.
Identify the state you intended to preserve
Suppose a portrait composition was saved with a blue background. You change it to green, then use Incremental Backup before preparing a second creative direction. The new backup can contain the blue version while the original filename now contains green.
That does not by itself indicate a failed save. It follows the order described in the Krita saving and backup manual: copy the last saved file first, then save the image under its current name.
Before choosing a command, decide whether the checkpoint should represent the earlier approved state or the current unsaved revision.
Match the command to the checkpoint
| Desired record | Relevant behavior |
|---|---|
| Preserve the previous saved state before updating the working file | Incremental Backup |
| Save the current state as a new numbered working file | Incremental Version |
| Keep only a normal working save | Save, with its separate configured backup behavior |
For the hypothetical green revision, use Incremental Version when you need a numbered file that contains green as the current checkpoint. Keep the existing files rather than deleting one because its appearance seems older than expected.
After any versioning action, note the open document's name and the role of the resulting file. A short note such as “approved blue” or “current green proposal” is more useful than an unexplained numeric suffix.
Verify the checkpoint without overwriting it
Open the intended checkpoint separately and inspect a distinctive recent revision. In this example, compare the background color and one other edited element. Do not verify by repeatedly saving over the checkpoint you are trying to inspect.
Accept the arrangement when the current proposal and the earlier recoverable state can both be identified and opened. Keep the source structure needed for revisions, as discussed in the editable-master handoff guide.
This disk-file behavior differs from the Krita cumulative-Undo mechanism, which groups editing steps within a session. Neither a long Undo list nor a high backup number establishes which saved file contains the revision you plan to deliver.
Related tasks
- Why Krita Groups Brush Strokes, and How to Control Undo Batches
- Why Can I Edit My Saved Layers but Not Undo Yesterday’s Steps?
- What Is the Difference Between an Editable Artwork Master and a Flat PNG?
Sources and scope
- Saving, AutoSave and Backup Files: Incremental Backup copies the last saved disk file to a numbered backup and saves current work under the original filename. Incremental Version saves the current document under a new numbered filename while leaving existing files alone.
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.