Cloud Backup

Your draft, backed up where you already work

Export is useful when you need a single file. Cloud backup keeps a living package of your manuscript, story bible, and outline outside Novilot, so a long novel is not trapped in one account.

What gets backed up

Each run pushes a structured package: chapter Markdown, story bible entries, outline cards, and project metadata. You can include a DOCX export for Dropbox when you want a Word-friendly copy alongside the Markdown tree.

Dropbox and GitHub

• Dropbox. Backups land under a Novilot Backups folder, with overwrite, timestamped, or keep-last retention you choose per project.
• GitHub. Install the Novilot GitHub App, grant only the repos you choose, and pick a private repo per novel. Each backup is a commit, so you get history without a separate versioning workflow.

Manual or scheduled

Run Backup now from Project Settings, or turn on a daily or weekly schedule. Unchanged manuscripts skip scheduled runs so you are not charged in noise for empty pushes. Connect destinations once in account settings, then enable them per story.

Backup, not two-way sync

Cloud backup is push-only. It does not pull edits from Dropbox or GitHub back into the editor. Disconnect removes Novilot's stored connection; files already on your destination stay put. A free signed-in account is required (guest sessions cannot connect destinations).

Works with export

Need a single publish-ready file? Use import and export for DOCX, EPUB, or PDF. Use cloud backup when you want an ongoing copy of the whole writing package in a place you already trust.

See also: import and export, story bible, and FAQ.