Kopia vs Restic

Kopia — strengths

• Includes a GUI (KopiaUI) alongside the CLI — friendlier for non-CLI users
• Built-in snapshot policies, scheduling, and retention without external cron
• Compression and deduplication with tunable performance
• Repository server mode for centralised, multi-client backups
• Broad backend support (S3, B2, GCS, Azure, SFTP, WebDAV, rclone)

Kopia — weaknesses

• Shorter track record than Restic
• More configuration surface (policies/settings)
• Smaller third-party tooling ecosystem

Restic — strengths

• Very mature, widely trusted, and extensively battle-tested for critical backups
• Dead-simple mental model: init, backup, snapshots, restore, prune
• Strong client-side encryption and content-addressable deduplication by default
• Huge ecosystem of wrappers (resticprofile, autorestic, backrest) for scheduling and UX
• Broad backend support, including anything rclone can reach

Restic — weaknesses

• No official GUI
• Scheduling and retention require external tooling
• Prune can be resource-heavy on large repositories

When Kopia fits

• User who wants scheduled, policy-driven backups with a GUI rather than hand-rolling cron and scripts: KopiaUI plus policies covers this end to end.
• Small team that wants several machines backing up to a central repository: Kopia's server mode is designed for exactly that topology.

When Restic fits

• Admin who wants the most proven, no-surprises CLI backup for important data and is comfortable pairing it with cron or a wrapper: Restic is the conservative, trusted choice.
• User who already relies on rclone for storage backends and wants deduplication and encryption on top: Restic slots in cleanly.

Kopia gotchas

• Newer than Restic with a shorter production track record — some prefer battle-tested tooling for critical backups
• More features and knobs (policies, compression settings) mean more to understand up front
• KopiaUI is convenient, but the CLI is still where advanced control lives
• Fewer third-party wrappers than Restic's mature ecosystem

Restic gotchas

• CLI-only — no official GUI; scheduling and retention are on you (cron or a wrapper)
• Compression is relatively recent (0.14), so older repositories predate it
• Pruning has historically been memory- and time-intensive on very large repos — plan resources
• Managing policies and schedules well usually means adding a wrapper like resticprofile or backrest

Choose Kopia when

Pick Kopia if you want built-in scheduling, retention policies, compression, and an optional GUI, plus a repository-server mode for centralised backups — a more batteries-included experience.

Choose Restic when

Pick Restic if you want the most mature, widely trusted, simple CLI backup tool and you're comfortable adding cron or a wrapper for scheduling — the conservative choice for critical data.

Migration

The two use incompatible repository formats, so you can't convert a Restic repo to Kopia (or vice versa) in place — migration means starting a fresh repository with the new tool. The safe approach is to keep the old repository intact and read-only for its retention window (so historical restores remain possible) while you begin taking new snapshots with the new tool into a new repository. Restore-test the old repo before you stop using it, point the new tool at the same source directories, configure equivalent retention, and once you have an adequate history in the new repository and have verified restores, retire the old one. Don't delete old backups until the new chain is proven.

Frequently asked questions

Which has a GUI?

Kopia — it ships KopiaUI, a desktop GUI, alongside the CLI. Restic is CLI-only; GUIs for it come from third-party projects like backrest.

Which is more battle-tested?

Restic has a longer production track record and a reputation as a conservative, trusted choice for critical backups. Kopia is newer but capable and actively developed.

Do both encrypt and deduplicate?

Yes — both use content-addressable storage with client-side encryption and deduplication by default, and both now support compression.

Which backends do they support?

Both support a wide range — S3, Backblaze B2, Google Cloud, Azure, SFTP, WebDAV — and both can use rclone to reach almost any remote.

Which handles scheduling better?

Kopia has built-in snapshot policies and scheduling. Restic relies on external scheduling (cron) or wrappers like resticprofile, autorestic, or backrest.

Can I migrate my Restic repo to Kopia?

Not directly — the repository formats are incompatible. You start a new repository with the new tool and keep the old one for restores during its retention window.

Which should I choose for a NAS or homelab?

Both work well. Choose Kopia if you want policies and a GUI out of the box; choose Restic if you value maximum maturity and don't mind wiring up cron or a wrapper.