Softwr

Backup · head to head

Borg Backup vs Kopia

Borg Backup logo

Borg Backup

Backup

Deduplicating archiver with compression and encryption

From
Free
Rated
-
Kopia logo

Kopia

Backup

Open source deduplicating backup with client side encryption and a repository on almost any storage

From
Free
Rated
-

The short version

  • Each has a real cost: Borg Backup linux, macOS and BSD only; Windows is not a supported platform; Kopia space is only reclaimed when maintenance runs, and in a shared repository full maintenance is owned by one client, so if that machine goes away the repository grows for ever while every backup still reports success.
  • They diverge on capability: Borg Backup covers Content-defined chunking, Kopia covers Content defined chunking.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Borg Backup and Kopia actually diverge.

Attributes where Borg Backup and Kopia differ
AttributeBorg BackupKopia
Pricing modelfreeOpen source, no licence fee
PlatformsLinux, MacLinux, macOS, Windows, Docker
Founded2015Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Backup).

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 Borg Backup

  • Content-defined chunking
  • Deduplication
  • Compression
  • Authenticated encryption
  • Pruning
  • Mount archives
  • SSH
  • BorgBase

Only in Kopia

  • Content defined chunking
  • Global deduplication
  • Pack blobs
  • Client side encryption
  • Desktop and command line
  • Repository verification

What people use each for

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

Borg Backup

  • Deduplicated backups where daily full snapshots would otherwise be expensivenot Kopia
  • Encrypted backup to a server you do not fully trust, since the server never sees plaintextnot Kopia
  • Browsing previous versions by mounting an archive over FUSEnot Kopia
  • Scripted server backups with no agent or daemon to runnot Kopia

Kopia

  • Backing up laptops and workstations to cheap object storage with a desktop interface rather than a cron jobnot Borg Backup
  • Deduplicating backups of several similar machines into one repository so common content is stored oncenot Borg Backup
  • Replacing a chunk based tool whose per object charges made a cheap bucket expensivenot Borg Backup
  • Keeping an encrypted offsite copy where the storage provider must never be able to read the contentsnot Borg Backup

Where each one falls short

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

Borg Backup

  • Linux, macOS and BSD only; Windows is not a supported platform
  • Command-line only, with no graphical interface in the project itself
  • Version 2.0 is still in beta, so production use means staying on the 1.4 line
  • Restoring requires the Borg tooling, since archives are a deduplicated chunk store rather than plain files

Kopia

  • Space is only reclaimed when maintenance runs, and in a shared repository full maintenance is owned by one client, so if that machine goes away the repository grows for ever while every backup still reports success.
  • The repository format has changed across versions and mixing client versions against one repository is discouraged, so a fleet must be upgraded together rather than machine by machine.
  • There is no central orchestration or reporting for many machines, so monitoring a fleet means building your own alerting around exit codes.
  • Restoring many small files is slower than the backup was, because content must be reassembled from pack blobs, and this is rarely tested until the day it matters.
  • Encryption is client side with no escrow, so a lost repository password means the data is unrecoverable and there is no vendor to appeal to.

Pricing, plan by plan

Borg Backup

Free
  • FreeFree
    • Deduplication
    • Compression
    • Encryption

Kopia

Free
  • KopiaFree
    • Full functionality, no data limit
    • Desktop application included
    • Any supported storage back end

Which should you pick?

Choose Borg Backup if

  • You need content-defined chunking.
  • You want to start without paying.
  • You work on Linux, Mac.
  • You also want deduplication.

Choose Kopia if

  • You need content defined chunking.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Docker.
  • You also want global deduplication.

Questions people ask

Is Borg Backup or Kopia better?
Neither clearly leads. Borg Backup starts at Free and Kopia at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Borg Backup or Kopia?
Borg Backup starts at Free and Kopia at Free.
Does Borg Backup or Kopia run on more platforms?
Borg Backup runs on Linux, Mac. Kopia runs on Linux, macOS, Windows, Docker.
Can I use Borg Backup for free?
Both have a free tier, so you can try either at no cost before committing.
What is Borg Backup best used for?
Borg Backup is most often used for deduplicated backups where daily full snapshots would otherwise be expensive, encrypted backup to a server you do not fully trust, since the server never sees plaintext, browsing previous versions by mounting an archive over fuse, scripted server backups with no agent or daemon to run. Of those, deduplicated backups where daily full snapshots would otherwise be expensive and encrypted backup to a server you do not fully trust, since the server never sees plaintext are not what Kopia is typically brought in for.
What can Borg Backup do that Kopia cannot?
Borg Backup covers Content-defined chunking, Deduplication, Compression, Authenticated encryption. Kopia covers Content defined chunking, Global deduplication, Pack blobs, Client side encryption.

Answered from the vendors’ own pages

Borg Backup: What is the cost of BorgBackup?

BorgBackup is completely free and open source under the BSD license with no mandatory costs for the core software.

Source
Kopia: Is a partly corrupt repository still restorable?

Partly. Deduplication means one damaged pack blob affects every snapshot referencing its contents, but unaffected files still restore. Run verification regularly rather than assuming.

Borg Backup: Are there paid services available for BorgBackup?

Yes, optional third-party services are available: BorgBase for specialized Borg repository hosting, Hetzner Storage Box with Borg support, and rsync.net cloud storage integration.

Source
Kopia: How does it compare with restic?

Similar guarantees, with packing that behaves better on per operation billing, a desktop interface, and compression enabled by default.

Borg Backup: How can I support the BorgBackup project?

BorgBackup accepts voluntary contributions through Open Collective, GitHub Sponsors, Liberapay, and PayPal, though donations are optional.

Source
Kopia: Do I need to run maintenance manually?

It is scheduled automatically by default, but you must ensure the client that owns full maintenance keeps running, otherwise deleted snapshots never free space.

Kopia: Can several machines share one repository?

Yes, and that is where deduplication pays off, but they should run compatible versions and only one owns full maintenance.

Share

Related pages

Other head to heads