cPanel ships with a backup system included in the license. JetBackup is a paid add-on. The interesting question is not "which is better" — that depends on the workload — but "where does each one win, and at what cost?" This article lays out the honest tradeoffs so you can decide based on your account count, your customer expectations, and your storage budget.
The short version: cPanel's built-in is fine for small servers where backups never get restored. JetBackup earns its license fee the first time a customer requests a single-file restore at 11pm on a Saturday.
At a glance
| Capability | cPanel built-in | JetBackup 5 |
|---|---|---|
| Incremental backups | No — full account dump every cycle | Yes, via JetEngine snapshots (hard-links + dedupe) |
| Disk usage for 30 daily snapshots | ~30x account size | ~1.2-1.5x account size for typical churn |
| Retention granularity | Daily, weekly, monthly slots (fixed) | Hourly, daily, weekly, monthly, custom — per job |
| Destinations | Local + a handful: FTP, SFTP, rsync, S3, Google Drive | Local, SFTP, FTP, S3, Wasabi, B2, Google Drive, Azure, custom DOs |
| End-user self-service restore | Whole-account only, requires reseller/WHM nudge | File, folder, email, database, DNS, cron — all in cPanel UI |
| Restore granularity (admin) | Account, home dir, MySQL DB, mail | Down to individual file, single email message, one DB table |
| Backup integrity verification | None built-in | Per-snapshot checksum, automated verify jobs |
| Compression | Yes (gzip), full archive only | Yes, per destination, on incremental deltas |
| Encryption at rest | Not in core (transport only) | Yes, per destination |
| WHM transfer-tool compatibility | Native — pkgacct format | Yes — JetBackup exports pkgacct on demand |
| License cost | Included with cPanel | $4-12/server/month typical, sliding by account count |
Where cPanel built-in wins
Cost. It is in the box. For a personal server, a low-margin reseller, or anything where backups are insurance you genuinely hope never to use, the price is right.
Simplicity. Enable in WHM → Backup Configuration, point at local or a remote target, done. There is no second daemon to monitor, no separate UI, no destination concept. If your monitoring stack has limits, fewer moving parts has value.
Transfer-tool native. The output is pkgacct-format tarballs, which is exactly what the WHM Transfer Tool consumes. JetBackup does this too, but with one more click.
Compatible with everything. Every cPanel backup tool ever written accepts the cPanel-native format. JetBackup's snapshot format is portable, but it is its own thing.
Where JetBackup wins
Storage efficiency. This is the headline. cPanel built-in writes a full tarball every cycle — 30 daily backups of a 10 GB account is 300 GB. JetBackup's JetEngine uses hard-links on the source side: only changed files take new space, so 30 daily snapshots of the same account land at roughly 12-15 GB. On a 50-account server the difference is multi-terabyte and shifts the whole storage budget.
End-user self-service. A cPanel user with JetBackup sees a JetBackup 5 icon in their account, browses snapshots, and restores a single file by ticking a box. With cPanel built-in, restoring one file means opening a support ticket, the admin restoring the whole account to a staging path, and copying the file out manually. The labour cost difference compounds quickly.
Granularity at restore. Restore a single file from a JetBackup snapshot in 30 seconds. Restore one email out of a 50,000-message inbox. Restore one DNS record. Restore one row from a database table by exporting a single table. cPanel built-in's smallest unit is "the entire MySQL database" or "the entire home directory".
Destinations. JetBackup speaks every S3-compatible API plus B2, Azure Blob, and any SSHFS-mounted filesystem. cPanel's destinations list is shorter and the S3 implementation does not support Wasabi cleanly — it works but has known signing edge cases.
Multiple destinations per job. Want local hourly retention plus Wasabi daily for offsite? One JetBackup job with two destinations. cPanel needs two separate backup runs.
Verify jobs. JetBackup can periodically restore random snapshots to a scratch directory and checksum the result. Catches silent corruption — a thing that does happen, and that you discover at the worst possible time without verification.
Where neither wins
Neither product handles application-aware backups. WordPress, Magento, and Moodle all benefit from a flush-buffers step before the database dump, which neither does without a custom hook. For mission-critical apps, layer Softaculous backups on top.
Neither handles point-in-time recovery at the MySQL transaction level. If you need RPO measured in seconds, you want binlog replication to a replica, not nightly backups from either product.
Neither does bare-metal restore. Both back up cPanel accounts. Reinstalling the OS, cPanel, EasyApache, and customisations is on you.
The decision
Pick cPanel built-in if:
- You run fewer than 20 accounts and disk is cheap.
- Customers do not have access to request restores themselves.
- Backups are insurance you have never actually used.
Pick JetBackup if:
- You run 50+ accounts and storage cost matters.
- Customers do request restores, even occasionally.
- You need offsite to S3, Wasabi, or B2.
- "How long did it take to restore that one file" is a metric anyone tracks.
The crossover is roughly 30 accounts on average-sized hosting. Below that, cPanel built-in is fine. Above it, JetBackup's storage savings alone usually cover the license fee, and the self-service restores are free upside.
Next steps
- Buy or trial at JetBackup licensing.
- Adding S3-compatible storage? See JetBackup 5 destinations for cPanel.
- Already running JetBackup? Disable cPanel built-in backups so you stop paying for both.