Author continuity guide
Backing Up a Local Fiction Project
Store a visible project file, keep dated copies and understand the limits of synchronization.
By Nathan Ardwell · author-planning perspective
Use more than one protection layer
FictionTools v2 separates the primary project file, browser recovery, rolling AutoBackups and deliberate ManualBackups. They solve different problems and should not be treated as interchangeable.
Choose a visible primary file
Use Save As and put the main .fictionproject file in a folder you recognize and already protect. A Downloads or temporary folder may be convenient for a test but is a poor long-term home if you routinely clean it out.
Let AutoBackups catch ordinary mistakes
Where your browser permits folder access, select a backup root. FictionTools creates an AutoBackups subfolder and writes rolling copies after changed work. These are a short-term safety net; older automatic copies may be removed under your retention setting.
Create unlimited manual checkpoints
Manual backups are never automatically deleted by FictionTools. Make one before major timeline changes, renumbering, large continuity edits or a milestone such as completing a draft.
Keep backup locations independent when practical
A cloud-synchronized folder, external drive or another protected location can provide useful separation from the primary file. Remember that a synchronized folder is also subject to the security and deletion behaviour of that service.
Test restoration
Occasionally open a backup and confirm that the project loads. When restoring, prefer Save As to a new current filename until you have verified the recovered copy.