diff --git a/images/en/autosave_named_restore.png b/images/en/autosave_named_restore.png new file mode 100644 index 0000000000000000000000000000000000000000..0000000000000000000000000000000000000000 GIT binary patch literal 0 Hc$@` + + +AutoSave +-------- + +AutoSave is what happens when you've worked for a bit and not saved your work yourself: Krita will save your work for you. Autosave files are by default visible in your file manager. You can configure Krita 4.2 and up to create autosave files that are visible in your file manager. By default, Krita autosaves ever fifteen minutes; you can configure that in the File tab of the General Settings page of the Configure Krita dialog, which is in the Settings menu (Linux, Windows) or in the Application menu (macOS). + +.. image:: /images/en/file_config_page.png + +There are two possibilities: + +- You hadn't saved your work at all +- You had saved your work already + +AutoSave for Unsaved Files +~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In the first case, Krita will create an unnamed AutoSave file. + +If you're using Linux or macOS, the AutoSave file will be a hidden file in your home directory. If you're using Windows, the AutoSave file will be a file in your user's TEMP folder. In Krita 4.2 and up, you can configure Krita to make the AutoSave files visible by default. + +A hidden autosave file will be named like ''.krita-12549-document_1-autosave.kra'' + +If Krita crashes before you had saved your file, then the next time you start Krita, you will see the file in a dialog that shows up as soon as Krita starts. You can select to restore the files, or to delete them. + +.. image:: /images/en/autosave_unnamed_restore.png + +If Krita crashed, and you're on Windows and your TEMP folder gets cleared, you will have lost your work. Windows does not clear the TEMP folder by default, but you can enable this feature in Settings. Applications like Disk Cleanup or cCleaner will also clear the TEMP folder. Again, if Krita crashes, and you haven't saved your work, and you have something enabled that clear your TEMP folder, you will have lost your work. + +If Krita doesn't crash, and you close Krita without saving your work, Krita will remove the AutoSave file: you work will be gone and cannot be retrieved. + +If you save your work and continue, or close Krita and do save your work, the AutoSave file will be removed. + +AutoSave for Saved Files +~~~~~~~~~~~~~~~~~~~~~~~~ + +In the second case, Krita will create a named AutoSave file. + +A hidden named autosave file will look like ''.myimage.kra-autosave.kra''. + +By default, named AutoSave files are hiden. Named AutoSave files are placed in the same folder as the file you were working on. + +If you start Krita again after it crashed and try to open your original file, Krita will ask you whether to open the AutoSave file instead: + +.. image:: /images/en/autosave_named_restore.png + +If you choose "no", the AutoSave file will be removed. The work done since the last time you saved your file yourself is lost and cannot be retrieved. + +If you choose "yes", the AutoSave file will be opened, then removed. The file you have open will have the name of your original file. The file will be set to Modified, so the next time you try to close Krita, Krita will ask you whether you want to save the file. If you choose No, your work is irretrievably gone. It cannot be restored. + + +Backup Files +------------ + +There are three kinds of Backup files + +- Ordinary Backup files that are created when you save a file that have been opened from disk +- Incremental Backup files that copy the file as it is on disk to a numbered backup, and saves your file under the current name +- Incremental Version files that saves the file you are working on with a new number, leaving alone the files on disk. + + +Ordinary Backup Files +~~~~~~~~~~~~~~~~~~~~~ + +If you have opened a file, made changes, then save it, or save a new file after the first time you've saved it, Krita will save a backup of your file. + +You can disable this mechanism in the File tab of the General Settings page of the Configure Krita dialog, which is in the Settings menu (Linux, Windows) or in the Application menu (macOS). By default, Backup files are enabled. +you can configure the behavior of Backup files in the File tab of the General Settings page of the Configure Krita dialog, which is in the Settings menu (Linux, Windows) or in the Application menu (macOS). + +.. image:: /images/en/file_config_page.png + +By default, a Backup file will be in the same folder as your original file. You can also choose to save Backup files in the User folder or the TEMP folder; this is not as safe because if you edit two files with the same name in two different folders, their backups will overwrite each other. + +By default, a Backup file will have ''~'' as suffix, to distinguish it from an ordinary file. If you are using Windows, you will have to enable "show file extensions" in Windows Explorer to see the extension. + +.. image:: /images/en/file_and_backup_file.png + +If you want to open the Backup file, you will have to rename it in your file manager. Make sure the extension ends with ''.kra''. + +Every time you save your file, the last version without a ''~'' suffix will be copied to the version with the ''~'' suffix. The contents of the original file will be gone: it will not be possible to restore that version. + +Incremental Backup Files +~~~~~~~~~~~~~~~~~~~~~~~~ + +Incremental Backup files are similar to ordinary Backup files: the last saved state is copied to another file just before saving. However, instead of overwriting the Backup file, the Backup files are numbered: + +.. image:: /images/en/save_incremental_backup.png + +Use this when you want to keep various known good states of your image throughout your painting process. This takes more disk space, of course. + +Do not be confused: Krita does not save the current state of your work to the latest Incremental file, but copies the last saved file to the Backup file and then saves your image under the original filename. + +Incremental Version Files +~~~~~~~~~~~~~~~~~~~~~~~~~ + +Incremental Version works a bit like Incremental Backup, but it leaves the original files alone. Instead it will save a new file with a file number: + +.. image:: /images/en/save_incremental_version.png