Version Control for Prose

Writers who got tired of novel-final-FINAL-v3-actually-final.docx discovered git. Plain-text manuscripts (markdown, LaTeX, Fountain) live happily in git; .docx does not (it's a zip of XML — diffs are unreadable). For collaborative editing see writing-collaboration-track-changes; for markdown editors see writing-markdown-editors.

Git for plain-text manuscripts

• ★ ★ Git — free OSS; the obvious answer for any writer working in markdown, LaTeX, Typst, Fountain. Branches for "version A vs version B," tags for draft 1 / 2 / 3 / submission, full history forever, free private hosting via GitHub / GitLab / Codeberg.
• GitHub — paid + free; unlimited free private repos; Issues / Discussions can be beta-reader feedback channels.
• GitLab — paid + free; same niche; self-hostable Community Edition.
• Codeberg — free; non-profit; pleasant for writers wary of MS-owned GitHub.
• Forgejo / Gitea — free OSS; self-hostable lightweight git host.

Git inside writing apps

• ★ Obsidian Git plugin — free; auto-commit and push your vault on a schedule. The default for the Obsidian-novelist workflow.
  • https://github.com/Vinzent03/obsidian-git
• Working Copy — paid + free; iOS git client; write in iA Writer / 1Writer and commit on iPad / iPhone.
• GitJournal — Apache; free OSS; iOS / Android markdown notes app with git sync.
• Manuskript Git plugin — community plugin; commits the manuscript folder.

Pandoc + git workflow

• ★ Pandoc — GPL; free OSS; pair with git: write in .md, version-control as text, build .docx / ePub / PDF for editors / submission. The canonical text-writer toolchain.
  • https://github.com/jgm/pandoc
• Quarto — MIT; free OSS; Pandoc-based; great for non-fiction / academic with citations + figures.
• Make / just — automate make epub, make pdf, make submission targets.

Diff tools for .docx / non-text formats

• Draftable — paid + free Lite; ★ for .docx diff; see writing-collaboration-track-changes.
• Word Compare — paid; built into Word.
• Pandoc to text + git diff — free trick: convert both .docx files to markdown and diff that — works surprisingly well.

Day-to-day backup (not just version control)

• Time Machine / File History — free; OS-level versioning.
• Backblaze / Arq — paid; offsite backup. See backup-disaster-recovery.
• Syncthing — free OSS; folder sync between machines.
• Dropbox / Google Drive / OneDrive / iCloud — paid + free; live sync; include version history (Dropbox keeps 30+ days on free, more on paid).

Specialist services

• Branch — paid; cloud manuscript versioning; was niche.
• PressForward — free; WP plugin for collaborative editorial workflows.
• Patchwork / patches — for editors who want email-based patch workflows (rare but exists).

What writers actually do

• Most prose-in-git users: git init, commit on each writing session ("session 41: 3,200 words; chapter 12 done"), push to a private GitHub repo, and that's the whole workflow.
• Many writers don't use git at all and rely on Dropbox + their app's autosave + local backups. That's fine for most projects under a year.
• The 95th-percentile writer using git also runs pandoc to build a .docx for their editor.

Pick this if…

• Markdown / Fountain / LaTeX writer: git + GitHub (or Codeberg) + Pandoc.
• Obsidian writer: Obsidian Git plugin + a private repo.
• iOS writer: Working Copy + iA Writer.
• .docx-only writer: Dropbox / OneDrive history + Draftable for diffs.
• Non-fiction / academic + citations: Quarto + git.
• Just want backups, not versioning: Backblaze + Time Machine.