The short answer
Version control for writing comes down to three habits: save a named snapshot before every big change, keep a history you can go back to, and compare two versions before you send or publish. The version history built into Google Docs, Microsoft Word and the WritePadPro editor covers most writers. Clear file names cover the rest. Git is optional, and it pays off mainly for long projects written in plain text.
Five ideas worth borrowing from software
| Term | What it means for a writer |
|---|---|
| Version (snapshot) | A saved copy of the whole document at one moment, such as “sent to editor” or “before cutting chapter 3”. |
| History | The list of versions, newest first, with dates and labels. |
| Diff | A comparison that shows exactly which words were added or removed between two versions. |
| Restore | Going back to an earlier version without losing the current one. |
| Branch | A copy you develop separately, such as an alternate ending or a shorter edition, while the main draft stays untouched. |
You don’t need special software for any of these. You need a habit and one place where the versions live.
Level 1: File names that sort themselves
If you save drafts as separate files, the name is your version control. Use this pattern:
YYYY-MM-DD_project_v##_status.ext
2026-10-02_grant-proposal_v01_draft.docx
2026-10-09_grant-proposal_v02_to-editor.docx
2026-10-14_grant-proposal_v03_editor-changes.docx
2026-10-16_grant-proposal_v04_approved.docx - Put the date first, as year-month-day. ISO dates sort alphabetically in the same order as chronologically, so any folder view lists versions in order.
- Pad version numbers to two digits. In plain alphabetical order, “v10” sorts before “v2”; “v02” and “v10” sort correctly. If you already have unpadded names, the Natural mode in Sort Lines orders a pasted list of names correctly (file2 before file10).
- Use a status, never “final”. “final”, “final-2” and “final-REALLY” are how version chaos starts. Say what state the file is in: draft, to-editor, client-edits, approved, published.
- Never edit a file you have sent. Save a new version number first, so the copy someone else is reading stays identical to yours.
- Keep one current file. Move older versions to an “archive” folder so nobody opens the wrong one.
Level 2: The version history you already have
Most writing apps keep versions automatically. The details below come from Google’s and Microsoft’s help pages, checked on 2026-10-14.
Google Docs
- Open the history from the “Last edit” link at the top of the document, or with Ctrl + Alt + Shift + H (Cmd + Option + Shift + H on a Mac). You need edit access.
- Name important versions (More, then “Name this version”). A document can have up to 40 named versions, and “Only show named versions” hides the automatic ones.
- You can restore any version, or make a copy of an old version as a separate file, which works as a simple branch.
Source: Google Docs Editors Help, “Find what’s changed in a file”.
Microsoft Word
- In Microsoft 365, version history works only for files stored in OneDrive or SharePoint. A file saved only on your own disk has no version history, so keep numbered copies yourself.
- Click the file name in the title bar and choose Version history; selecting a version opens it in a separate window with a Restore option. Office 2016–2021 uses File, then History. On a Mac, click the document name in the title bar and choose Browse Version History.
- Microsoft says a personal account can retrieve the last 25 versions; for work and school accounts it depends on how the library is set up.
Source: Microsoft Support, “View previous versions of Office files”.
Track Changes is not version history
Track Changes (Ctrl + Shift + E in Word) records proposed edits inside one file so someone can accept or reject them. It is a review tool, not a backup: once changes are accepted, the old wording is gone from that file. Save a version before you accept a round of edits. Word’s Compare command on the Review tab builds a tracked-changes view from two separate files, which helps when an editor returns a copy without tracking.
Version history in the WritePadPro editor
The WritePadPro editor saves your document in your browser as you type and keeps versions alongside it. This is how it works, taken from the editor’s code:
- Manual versions: press Ctrl + S (Cmd + S on a Mac) to save a “Saved version”. If nothing has changed since the last version, no duplicate is created.
- Automatic versions: when you start editing a saved document in a new session, the editor first keeps a “Before this editing session” version. While you keep editing, it adds an automatic version about every 10 minutes.
- Safety versions: the old text is kept as a version before you restore another version, before a document is emptied, and when the same document was changed in another browser tab.
- Preview: any version can be compared word by word with your current text, with a count of words added and removed, or viewed as it was.
- Restore: restoring replaces the text, but your current text is saved as a version first, so a restore can always be undone.
- Limit: up to 50 versions per document. When the limit is reached, the oldest automatic versions are removed first, then the oldest manual ones.
The Versions panel is in the left sidebar of the full workspace. Ctrl + S also works in the homepage editor; open the full workspace to see the list. Our Version Snapshots guide walks through the panel step by step.
Where versions live: documents and versions are stored only in this browser on this device, never on a server. Clearing your browser’s site data deletes them. To move them, or to keep a backup, use “Back up all” in the Documents drawer to download a file, then “Restore backup” in another browser. A restore never overwrites: if the same document exists in both places, the newer text stays current and the other copy becomes a version.
Level 3: Compare two versions
A diff answers the question “what exactly changed?” That matters when an editor returns a file, when two people edited copies, or before you publish an update to an old article.
Example. Version 1: “We will launch the new plan in March for all customers.” Version 2: “We will launch the plan in April for existing customers.” A word-level comparison shows three deletions (new, March, all) and two insertions (April, existing). Small changes like these are easy to miss when you read both versions side by side yourself.
The Text Diff Checker compares two texts by line, word or character, side by side or in one column. It can ignore case, whitespace, blank lines and punctuation-only changes, collapse unchanged lines, jump between changes, merge them, and export a standard .diff file or an HTML report. For a walkthrough, see How to Compare Two Documents.
- Use word mode for prose. Line mode marks a whole paragraph as changed when one word moved.
- Turn on “ignore whitespace” after reformatting. Otherwise rewrapped lines and double spaces hide the real edits.
- Compare against what you sent, not your last draft, when checking an editor’s changes.
Branching without Git
Sometimes you need two live versions of the same piece: a 1,500-word article and a 600-word newsletter edition, or two possible endings. That is a branch, and you can make one in any tool.
- Google Docs: make a copy of the document, or of an older version from the version history.
- WritePadPro: use Duplicate in the Documents drawer. The copy gets “(copy)” added to its title and starts with no versions of its own; the original keeps its full history.
- Files: put the branch in the name, for example 2026-10-14_article_v03_newsletter-edition.docx.
Merging prose is a manual job. Compare the two texts in the Text Diff Checker, then choose “Use original” or “Use modified” for each change; the merged result builds up as you go, and you can edit it before copying it out.
Level 4: Git for prose (optional)
Git is the version control system most software teams use. It is worth learning for writing when the project is long (a book, documentation, a thesis), written in plain text such as Markdown, and you want a complete, offline history or several people work on it. For a single article in Google Docs, it is overkill.
git init # start tracking a folder
git add chapter-01.md # stage the file
git commit -m "Draft chapter 1" # save a version with a message
git log --oneline # list versions
git diff --word-diff # word-level changes since the last commit
git switch -c shorter-edition # start a branch for an alternate version
git restore --source=HEAD~2 chapter-01.md # bring back the file from two commits ago - Write in plain text. A .docx file is a compressed package, so Git can store it but can’t show a readable diff. Draft in Markdown, for example in the Markdown Editor, and export to Word at the end.
- Put one sentence on each line. Markdown joins the lines into one paragraph when rendered, and Git’s line-based diffs then show changes sentence by sentence.
- Write commit messages that say why. “Cut the second example; it repeated the first” is useful in six months. “Edits” is not.
The [-removed-]{+added+} markup that git diff --word-diff prints is the same markup the Text Diff Checker copies in word mode, so you can share a comparison with a Git user either way.
A versioning routine that works
- Before any big change (restructuring, cutting a section, accepting edits), save a named version.
- While you write, let autosave and automatic versions run.
- At each milestone (first draft, sent for review, approved), export a file with a dated, numbered name.
- When feedback comes back, compare the returned copy with the one you sent before accepting anything.
- After publishing, keep the published version as its own named version, so later updates can be compared with what readers saw.
Mistakes to avoid
- One file, overwritten forever. Autosave protects you from a crash, not from your own bad edit an hour ago. Named versions do.
- Versions in only one place. Browser-based history lives in that browser; cloud history lives in that account. Export important milestones as files.
- Treating Track Changes as a backup. Accepting all changes removes the old text from the file.
- Comparing the wrong pair. Check which two versions you are diffing; the names and dates should be in front of you.