Tool profilesTested by us

Restic: encrypted backups you can restore, free and open source

Restic is a free backup program that encrypts your data and only stores what changed. We tested it on Windows with fake data: what it does, a 5-step tutorial, its limits (lose the password, lose the backup) and what we could not confirm.

Type

Backup program (command line)

License and cost

BSD 2-Clause licence, free

Reviewed

30 Oct 2026

Version

0.19.1 (released 5 Jul 2026), tested on Windows 64-bit

Best for

Founders and small teams who want an encrypted backup they can restore, without paying for a service.

Watch out for

Lose the password and the backup is gone. Test a real restore, not just the check.

← All tool profilesNo. 2 / 11

In one sentence

Restic copies the folders you choose into a repository, which is just a storage place such as a folder, a server or a cloud bucket. It encrypts everything before it is stored, and each new backupBackup A copy of your data kept apart from the original, so you can recover it if something is lost, broken or locked. Tap again to open the glossary only adds what changed.

Who it is for

Founders, indie makers and small teams who keep their project, their notes or their servers' data in a few folders and want a backup they can restore, without paying for a service. It is a command-line tool, so you need to be comfortable typing commands.

What the documentation says

  • Encrypted: restic protects the privacy and integrity of the data, even if it is stored somewhere you do not trust.
  • Only the new parts: duplicate data is removed before it is written, so later backups add only what changed.
  • Snapshots: every backup is a snapshot. You can restore files with restic restore or browse old snapshots by mounting the repository.
  • Many places to store it: a local folder, SFTP, a REST server, Amazon S3 and compatible services, Backblaze B2, Azure, Google Cloud Storage, and many more through rclone.
  • Systems: Linux, macOS and Windows, among others.

What we saw when we tested it

On 30 October 2026 we tested restic 0.19.1 on Windows, with fake files in an isolated folder and a throwaway password. Nothing real was backed up.

  • Download and check: we downloaded the official Windows zip from the project's releases page. Its SHA-256 matched the one in the release's SHA256SUMS file. We did not check the project's signature.
  • First backup: 3 files, about 195 KiB. restic added about 205 KiB to the repository.
  • Second backup after changing one line in one file: restic added about 10 KiB. That is the "only what changed" claim, seen working.
  • Check: restic check ended with "no errors were found" on the two snapshots.
  • Restore: we deleted the folder, restored the latest snapshot into an empty folder and compared the file with the original. It was identical. One thing to know on Windows: the restore also tried to set the dates of the parent folders from the original path, failed, and ended with exit code 1 and "Fatal: There were 1 errors", even though our file came back identical. Do not read that exit code alone: look at the message and compare the files.
  • Wrong password: "wrong password or no key found", exit code 12.
  • Empty password: refused, as the documentation says, unless you pass --insecure-no-password.
  • Source that does not exist: it says it is skipping it, and when nothing is left, it ends with a fatal error and exit code 1.

The good

  • Free and open source, with a simple model: one repository, many snapshots.
  • EncryptionEncryption Scrambling data with a key so that only someone with the key can read it. Tap again to open the glossary is not an extra: it is how the tool works.
  • You choose where the copy lives, so you can keep it away from the machine you back up.
  • Later backups were small and fast in our test.

The limits it admits

  • If you lose the repository password, the data cannot be recovered. The documentation says so more than once, and the program prints it when you create the repository.
  • Storing the repository on a CIFS/SMB share on Linux, or backing up from one, is not recommended because of compatibility problems in older kernels.
  • A backup piped in with --stdin can hide a failure of the program that produced it, and leave an empty or incomplete copy. The documentation recommends --stdin-from-command instead.

When not to use it

  • If you do not want to manage a password and a place to store the copy. A lost password means a useless backup.
  • As your only copy. A backup you have never restored is a guess, not a backup.
  • If you need a graphical tool: restic works from the command line.

What it costs you

Time more than money. Our test, from download to a checked restore, took a few minutes. The real work comes after: choosing where the repository lives, setting up a schedule so the backup runs by itself, and checking now and then that it still works. If you keep the repository in a cloud service, that service has its own price.

Typical setup mistakes

  • Losing or never saving the password. Store it in a password managerPassword manager An app that creates, stores and fills in a different strong password for every account, so you only remember one. Tap again to open the glossary, in a different place from the backup.
  • Never testing a restore. restic check verifies the repository, but a real restore is the proof.
  • Keeping the repository on the same disk you are backing up. If the disk fails, you lose both.
  • Ignoring the exit code and the message. The documentation says 0 means a full success, 1 means a fatal error with no snapshot, and 3 means some files could not be read, so the snapshot is incomplete. We also saw 12 for a wrong password, and the Windows restore quirk above. A schedule that never looks at the result can fail silently.
  • Wrong exclude patterns. Patterns do not apply to paths you pass explicitly, and a wrong pattern can leave out what you wanted to keep.

5-step tutorial (tested on Windows, restic 0.19.1)

Use a test folder with fake files first. Replace the names in angle brackets with your own.

  1. Download and check. Get the zip for your system from the official releases page, and compare its SHA-256 with the SHA256SUMS file on the same page. Unzip it into its own folder.
  2. Set a password for this session and create the repository. For a real backup, create a long password and save it in your password manager first. Then run restic init --repo <repository folder>. Restic prints the warning about losing the password.
  3. Back up. Run restic -r <repository folder> backup <folder to back up>. It prints how many files are new and gives you a snapshot ID.
  4. Change something and back up again. Edit a file and run the same command. Look at the "Added to the repository" line: it should be small.
  5. Check and restore. Run restic -r <repository folder> check and expect "no errors were found". Then restore with restic -r <repository folder> restore latest --target <empty folder> and compare a file with the original. On Windows, the files can be several folders deep inside the target, because the original path is recreated.

Expected result after step 5: the restored file is identical to the original. For a real setup, add a schedule and keep the password outside the machine you back up.

What we could not confirm

We tested on one Windows machine with a local repository only. We did not test cloud or server repositories, Linux or macOS, large amounts of data, pruning old snapshots, or running restic on a schedule. We did not verify the project's cryptographic signature of the release, only its SHA-256. The backup documentation we read does not cover restore, forget or prune in detail, so we do not describe them beyond what we ran. We have not compared restic with other backup tools.

Glossary: backup, encryption. Our own free checks live in Tools.

More free tools

Other profiles in this section.

Sources

Follow us

New profiles and security news: YouTube (@safet2ship) and Instagram (@safet2ship).

YouTube channel · Instagram

Get the free runbooks

One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

Send me the runbooks