How to Back Up Your Website Files in cPanel
A website backup is a separate copy of the files, databases and account settings that make a site work. If an update fails, a plugin corrupts content or an accidental deletion affects your hosting account, that copy can save hours of rebuilding.
HostGator customers can create and download backups through cPanel, the control panel used for many everyday hosting tasks. The process is suitable for WordPress sites, small business pages, online shops and static websites hosted on a shared plan.
Backing up website files in cPanel is straightforward, but the safest approach is to understand what each backup contains. A home directory archive may include website files and email data, while a database export is needed for WordPress posts, pages, settings and customer records.
Australian businesses also need to think about practical storage and compliance matters. A café in Melbourne, a trades business in Perth or an online retailer serving Sydney customers may rely on its site every day, so a backup should be stored away from the hosting account and tested before it is needed.
| Backup option | What it includes | Best use | Main limitation |
|---|---|---|---|
| Home directory backup | Website files, email folders and account files | Keeping a broad copy of hosting data | May not include a separate database export |
| Full account backup | Home directory, databases and account configuration | Disaster recovery and migration | Restoration may require HostGator support |
| File Manager archive | Selected folders such as public_html |
Quick copy of specific site files | Does not automatically capture databases |
| Database export | MySQL or MariaDB data | WordPress and other database-driven sites | Cannot restore missing theme or media files by itself |
What A cPanel Backup Covers
The main website files are usually stored in the public_html directory, although an addon domain may use a different document root. This folder can contain WordPress core files, themes, plugins, images, JavaScript, CSS and configuration files. A static HTML website may have nearly everything it needs in this location.
A database is a separate component. WordPress content, menu settings, user accounts and many plugin settings are stored in MySQL or MariaDB rather than inside public_html. A file archive without a database export may restore the appearance of a site but leave out its articles, products or configuration.
Email can also be part of the hosting account. If your domain uses cPanel mailboxes, messages may be stored within the account’s mail directories. Confirm what your backup includes before deleting or moving anything, particularly if staff use webmail for daily business correspondence.
A full account backup usually creates one compressed archive containing a broad range of account data. On some HostGator plans, the customer can generate and download the archive but cannot restore it directly through cPanel. Restoration rules vary by plan, so keep the original file intact and check the support documentation if a recovery becomes necessary.
Prepare Your Account Before Downloading
Start by checking the current account status. Confirm that the website loads correctly, identify the main domain and addon domains, and note where each site’s document root is located. This makes it easier to recognise the right folders when selecting individual files.
Log in to cPanel through the HostGator customer area or your usual secure login address. Under the Files section, look for Backup or Backup Wizard. The exact appearance can vary with the cPanel theme, and the cPanel theme guide can help you recognise the relevant controls if your interface looks different.
Before creating an archive, remove temporary files that do not need to be preserved, such as old installation packages, cache archives or previous backup files stored inside the web directory. Do not delete anything unless you know its purpose. A backup made immediately before a major update should preserve the live site as it exists, including essential hidden files such as .htaccess.
Check available disk space in cPanel as well. A compressed backup may still require temporary working space while cPanel builds it. If the account is close to its quota, remove known clutter or contact HostGator support before starting the process.
Create A Full Account Backup
In cPanel, open Backup or Backup Wizard and choose the option for a full account backup. Select the destination offered by your plan, usually the home directory, unless you have a secure remote destination configured. A remote destination can be useful because it keeps the first copy separate from the hosting account.
Enter an email address for completion notifications if the interface provides that field. Large accounts may take time to package, especially when they contain video, high-resolution photographs or years of email. Avoid starting several backup jobs at once, as this can consume resources and make the account harder to manage.
When cPanel finishes, return to the backup area and download the generated archive to your computer. The filename commonly includes the account username and creation date, which helps identify it later. Save the archive outside the public web directory so visitors cannot access it through a guessed address.
A downloaded backup is only the first copy. Store another copy on an external drive or a reputable cloud storage service, using a clear naming system such as example-au-full-2025-03-08. If the business operates in Australia and has contractual or privacy obligations, check where the cloud provider stores data and who can access it.
Save Individual Website Files
An individual file backup is useful when you need a quick copy before editing a theme, updating a plugin or changing a configuration file. Open File Manager in cPanel and navigate to the correct document root, often public_html. Select the required folders and files, then use Compress to create a ZIP archive.
For a WordPress site, include the complete installation if you want a standalone file copy. At minimum, this normally includes the WordPress files, wp-content, .htaccess and wp-config.php. The wp-content directory holds themes, plugins and uploaded media, so it is especially important for preserving the site’s customised elements.
After the archive has been created, select it in File Manager and choose Download. Once the file is safely stored elsewhere, you can remove the temporary ZIP from the hosting account if it is using substantial quota. Never leave a backup archive in a public directory longer than necessary because it may contain configuration details.
A file-level copy is particularly useful for small brochure sites, landing pages and development work. For a full WordPress recovery, pair it with a current database export. Keeping files and database data from roughly the same time gives you a more consistent restoration point.
Back Up Databases And Email
To export a database, open phpMyAdmin from cPanel and identify the database used by the site. WordPress users can check the database name in wp-config.php, while other applications may list connection details in a configuration file or administration panel. Select the database, choose Export, use the Quick method with SQL format, and download the resulting file.
For larger or more complex databases, the Custom export option can provide greater control. Keep the default structure and data selections unless you have a specific reason to change them. Give the downloaded file a descriptive name and store it with the matching website archive.
If your domain uses cPanel email, decide whether messages need to be retained separately. The account backup may include mailbox data, but a dedicated mail export or local mail client copy can provide an additional safeguard. Guidance on setting up email accounts is useful when you need to recreate addresses after a migration or account change.
Remember that DNS records are not always covered in the same way as website files. Record important settings such as MX records, TXT verification entries, SPF, DKIM and DMARC values. This information helps restore mail delivery and third-party services if the domain is moved or the account is rebuilt.
A Practical Backup Routine
A reliable schedule should reflect how often the website changes. A local community organisation with occasional updates may need a weekly or monthly copy, while an online shop processing orders every day requires more frequent protection. Keep at least one recent backup and one older version in case a problem remains unnoticed.
Use the following checks before each major backup:
- Confirm the site and key forms load correctly
- Check the account has enough storage quota
- Record the backup date and website version
- Include files, databases and relevant email data
After downloading, apply a simple storage routine:
- Keep one copy outside the hosting account
- Store a second copy on separate media or cloud storage
- Restrict access to archives containing private information
- Delete obsolete public copies from web directories
For businesses in Brisbane, Adelaide or regional areas, internet performance can vary with local NBN conditions and busy upload periods. A large archive may be more practical to download overnight, using Australian Eastern Standard Time or Australian Eastern Daylight Time as appropriate. Smaller file and database exports can be completed separately when a full archive is inconvenient.
If you manage several customer sites, a short skills resource such as this hosting learning course can complement the day-to-day cPanel workflow. The key is consistency: label every copy, document its contents and avoid relying on memory during an emergency.
Verify And Store Copies Safely
A backup should be checked, not simply created and forgotten. Confirm that the archive appears complete, opens without an error and has a sensible file size. A zero-byte download or unexpectedly tiny archive can indicate that the process failed or that the wrong folder was selected.
For a file backup, open the ZIP and inspect representative folders such as wp-content/uploads, theme files and configuration files. For a database export, open the SQL file in a text editor and check that it contains database statements and recognisable site data. Avoid editing the export unless you have a specific technical reason.
The strongest test is a restore to a separate staging account or local development environment. Restore the files and database, update the configuration details, and check the home page, internal links, images, forms and login. This confirms that the backup is usable before the live website suffers a problem.
Keep a simple record with the date, domains included, database names, storage location and any exclusions. If a site handles Australian customer information, limit access to backup files and use encryption where available. Begin by opening cPanel, creating a dated full account backup, downloading it, and saving a second copy outside the hosting account.