Development & infrastructureGit project contributorsOpen source
Git
Decision matrix
Git app decision matrix
Overview
Git is free, open-source version control software: it tracks every change to a set of files, lets you go back to any earlier version, and lets several people work on the same files without overwriting each other. Pick it for any text-based work (code, notes, configuration) you'd regret losing a history of; pair it with a host like Gitea or GitHub to share a repository with others.
Other good fits
Several people working on the same files without a shared drive's overwrite risk.
+ Pros
Read pros
Git tracks every change to a set of files over time: each saved change (a "commit") is recorded with what changed, when, and a message explaining why. You can go back to any earlier point, see exactly what changed between two versions, and let several people work on the same files in parallel (on separate "branches") without silently overwriting each other's work.
Pick it when…
You're working on anything text-based, code, Markdown notes, configuration files, where a history of changes has real value.
More than one person needs to work on the same files, and you want a clear way to merge everyone's changes.
You want the ability to undo a mistake by going back to an earlier version, not just trust that nothing goes wrong.
− Cons
Read cons
Git tracks text-based changes well but handles large binary files (video, big design assets) poorly without extra tooling like Git LFS; don't expect it to behave like a general file backup tool for those. It has a real learning curve: branching, merging and resolving conflicts take some practice before they feel natural, and a badly resolved merge can quietly lose someone's change if you're not careful.
Pick something else when…
You just want simple personal file sync, not full version history. A sync tool is simpler for that one job.
Your files are mostly large binaries (video, big design files). A dedicated asset-management or media tool handles that better than plain Git.
You want a hosted place to keep a shared repository, not just local version control.Gitea (self-hosted) or GitHub (hosted) give you that on top of Git itself.
Avoid if
You just want simple cloud sync for personal files; a sync tool is simpler than learning Git's model for that alone.
Workflow
Initialise a repository in a folder (git init) or clone an existing one → make changes and save them as commits with a clear message → create a branch for a set of related changes → merge that branch back once it's ready → push to a shared host (like Gitea or GitHub) if you're collaborating with others or want an off-machine backup.
Cost
Git itself is free, open-source software with no subscription or credit system; you install it once and it runs locally on your own files. The running effort is learning its core commands and habits (commit often, write clear messages, branch for anything experimental); hosting a shared copy (for backup or collaboration) is a separate choice, self-hosted with something like Gitea, or on a service like GitHub, each with its own pricing.
Restrictions
Git itself has no hosting, access control or web interface built in; those come from a separate hosting service layered on top. Large binary files need Git LFS or a different tool entirely; plain Git will work but perform poorly as those files grow.
First project
Documentation-based suggestion — not run here.
Turn a folder of plain-text notes into a Git repository: initialise it, make an initial commit, then deliberately make and commit three small changes over a few minutes. Use git log to see the history, then check out an earlier commit to confirm you can actually recover a previous version.
Done when you've made at least three commits, viewed the history, and successfully recovered content from an earlier commit, not just trusted that you could.
Links & evidence
Documentation-based · not hands-on · Sep 23, 2026
Rests on Git's official documentation, read on 2026-09-23. No repository was created for this review.
Record, compare, branch, and restore changes to project files.
Work locally without depending on a hosting provider.
Use commits to make prompts, code, and analyses reproducible.
Git project contributors · free · self-host
version control
branching
change history
diff inspection
rollback
write-code
version-control
collaborate
View sourced imageThe gitg desktop interface for Git, as illustrated on Git's official GUI directory. Git itself also provides a command-line interface.
Git official product documentation
Owner-requested editorial use of public official interface screenshots, 15 September 2026. Copyright retained by the original publisher; attribution preserved. No open licence or hands-on course execution is asserted. Source asset: https://git-scm.com/images/guis/gitg@2x.png. PNG conversion preserves the complete frame.
