# Version control

Version control records changes to your files over time, so you can go back to any saved version. How it works with Git and GitHub, explained for writers.

**Definition:** Version control is a system that records changes to a set of files over time, so you can go back to any saved version, compare versions and see what changed when.

## The parts, in plain words

- **Repository:** a folder whose history is recorded. With Git, the history lives in a hidden `.git` folder inside it.
- **Commit:** one saved version of the whole folder, with a message and a unique ID.
- **History:** the list of commits, newest first, each one a version you can go back to.
- **Diff:** what changed between two versions. See [git diff](/glossary/git-diff), and for prose, a [word diff](/glossary/word-diff).
- **Remote:** a copy of the repository somewhere else, such as GitHub, that you push to and pull from.

## Why writers use it

- **Undo past the last save.** Go back to Tuesday's draft, or to the version before an agent rewrote it.
- **Agents change many files at once.** A commit before the agent starts is a clean way back.
- **A copy off your computer.** Pushing to a remote backs up the files and their whole history.

Git is built around code, but it records nearly any kind of file, Markdown drafts included.

## In Flywrite

Flywrite does version control for you. Each [checkpoint](/glossary/checkpoint) is a Git commit of the whole project, saved when Claude Code starts, when Cursor Agent starts after its one-time setup, or when you press ⌘⇧C. Versions (⌘⇧V) lists them newest first, and you restore the project or one file from any of them. Connect the project to your own GitHub account and Sync backs it up with one button. You never type a git command. More in [Backup & sync with GitHub](/docs/github-backup-and-sync) and the guide to [backing up Markdown to GitHub](/guides/back-up-markdown-to-github).

## Questions

### Is version control the same as a backup?

Not on its own. A repository on your Mac is a history, not a second copy. Pushing it to a remote such as GitHub puts a full copy, history included, off your computer.

### Do I need to learn Git to use version control?

Not in Flywrite. Checkpoints are Git commits Flywrite makes for you, and GitHub backup is one Sync action, with no git commands.

## Sources

1. [Pro Git: About Version Control](https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control), checked 2026-11-10
2. [GitHub Docs: Commits](https://docs.github.com/en/pull-requests/reference/commits), checked 2026-11-04
3. [Flywrite docs: Checkpoints & versions](/docs/checkpoints-and-versions), checked 2026-11-17
4. [Flywrite docs: GitHub backup & sync](/docs/github-backup-and-sync), checked 2026-11-17

---

This is the Markdown copy of https://flywrite.app/glossary/version-control.
