At the present time, pre-built binaries are not available for Tarsnap — it must be compiled from the source code. Some operating systems include Tarsnap packages (e.g., the FreeBSD Tarsnap port, NetBSD Tarsnap port), which automate the compiling and installation process.

If you wish to compile manually,

1. Download the latest source tarball and SHA256 hash file (below).
2. Proceed to Compiling Tarsnap.

Tarsnap 1.0.37 (March 10, 2016)

Downloads:

• source tarball
• signed SHA256 hash file

You can see all of the changes between 1.0.36 and this version in the public git repository at

https://github.com/Tarsnap/tarsnap

Major changes since version 1.0.36:

• tarsnap-key(gen|mgmt|regen) now accept a --passphrase-time option, which specifies the duration to be spent on computing the derived keys used for encrypting the tarsnap key file.
• tarsnap now accepts a --keep-going option when deleting or printing statistics about multiple archives.
• tarsnap-keymgmt now accepts a --print-key-permissions option for listing the permissions contained in a key file.
• tarsnap --print-stats now accepts a --csv-file option for printing statistics in comma-separated-value format.
• tarsnap now accepts a --verify-config command which exits silently after checking the configuration file(s) for syntax errors.
• tarsnap now looks for a server named "v1-0-0-server.tarsnap.com" instead of the historic "betatest-server.tarsnap.com" hostname. This should have no user-visible effect in most configurations.
• tarsnap now correctly warns if a sparse extract fails due to hardlinks.
• tarsnap now prints a warning if creating an empty archive.

• Old releases are available for historical and diagnostic purposes, but we strongly recommend that people use the latest official tarball.
• The Tarsnap git repository is on github; developers may wish to watch changes in progress or investigate bugs.