How to Back Up a Website

What a complete website backup includes

A complete website backup is the files and the database taken at the same time. Files are the themes, plugins, uploads, and custom code. The database holds posts, products, users, and settings. Also take .htaccess and wp-config.php, which sit in the account and are easy to skip.

Files without the database bring back an empty shell. A database without the files brings back text with no theme and no images. Give both pieces the same date in the filename so you never restore a mix.

Method	What you save	It worked when
cPanel full account backup	Home directory, databases, and forwarders in one archive	The archive is off the server and is megabytes, not a few kilobytes
cPanel partial	Home directory plus each MySQL database	Both downloads sit in one dated folder and the SQL file is not empty
WordPress plugin	wp-content and the database, sent to other storage	Today's remote files exist, and a spare address loads after a restore
SFTP plus phpMyAdmin	Document root, including hidden files, plus a SQL export	Files go back first, the SQL import creates the tables, and the admin login opens
VPS tar plus mysqldump	Web-root archive and a database dump on another machine	tar lists real files and the SQL dump is not empty

Saving someone else's public pages for offline reading is a different job. That crawl has no database and no hosting account, so it cannot restore a site you run. A backup also does not stop a hack. It is how you recover after one.

How to back up a website in cPanel

On shared hosting, cPanel is the short path to a full website backup. The full account archive packs the home directory, the databases, and the forwarders into one file. Some hosts hide that button. Partial downloads still work if you take both halves.

Log in to cPanel for the account that holds the site.
Open Files, then Backup.
Choose Download a Full Account Backup. If that control is missing, download the Home Directory, then download every MySQL database listed under partial backups.
Leave the destination as the home directory and enter an email address so you know when the job finishes.
Start the backup and wait until cPanel says the job has started. Do not refresh the page in the middle of that click.
When the email arrives, download the archive from the Backup page or File Manager onto your computer. A copy that stays in the home directory is not off the server.
Check the size. A few kilobytes means the job failed. The name should include today's date.

Indian trader monitoring candlestick charts on multiple screens in evening light — how to back up a website

How to back up a WordPress website with a plugin

A plugin is the right tool when you want a schedule and a copy sent off the server without SSH. It has to save the wp-content files and the database. A tool that only exports posts is not a full website backup.

Install one backup plugin from Plugins, then Add New. UpdraftPlus is a common pick. Any plugin that stores files and the database is enough.
Run a backup now. Include the database, plugins, themes, and uploads.
Send the copy to storage that is not this hosting account.
Open that remote folder. Today's files should be there, and they should be larger than a few kilobytes.

You know this worked when a restore onto a spare address loads the site. The WordPress website backup service is the version WebJi® runs for you if you do not want to own the schedule.

How to back up a WordPress website without a plugin

Without a plugin, you take the two halves yourself. Download the files over SFTP. Export the database from phpMyAdmin, or with mysqldump if you have a shell. On a busy site, dump the database first so the file copy is not newer than the content.

Connect with SFTP and download the document root, usually public_html. Show hidden files so .htaccess and wp-config.php are included.
Read DB_NAME in wp-config.php. That is the database to export.
In cPanel open phpMyAdmin, select that database, choose Export, keep the format as SQL, and save the file.
Put the folder and the .sql file in one directory named with today's date.

On a restore, put the files back first, then import the SQL. If the new database user or password differs, edit wp-config.php to match before you test the login.

How to back up a website on a Linux VPS

On a VPS you make the same pair from the shell, then copy it off the machine. Dump the database before you archive the files. A cron job only helps if the destination is another server.

Dump the database with mysqldump and --single-transaction so a live MySQL or MariaDB server is not locked for the whole run.
Archive the web root with tar. Leave cache directories out when they are large and safe to rebuild.
Copy both files with rsync or scp to a different machine. A copy in /root on the same VPS is not off-site.
List the tar contents and check the SQL file is not empty. Schedule the three commands only after that manual run succeeds.

Restore on a spare server or a subdomain first. Putting a cPanel archive back is covered in the cPanel backup restore guide. A VPS restore is the same order: files first, database second.

Where to store a website backup under the 3-2-1 rule

The 3-2-1 rule means three copies, two kinds of storage, and one copy off the live server. The website itself is copy one. Copy two can be a disk or a second server. Copy three must survive the loss of that hosting account.

A full backup left in the cPanel home directory fails the rule. Quota pressure and a hacked account take it with the site. Move it the same day.

What counts as the second medium is spelled out in the 3-2-1 backup rule guide. If you want the off-site copy on a schedule, server backup solutions from WebJi® start at ₹1,300 a month before 18% GST for 200 GB. That price was read on 30 October 2026 and does not include the hosting plan.

How often to back up a website

Back up as often as you would hate to retype the changes. Use the shorter interval when the site does more than one of these jobs.

Orders, bookings, or member posts: every day, and again just before a plugin, theme, or core update.
A blog or catalogue that changes through the week: once a week, plus a copy before any update.
A brochure site that sits still: once a month, plus a copy before you edit it.

Keep three to five recent copies. The newest file is useless if the damage is already inside it. The copy you want is the one from before the bad change.

How to test a website backup before you need it

A file you have never restored is an unverified download. Restore to a subdomain or a spare account, not over the live site. A rollback is this same restore, using the pair from before the bad change.

Put the files in place first, then import the database from the same date.
Point wp-config.php at the database user for that test account if it differs.
Open the homepage, one inner page, and the admin login.
The backup is good when those three load and the content matches the date you saved. Broken styling usually means the files and the database are from different times.

Free migration of an existing site onto WebJi® is available subject to terms and approval. Email support@webji.services before the old host deletes the account. The office phone is not the support line.

Frequently Asked Questions

How do I back up my entire website?

Copy the files and the database from the same moment, then store that pair somewhere other than the live server. A files-only download, or a database export on its own, restores half a site. You are done when a test restore shows the homepage, an inner page, and the admin login.

How do I back up my website in cPanel?

In cPanel open Backup. Use Download a Full Account Backup when it is there, wait for the email, and download the archive off the server. If that button is missing, download the home directory and every MySQL database as separate files, and keep them in one dated folder.

How do I back up WordPress without a plugin?

Download the document root over SFTP, including hidden files such as .htaccess and wp-config.php. In phpMyAdmin, export the database named in wp-config.php as SQL. Restore files first, then import the SQL. Update wp-config.php if the database user on the new server is different.

What is the 3-2-1 backup rule?

Keep three copies of the site, on two kinds of storage, with one copy off the server that hosts the live site. The live site is one copy. A backup sitting in the same cPanel home directory is not the off-site copy, because it dies with that account.

How often should I back up my website?

Match the schedule to how often the site changes. A shop that takes orders needs a daily copy, and another copy before a plugin or theme update. A site that rarely changes can use a monthly copy plus one before any edit. Keep three to five recent copies. The newest file alone is not enough.

Where should I store website backups?

Put at least one copy on a disk or cloud account that is not the hosting server. WebJi® server backup solutions start at ₹1,300 a month before 18% GST for 200 GB if you want that copy on a schedule. That figure was read on 30 October 2026.

How do I roll a website back to an earlier version?

A rollback is a restore of the last files-and-database pair from before the bad change. Restore the files first, then the database from that same time. Do not mix yesterday's files with an older database. Check the homepage, one inner page, and the admin login before you send visitors back.

Does my host's backup replace a copy I keep?

No. A host copy you cannot download, or that lives on the same account, is not a backup you control. Ask how often it runs and how long it is kept, and keep your own off-site pair as well. On WebJi®, scheduled off-site copies are a separate backup service, not something to assume on every hosting plan.