Duplicati vs Kopia: Which Folder Backup App Should You Choose?

Duplicati vs Kopia at a glance #

The Duplicati and Kopia software is separate from any bill for cloud storage. Duplicati's console pricing includes a Free monitoring plan for two machines and the last 200 backups. That plan is optional, and it doesn't turn the desktop client into a trial.

Setup: Duplicati groups the decisions into one job #

Duplicati's setup wizard walks through configuration, destination, source folders, schedule, and retention. A job is a fairly concrete thing: this folder, this storage location, these run times. If you have a website project on one computer, that's a natural way to start.

Kopia asks you to create or connect to a repository, then define the sources and policies. A policy can apply to a path, user, machine, or the repository more broadly. That gives an administrator more control, but it also means understanding which settings a source inherits. A rule that feels clear for one folder becomes more valuable when ten folders need related schedules.

I'd begin with one source either way. Building a complete household backup arrangement before recovering a single file makes it harder to spot which decision caused a problem. A repository also isn't a directory full of ordinary copies you can inspect with any file manager. The backup application reads and reconstructs those files for you.

The Kopia getting-started guide shows the repository-and-snapshot model, and its installation page separates KopiaUI from the CLI. You can start with a desktop app and keep terminal access available for later automation. Duplicati takes the same general approach, but its job wizard is the clearer introduction for someone who has never set up encrypted backups.

Winner for a first single-computer setup: Duplicati.

Storage: direct cloud connections versus a shared repository #

Duplicati supports several vendor-specific backends as well as standards such as SFTP, WebDAV, and S3-compatible storage. Its destination overview distinguishes object storage from file-sync providers such as Dropbox and OneDrive. A supported provider in the destination picker saves you from adding another command-line bridge simply to connect an account.

Kopia supports local and remote repositories, with Rclone extending the list of cloud services. Its repository documentation covers those connections. An Rclone setup adds another component and its configuration, so I'd count it as part of the job when comparing convenience. If your destination is already supported directly, that extra work may disappear.

Kopia can deduplicate matching content across sources sharing a repository. That's attractive for several computers holding the same asset folders. But a directly shared repository password gives other users access to its data. A private family backup and a business backup with individual staff permissions need different designs.

Kopia's repository-server documentation describes the separate server arrangement for authenticated users and machine sources. You don't need it for a single laptop. I'd only add it when access management or central operations justify running another service.

For a small site project, I would choose the simplest destination you can recover from on a replacement computer. A familiar storage account is preferable to a complicated arrangement that only its original administrator understands. If you already transfer project files over SFTP, WinSCP can help inspect the account, although its ordinary transfers don't replace the backup program's version history.

Winner for built-in consumer storage connections: Duplicati; for several related sources in one repository: Kopia.

Recovery: Duplicati's local database and Kopia's snapshot sources #

Duplicati keeps a local database that indexes the remote backup. Its database documentation says the index can be reconstructed from the backup data. Having it present makes browsing and restores more efficient; losing it doesn't automatically mean losing the backed-up files.

That detail affects how long a recovery feels. A configured job can look up its local index immediately, while another computer first has to download and process the information needed to find the files. I'd keep the exported configuration available as part of a recovery plan, with credentials stored securely. Re-entering a cloud destination during an emergency is avoidable work.

Kopia's snapshot view can be filtered by source identity. In a January 2025 forum discussion, a user connected from another installation and wanted to resume the old history. Replies explained All snapshots, the original user and hostname, and moving history to the new identity. The files had a different source label; the situation initially looked like missing history.

I'd write down the source computer and repository details before replacing a machine. A good recovery plan identifies both the storage and the source history you're trying to recover. Kopia gives you file restore and snapshot mounting, while Duplicati's restore interface selects a backup version and its files. Both require understanding where the recovered output will go.

For a dead Windows system drive, look at Veeam Agent or Rescuezilla alongside either application. Folder backups are excellent for a lost project file, but reinstalling an operating system and its applications is a different task.

Winner for a familiar job-based recovery view: Duplicati; for browsing sources across one repository: Kopia.

Maintenance and privacy: encryption is only one decision #

Kopia always encrypts its repository data before sending it to storage. Duplicati lets you choose encryption, with built-in AES and a GPG option described in its encryption documentation. I'd choose encrypted backup data for either a cloud account or a disk that could leave the room.

Encryption doesn't stop an authorized storage account from deleting the encrypted files. Repository retention, storage permissions, and the place where you store access details remain part of a backup arrangement. Nor does hiding file contents make the destination provider disappear: it still operates the storage account and receives network requests.

Kopia assigns one user and hostname as the maintenance owner. Its maintenance guide explains that other clients won't run those automatic tasks for that owner. If that computer disappears permanently, changing ownership is part of moving the backup arrangement. Expired snapshot data also takes maintenance time to remove; deleting a snapshot isn't a promise that the storage bill drops instantly.

Duplicati offers monitoring and management through its console. You can also run the client independently. A March 2025 forum question about fully self-hosting prompted its developer to explain that the open-source client and commercial console are separate products. That distinction is easy to miss when the website leads with the hosted service.

Both projects provide public release records. The Duplicati stable-download directory and Kopia releases give you current packages and change history. I'd choose a stable release for a routine backup and read its upgrade notes before replacing a version that already writes to an important repository.

Winner for automatic encryption by default: Kopia; for optional hosted monitoring: Duplicati.

What users say #

Duplicati users who want full control over storage welcome the standalone client, while the self-hosting thread shows frustration when the optional console looks like a required account. The developer's explanation resolves that: the client remains its own open-source program. Its other source of friction is having several concepts to manage once a destination or local database needs attention.

Kopia's forum replies show how much assistance comes from understanding repository and source identities. The January 2025 discussion is encouraging because replies provide direct recovery commands and GUI paths. It also exposes a usability problem: a filter can make recoverable history appear absent until you know where to look. I wouldn't hand a multi-machine repository to someone without documenting its source names.

Choose the recovery model you can explain to the person who will use it later. A well-documented source name and destination can save more confusion than another optional feature.

Choose Duplicati if… #

• You want a wizard that keeps a folder, schedule, and destination together.
• Your storage provider has a direct Duplicati backend.
• You want the option of paid hosted monitoring later.
• You prefer recovering files through a named backup job.

Choose Kopia if… #

• You want policies that apply at several source and machine levels.
• Several computers can benefit from one repository's deduplication.
• You want encryption required throughout the backup arrangement.
• You're comfortable documenting source identities and maintenance ownership.

Alternatives to both #

Restic is worth considering when you want scripted folder backups and a command-line workflow. BorgBackup is another encrypted, deduplicated option for people who prefer that approach. UrBackup focuses on a server dashboard and client computers. For a Windows system image, Veeam Agent covers a recovery task that neither Duplicati nor Kopia is designed to replace.

Frequently asked questions #

Are Duplicati and Kopia really free?

Yes, their open-source backup clients are free. You supply storage, which might be a drive you own or a paid cloud account. Duplicati also sells an optional console and integrated storage. The console's free monitoring limits apply to that service, not to the number of independently installed free clients. Kopia has no paid desktop feature tier in its official project documentation.

Can I restore Duplicati backups without the original computer?

Yes. Duplicati's documented direct-restore workflow needs access to the destination and the encryption passphrase when encryption was enabled. It can construct the information needed from backup files. The old local index and configuration make the job easier, but aren't the only route. A new machine may spend time reading remote metadata before it can present a file list.

Does Kopia require a server?

No. A local Kopia client can back up directly to a supported repository. Its server mode is optional and adds a central service for authenticated users and repository access. For one computer, start with the desktop client and a supported storage destination. Running a server only makes sense when its access control or administration features solve a concrete need.

Can either program restore Windows and all my installed apps?

Neither provides the same bare-metal Windows system-image workflow as an imaging product. They back up files and folders, so they are good candidates for recovering source code, documents, and exported application data. To recover a failed system disk with Windows and installed applications, add an imaging and recovery-media plan. Don't assume a complete user-folder backup covers the boot and system partitions.

Sources #

Product facts come from Duplicati documentation, Duplicati console pricing, Kopia documentation, and the projects' release and license records. The linked forum discussions explain the standalone-client choice and recovery of old source history.