Find your fit
Who it is for
It fits a desktop user who wants Borg’s backup format without managing every run in a terminal. The operator still chooses and maintains a local, removable or remote repository and must keep the passphrase or keyfile recoverable.
For a Windows-first environment, check platform fit carefully: Borg is not fully supported natively on Windows, and the project documents WSL as a workaround. Test on the actual operating system before adopting it for a critical machine.
The work it supports
Core capabilities
Create a profile for source folders, exclusions, destination and schedule. A local repository may sit on the same computer or removable drive; a remote repository can run on your own SSH/Borg server or optional hosting.
The backup engine is Borg, which provides encryption, deduplication and compression. Vorta exposes those backups through a desktop application, so compare it with BorgBackup and borgmatic as a user interface and workflow choice rather than as an unrelated backup format.
Each successful run creates an archive in the repository. Browse point-in-time archives to identify the version you need and try a harmless sample restore before treating the schedule as a recovery plan.
The integrated scheduler shows the next planned run after you apply an interval. Vorta itself must remain running for that scheduler to fire; enabling desktop startup and checking the next-run display are useful setup checks.
An external cron job or script can trigger a named profile in a running Vorta application. This is an alternative trigger for an operator who already manages system scheduling or removable-drive events.
For recovery, extract selected files to a chosen location or mount an archive and copy files from it. Mounting can require FUSE support, so test extraction as well as the preferred browse path on your target machine.
Prune old archives manually or after backup according to retention rules. Because this removes recovery points, first model what will remain and keep enough destination space while validating the policy with disposable files.
Profile and repository settings can be exported as JSON for moving to another installation. The export may optionally contain the repository password; handle that file as sensitive and check exactly what is included before sharing or storing it.
Understand the offer
Pricing and getting started
Vorta itself is free and open source under the GNU GPL. The software does not include physical backup capacity; the repository can be local, removable or remote and remains the operator’s storage choice.
BorgBase is one optional remote hosting destination described by the project, while a self-managed SSH/Borg server is another. Check the chosen provider’s current price, storage allowance and access terms separately; no hosting fee is included in Vorta’s free-client statement.
Look a little closer
Before you choose
Back up a disposable folder, inspect its archive and restore a changed file to a separate location. A completed scheduled run alone does not prove that repository access, key custody and the desired recovery route work.
Keep a usable copy of the Borg passphrase or keyfile off the source machine, and preserve any SSH credentials needed to reach a remote repository. SSH authentication and Borg encryption are separate keys with separate recovery duties.
Watch whether Vorta starts and stays running after login; its integrated scheduler depends on the app being open. Check the displayed next run and later archive, especially after sleep, logout or operating-system updates.
Decide retention before enabling pruning, since deleted archives remove historical restore points. Protect any JSON settings export that includes a repository password, and check remote destination charges if using hosted storage.
8 distinct sources behind this profile. Research observed Oct 27, 2026. Features and offers can change.
View sources and research →
