WPX backups and restore options: what site owners should verify

Disclosure: This article contains affiliate links. I may earn a commission if you buy through them. This is a researched guide, not a claim of hands-on testing.

WPX backups and restore options are useful only when you know what was saved and what a restore will replace. The key distinction is between automatic daily backups and a personal backup you create before making a change. Neither should be treated as permanent archival storage.

If this operating setup fits your needs, check the current WPX Hosting offer while you compare the requirements below.

Automatic backups versus personal backups

WPX’s official documentation says automatic daily backups are kept for 28 days. Personal backups are on-demand points kept for 24 hours, take up account disk space, and are limited to one per website at a time. Creating a new personal backup overwrites the previous one.

That means a personal backup is a short-lived working checkpoint. If you need to retain it longer, download it and store it securely outside the hosting account. Do not assume a point created before last month’s redesign will still be there.

What WordPress needs for a full recovery

WordPress uses files and a database. Files include core software, themes, plugins, and uploaded media. The database includes posts, pages, settings, and other application data. A complete restoration often needs both from a compatible point.

Restoring only files may help with a broken theme file, but it will not necessarily undo a database-setting change. Restoring only the database may recover an article, but it can leave the wrong plugin files in place. Diagnose what changed before choosing the restore scope.

For a store or membership site, the database may contain new orders and account activity. Rolling it back can remove legitimate transactions since the backup. Export or preserve new activity where possible and ask support before applying an old point to a live transactional site.

Create a checkpoint before a risky change

Before updating a major plugin, switching themes, or importing content, open the correct website in the WPX control panel’s Backups area. Choose a full personal backup when both files and database are needed. Wait for completion and confirm the point exists.

Download the copy if you need to retain it beyond the 24-hour window. Record the creation time and the change you plan to make. A file called “backup-final” is less useful than a dated copy associated with a specific update.

Keep downloaded backups private. They can contain personal information, configuration details, and credentials. Store them in an access-controlled location rather than a publicly accessible website folder.

Restore from an automatic point

The documented workflow is to select the hosting plan, open its control panel, enter Backups, choose the website, and select an available date under Automatic Backups. Review the restore options before confirming.

WPX distinguishes files and static content, MySQL databases, and mailboxes when included in the account. The page notes that a full-site restore requires selecting the database as well as files. Read the scope rather than trusting a default checkbox to recover everything.

One option empties public_html before restoring. That deletes existing files from the website root and can cause downtime during the process. It may be appropriate for a clean restoration after corruption, but it is not a harmless toggle. Ask support if you are uncertain.

Verify the restored site

• Open the homepage and several article pages.
• Check images and navigation.
• Confirm administrator login works.
• Test forms, email integrations, and transactions as applicable.
• Inspect whether newer content disappeared.
• Clear relevant cache and test logged-out views.
• Confirm the original problem is resolved.

Do not conclude the restore succeeded because the dashboard says it finished. A site can render its homepage while a form, plugin, or database-dependent feature still fails. Test the specific function that prompted the recovery.

Deleted websites require a different path

WPX’s restore guide says deleting a website from the Manage Websites area requires contacting support for restoration. Re-adding the same domain does not necessarily reconnect its previous backups. Tell support what was deleted and approximately when.

Do not treat retention as a guarantee that every deleted or terminated account can be recovered. The provider describes separate policies for those cases. Keep your own copies of important sites, especially before cancellation.

Build a retention policy for your business

A daily recent backup is useful for quick recovery. A monthly independent archive can serve a different need, such as finding a problem discovered late. Your retention should reflect how often you publish, how long errors can remain unnoticed, and whether the site contains transactions.

For an affiliate blog, make additional copies before large content imports and redesigns. For a store, discuss more frequent protection of transaction data. Match the recovery point to the acceptable loss of work rather than assuming “daily” is always enough.

Occasionally test restoration into a safe environment. An untested archive may be incomplete or difficult to use when an emergency arrives. Document who can access the backup and how to request support.

Frequently asked questions

Can I keep a personal backup forever in the panel?

The documented retention is 24 hours. Download it for longer independent retention.

Will restoring files recover deleted posts?

Posts normally live in the database. Select a suitable scope and account for newer content that a database rollback may remove.

Should I restore immediately after suspicious behavior?

First identify and preserve evidence where useful. A clean point may help, but the vulnerability or compromised access also needs attention or the problem can return.

Make recovery an operating routine

Know your retention windows, take a checkpoint before changes, and verify the restore afterward. Backups are a safety mechanism you need to practice using, not just a hosting feature to tick off during purchase.

Next step

Check WPX Hosting through my affiliate link against the requirements above before purchasing. Compare the current checkout and renewal terms, and keep a copy of the offer you accept.

Sources and review date

Official documentation checked October 5, 2026. Features, offers, and account eligibility can change. Editorial recommendations are based on the documented scope, not independent performance benchmarks.

• Automatic restore options
• Personal backup limits
• Managed hosting responsibilities
• Deleted-site recovery

Build the business behind the tools

The tools in this guide are part of a bigger picture. At Ecommerce Paradise, I teach how to build and run a high-ticket ecommerce business. Start with a clear business model, then choose the tools that help you execute it.

If you are still figuring out the model, read my high-ticket dropshipping guide. You will understand the relationship between your store, suppliers, customers, and profit before spending money on software.

For product research, use my high-ticket niches list to explore categories and narrow down your ideas. Go deep before you go wide.

Next, work through my supplier sourcing guide so you know how to research manufacturers and approach them about becoming an authorized dealer.

My business formation checklist helps you organize the legal and financial setup. Use it to prepare your questions and confirm the requirements that apply to your business.

Get help putting the pieces together

If you want me to help you work through your next decisions, check out my private coaching. Bring your actual questions so we can focus on what is holding you up.

If you want a complete business build, take a look at the done-for-you store service. Review the scope and choose the support that fits your situation.