Capability-aware design
Browser Compatibility
How FictionTools adapts to browser support for direct file saving, automatic backup folders and local browser recovery.
Core project work
Creating and editing projects, local browser recovery, reports, project settings, open-file uploads and downloadable project copies are designed to work broadly in current desktop browsers with JavaScript and local browser storage enabled.
Browser capability summary
| Capability | When supported | Fallback when unavailable |
|---|---|---|
| Direct Save / Save As | FictionTools can receive a writable handle to a file the author selects. | FictionTools downloads an updated project copy; the browser controls the destination. |
| Chosen backup folder | FictionTools can create separate AutoBackups and ManualBackups subfolders after permission is granted. | No unattended folder AutoBackups. Manual backups are downloads. |
| Browser recovery | Uses local browser storage and is separate from the folder-picker capability. | |
Firefox
Firefox currently does not expose showSaveFilePicker(), showOpenFilePicker() or showDirectoryPicker() to websites. FictionTools therefore uses its fallback workflow in Firefox.
- Browser recovery: available when local browser storage is available.
- Open project: uses the normal file-upload chooser.
- Save project: downloads an updated project copy rather than writing directly back to the prior file.
- Automatic folder backups: unavailable because FictionTools cannot be granted a chosen directory.
- Manual backups: available as downloads. Firefox controls where the downloaded file is saved.
The workspace labels these controls explicitly—for example, Download Manual Backup—so an author is not left thinking a separate backup folder was used.
Edge, Chrome and other browsers with the required picker APIs
Where the required file-system picker features are present, FictionTools can offer direct user-selected Save As and a user-granted backup root containing separate AutoBackups and ManualBackups folders. Permission can still be revoked by the browser or operating system, so the workspace checks access rather than assuming it remains available forever.
Download location is a browser setting
When FictionTools falls back to a download, the website cannot choose a different destination on its own. The browser may save to its configured Downloads folder or may ask where to save, depending on the author’s browser settings.
Browser recovery
FictionTools uses IndexedDB for local recovery storage. Private/incognito modes, aggressive privacy settings, storage quotas, profile removal or cleanup tools may limit or erase local recovery data. Browser recovery is a safety layer, not a permanent archive.
What should I do if a feature is unavailable?
Keep using browser recovery and create frequent manual backup downloads. Move important downloaded backups into a deliberate long-term folder as part of your normal file-management routine. If automatic folder backups are important, use a browser/device combination that exposes the required directory-picker capability.
Mobile devices
The interface is responsive, but long-running fiction projects, file organization and backup-folder workflows are generally easier on a desktop or laptop. Mobile browsers may impose stricter file-access and storage limits.