To back up a website in cPanel, download a full or partial backup from the Backup tool, and separately export your databases and key files. Then store at least one copy somewhere other than your hosting account, such as your computer and a cloud drive. A backup that lives only on the same server as the website is not much protection if that server has a problem.
This guide shows a practical routine for a small site on a cPanel plan, with the steps in order and the checks that make a backup trustworthy. Screens differ a little between cPanel versions and server configurations, so look for the same options under slightly different names.
Know what you are backing up
A typical website has three parts. The first is files: themes, plugins, uploaded images and configuration. The second is databases: WordPress posts, pages, settings and users are stored in a MySQL database, not in files. The third is email, if you use mailboxes on the account, plus settings such as forwarders and DNS zones.
A useful backup captures all of them. Beginners often copy only the files and discover during a restore that the posts and settings are missing. Others export only the database and lose uploaded media. Decide up front which parts matter for your site, and cover each.
Who is responsible for backups
Be clear about the responsibility. Lifetime Hosting plans are self-managed, and the terms state that you are responsible for maintaining your own backups, and that no backup frequency or restoration guarantee is stated. The plan listings do not publish a backup schedule. Treat any provider-side copy as a bonus and not as something to rely on.
That is not unusual for shared hosting, but it means the routine in this guide is not optional. If your site earns money or holds work you cannot recreate, backups are part of the running cost, paid in a few minutes of your time.
Step by step: create a full backup in cPanel
- Log in to cPanel and open the Backup tool, or Backup Wizard if that is what your account shows.
- Choose to back up. If a full account backup is offered, it creates one archive of your home directory, databases and settings. Some accounts restrict full backups, in which case use partial backups.
- For partial backups, download the Home Directory backup, then each MySQL database backup, and the email forwarders and filters if you use them.
- Download the files to your computer and wait until each download finishes completely.
- Name the files with the site and the date, for example sitename-2026-11-05, so you can tell which is the newest.
- Copy them to a second location as described below.
If the Backup tool is not available on your account, the manual method below covers the same ground.
The manual method: files and database
For a WordPress site you can build a reliable backup by hand. In File Manager, select the site's document root folder, compress it into a zip archive and download it. Then open phpMyAdmin in cPanel, select the site's database and use Export with the default quick option to download an SQL file.
To find which database the site uses, open the wp-config.php file in the site folder and look at the database name entry. Do not share or paste that file anywhere, because it also contains credentials. If you only need the name of the database, copy only that line.
This pair of a files archive and an SQL export is enough to rebuild the site on any compatible host. It is also the format most migration guides expect, which is helpful if you ever move.
Keep off-site copies
The common advice is the 3-2-1 rule: three copies, on two kinds of storage, with one off-site. For a small website, a practical version is simple. Keep the working site on the hosting account, one copy on your computer and one copy in a cloud storage account you control.
Why not rely on the hosting account alone? Because accidental deletion, a bad plugin update, a hacked site or a server problem can affect everything stored there. Backups stored on the same account can be affected by the same event.
Encrypt or protect backups that contain customer data, since a database export may include names, emails and orders. Store them in a place with a strong password and two-factor authentication.
How often to back up
The right frequency depends on how often the site changes. A brochure site that you edit once a month needs a backup after each edit. A blog with frequent posts or a store with orders needs more frequent database backups, because the database is where new content and orders land.
A simple rule is to ask how much work you would be willing to redo. If losing a week of changes is acceptable, weekly backups are enough. If it is not, back up more often or use a WordPress backup plugin that can run on a schedule and send copies to cloud storage. Check that any plugin you use is compatible with your site and does not overload the account, since the plans have fixed resources.
Also take a backup before risky changes: updating WordPress core, switching themes, changing PHP versions or editing configuration files. It is the cheapest insurance there is.
Test a restore, not just a download
A backup you have never restored is a hope, not a backup. At least once, test that the archive opens, that the SQL file is not empty and that the file sizes look reasonable. Ideally, restore to a test subdomain or a local environment and see whether the site loads.
When you restore for real, upload and extract the files, create an empty database and user, import the SQL file and update the configuration to match the database details. If the domain changed, you may need to update site addresses in the database too. Take it slowly and keep the damaged version until the restored one is confirmed to work.
Our guide to installing WordPress in cPanel explains how the pieces fit together, which makes restores less mysterious.
Backups and migration
A good backup is also your exit plan. If you decide to leave your current host, or move to a Lifetime Hosting plan from another provider, the same files and database export let you rebuild the site elsewhere. After the move, point the domain to the new server as described in point your domain to hosting.
This is also the practical answer to the continuity concern around any pay-once service. We cover the trade-offs openly in is lifetime web hosting worth it: the safest way to use any host, including ours, is to keep your own recent copies and control your own domain.
Which plan do I need for backups
Backups need storage space and some CPU time to create archives. Starter lists 10 GB NVMe, Advanced 30 GB and Turbo unlimited NVMe subject to fair use, with 2 CPU cores and 2 GB RAM on all three, as shown on the plans page. Keep in mind that backup archives stored on the account count toward your usage, so download them and remove old ones rather than letting them pile up.
If you want to understand what the control panel offers, the lifetime cPanel hosting page summarises it. For a WordPress site, the lifetime WordPress hosting page covers the stack.
A simple routine you can follow
Make it a habit that fits your site. Back up files and database before every major change. Download a copy to your computer and one to cloud storage. Keep the last few versions, not just the latest. Delete old archives from the server. Test a restore twice a year. Write the steps down so that someone else could follow them if you are unavailable.
Small steady habits protect a website better than any one clever tool.