Novilot

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.

Cloud backup

Push package. Not two-way sync.

Ready
  • Chapters (Markdown)Included
  • Story bibleIncluded
  • Outline cardsIncluded
DropboxGitHub (private repo)

Illustration of Novilot pushing a manuscript package to Dropbox or a private GitHub repo.

A long novel should not live in one place only

Backup is about continuity of the project package, not just a one-off file.

Account lock-in fear

Years of chapters and canon sit in one product account with no copy you control elsewhere.

Story bible left behind

A manuscript export without the bible and outline is an incomplete snapshot of the project.

No history on ad-hoc copies

Renamed zip files on a desktop do not give you commit history or retention you chose.

Sync confusion

Writers need an honest push backup, not a vague promise of two-way sync that can overwrite work.

How cloud backup works

Connect once. Enable per story. Push on demand or on a schedule.

  1. 1

    Connect Dropbox or GitHub

    Connect destinations in account settings. For GitHub, install the Novilot GitHub App and grant only the repos you choose.

  2. 2

    Enable backup per project

    Pick overwrite, timestamped, or keep-last retention for Dropbox, or a private repo per novel for GitHub.

  3. 3

    Run now or on a schedule

    Backup now from Project Settings, or turn on daily or weekly runs. Unchanged manuscripts skip scheduled runs so empty pushes do not create noise.

Backup pairs with export and canon

Questions, answered plainly

No. Cloud backup is push-only. It does not pull edits from Dropbox or GitHub back into the editor.

Back up your manuscript

Create a free account, connect Dropbox or GitHub, then enable cloud backup in Project Settings.

Start free

Or see import and export