Softwr

Backup · head to head

Restic vs Syft

Restic logo

Restic

Backup

Fast, secure, and efficient backup program

From
Free
Free plan
Yes
Syft logo

Syft

Cybersecurity

Generates a software bill of materials from images, filesystems and archives

From
Free
Free plan
Yes

The short version

  • Restic is a fast, secure backup program.
  • Both are free.
  • Only Restic lists content-defined chunking; only Syft lists multi-format output.
  • Where Restic falls short: A Windows file whose name contains a character Windows treats as invalid cannot be read by restic and has to be renamed.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Restic and Syft actually diverge.

Attributes where Restic and Syft differ
AttributeResticSyft
Pricing modelFreeOpen source, no licence fee
PlatformsWindows, macOS, LinuxmacOS, Linux, Windows, Self-hosted
CategoryBackupCybersecurity

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Syft.

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Restic

  • Content-defined chunking
  • Cryptographic verification
  • Deduplication
  • Encryption
  • Multiple backends
  • Snapshot management
  • AWS S3
  • Azure

Only in Syft

  • Multi-format output
  • Broad ecosystem coverage
  • Binary classifiers
  • In-toto attestations
  • Library and CLI
  • Pairs with Grype

What people use each for

The jobs each tool is most often brought in to do.

Restic

  • Encrypted deduplicated backups to S3, B2, SFTP and local disk from the command linenot Syft
  • Scripted server backups with snapshot retention policiesnot Syft

Syft

  • Producing a bill of materials for a customer or regulator that requires onenot Restic
  • Feeding an inventory into a vulnerability scanner rather than scanning images directlynot Restic
  • Recording what shipped in a build so a future disclosure can be answered quicklynot Restic
  • Public sector work where an SBOM is a contractual deliverablenot Restic

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Restic

  • Cold storage is not natively supported; restoring from S3 Glacier and S3 Glacier Deep Archive is only available as an experimental feature behind a feature flag
  • A Windows file whose name contains a character Windows treats as invalid cannot be read by restic and has to be renamed
  • Antivirus real-time protection degrades performance on Windows unless the restic binary is added to an exclusions list
  • On large repositories the built-in five minute stuck-request timeout fires during file listing and has to be raised manually with --stuck-request-timeout

Syft

  • Lockfile parsing can drop packages silently. An open issue filed in August 2026 reports the yarn v1 cataloguer returning 118 of 745 packages with no error raised, which means a complete bill of materials and an 84 percent incomplete one look identical to the caller
  • Fidelity varies sharply by ecosystem. Conan for C and C++, Haskell and Terraform get cataloguer support with no licence data, no dependency relationships and no file ownership, so a C and C++ shop gets the least from it
  • Binary classification yields no licence or dependency metadata, and vendored or statically linked code is exactly where supply chain risk hides, so the blind spot and the risk overlap
  • Incorrect CPE values and CPE collisions are recorded as open issues, and since Grype matches on CPE and PURL, an inventory error becomes a false negative in the security report downstream
  • An inventory is not a risk assessment. Even a perfect bill of materials says a vulnerable version is present, never that the vulnerable function is called, and the triage burden lands entirely on the reader

Pricing, plan by plan

Restic

Free
  • FreeFree
    • Content-defined chunking
    • Encryption
    • Multiple backends

Syft

Free
  • SyftFree
    • Apache-2.0
    • No usage limits
    • Community support
  • Anchore EnterpriseOn request
    • Policy enforcement and reporting
    • Federal and commercial tiers
    • Pricing not published, quoted on request

Which should you pick?

Choose Restic if

  • You need content-defined chunking.
  • You want to start without paying.
  • You work on Windows, macOS, Linux.
  • You also want cryptographic verification.

Choose Syft if

  • You need multi-format output.
  • You want to start without paying.
  • You work on macOS, Linux, Windows, Self-hosted.
  • You also want broad ecosystem coverage.

Questions people ask

Is Restic or Syft better?
Neither clearly leads. Restic starts at Free and Syft at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Restic or Syft?
Restic starts at Free and Syft at Free.
Does Restic or Syft run on more platforms?
Restic runs on Windows, macOS, Linux. Syft runs on macOS, Linux, Windows, Self-hosted.
Can I use Restic for free?
Both have a free tier, so you can try either at no cost before committing.
What is Restic best used for?
Restic is most often used for encrypted deduplicated backups to s3, b2, sftp and local disk from the command line, scripted server backups with snapshot retention policies. Of those, encrypted deduplicated backups to s3, b2, sftp and local disk from the command line and scripted server backups with snapshot retention policies are not what Syft is typically brought in for.
What can Restic do that Syft cannot?
Restic covers Content-defined chunking, Cryptographic verification, Deduplication, Encryption. Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations.

Answered from the vendors’ own pages

Restic: How much does restic cost?

Restic is entirely free to use and completely open source. There are no subscription tiers, paid plans, or licensing costs.

Source
Syft: Does Syft find vulnerabilities?

No. It produces an inventory. Grype, from the same company, matches that inventory against vulnerability feeds. They are separate tools and the distinction is frequently lost.

Syft: Does anything in the Anchore stack do reachability analysis?

No. Neither Syft, Grype nor the commercial Anchore platform performs call graph or reachability analysis, so none of them tells you whether a vulnerable code path is actually invoked.

Syft: Is it a CNCF or OpenSSF project?

No. It is single-vendor open source owned by Anchore, with no foundation governance. That is a different licence risk profile from Sigstore.

Syft: What does Anchore Enterprise cost?

Not published. The pricing page is contact-sales only, with named but unpriced commercial and federal tiers.

Syft: How do I know my SBOM is complete?

You largely cannot, which is the honest answer. Silent partial parsing is a known open defect, so a bill of materials used for compliance should be spot-checked against a known dependency list.

Share

Related pages

Other head to heads