How to Safely Reset Your WordPress Site: A Step-by-Step Guide

Emnes April 17, 2026

Circular reset arrow icon representing WordPress site reset

Resetting a WordPress site is one of those tasks that sounds simple until the moment you realize you need to do it for real. A staging site full of test content that you want to wipe before launch. A development install that accumulated weeks of experimentation. A client site you inherited in such a bad state that fixing it would take longer than starting over. A WooCommerce store with thousands of test orders clogging the database before opening day.

Deleting and reinstalling WordPress works, but it’s heavy-handed. You lose your theme, your plugin list, your user accounts, your SMTP settings — everything. A WordPress reset is different: it wipes content (posts, pages, comments, products, customers, media) while keeping the infrastructure (WordPress core, active theme, plugins, general settings) intact. Two minutes instead of two hours.

This guide is a complete walkthrough of how to safely reset a WordPress site in 2026 — from deciding whether you actually need a reset, to backing up first, to choosing what to keep, to verifying everything worked. We’ll cover manual resets, plugin-based resets using Backup Migrate Reset, and the edge cases that trip people up (WooCommerce, multisite, custom tables, media library).

When You Actually Need to Reset WordPress

A reset is the right answer when:

A staging site is going live and is full of lorem ipsum, test users, and dummy products that must not appear in production
A development environment has accumulated weeks of test data and you want a clean slate for a new feature
You’re switching industries or use cases — the site was a blog, it’s becoming a portfolio, and none of the old content applies
You’ve finished demoing to a client and want to hand over a clean install with only the infrastructure and custom work intact
You’re cleaning up after a failed plugin experiment that left database tables and custom post types behind
A WooCommerce store has thousands of test orders and customers from setup and QA that shouldn’t pollute opening-day analytics

A reset is the wrong answer when:

You want to fix a specific plugin conflict — disable plugins one at a time instead
Your site is hacked — restore from a clean backup, don’t reset (the malware may be in files, not the database)
You want a fresh theme — switch the theme, don’t reset the whole site
You want to undo a single bad change — restore a backup of the affected content

Back Up Before You Reset. Always.

A reset is irreversible. The moment you click the confirmation button, everything selected is deleted at the database level — no recycle bin, no undo. Take a full backup before you reset, even if you’re “sure” you don’t need the data.

A proper backup for reset purposes includes:

The database — every table, not just the WordPress default ones (many plugins add their own tables)
The wp-content/uploads folder — your media library
The wp-content/themes folder — so you can restore any custom theme work
The wp-content/plugins folder — especially important for custom or customized plugins
The wp-config.php file — contains database credentials and auth salts

Store the backup off the server you’re resetting. A backup sitting in wp-content/backups doesn’t help you if a reset accidentally nukes that folder. Download it locally, upload to cloud storage, or both.

Our Backup Migrate Reset plugin does this automatically: before any reset operation, it creates a full backup you can restore with one click. Other reputable options include UpdraftPlus, Duplicator, and All-in-One WP Migration. The best backup plugin is the one you actually run, so pick any of them and verify it works.

What a WordPress Reset Actually Does

A proper reset drops and recreates the core WordPress database tables, then reinstalls the initial schema with your current site’s name, URL, and admin user preserved. Specifically:

Reset (deleted and recreated):

All posts, pages, and custom post types (wp_posts)
All post meta (wp_postmeta)
All comments and comment meta
All categories, tags, and custom taxonomies
All media library attachments (database records; files on disk are handled separately)
All users except the current admin (optional)
All plugin-specific tables, depending on the reset tool

Preserved:

WordPress core files
The currently active theme
All installed plugins (still active, with settings intact unless you reset those too)
The site URL, site title, and general settings
The current admin user
The wp-config.php file and database credentials

Good reset tools let you choose which of these to keep and which to wipe. A generic reset might default to keeping all plugins active; a WooCommerce-aware reset might specifically target products, orders, and customers while leaving the WooCommerce settings intact.

Step-by-Step: Resetting WordPress Safely

Step 1 — Put the Site in Maintenance Mode

If this is a public site, drop a maintenance page so visitors don’t hit half-deleted content mid-reset. Even a simple .maintenance file in the WordPress root works. Skip this on true development or staging sites that nobody else accesses.

Step 2 — Take a Full Backup

Not optional. Run your backup plugin of choice, verify the backup file is complete (not zero bytes, not truncated), and download it somewhere off-server. Don’t rely on a hosting-provider snapshot unless you’ve actually tested restoring from one recently.

Step 3 — Decide What to Keep

Walk through your reset plugin’s options and make a deliberate choice for each one. Typical decisions:

Keep the active theme? Usually yes.
Keep inactive themes? Usually no — remove cruft now.
Keep active plugins activated after reset? Yes for a selective reset; no for a deep clean.
Keep the media library files? Yes if you want to reuse images; no if you want a totally fresh install.
Keep users? Just the current admin in most cases.
Keep site title, URL, timezone, language? Almost always yes.

Step 4 — Run the Reset

Confirm the action. Good reset tools require typing a confirmation phrase (e.g., typing “RESET” in capitals) so you can’t trigger a reset by accidentally clicking a button. The actual operation is fast — seconds to a couple of minutes even on large sites, because it’s just dropping and recreating tables, not copying data.

Step 5 — Verify the Reset Worked

Walk through the admin:

Posts section should be empty (or contain only the default Hello World post if you chose that option)
Pages section should be empty (or contain only the default Sample Page)
Users should only contain the admin you logged in as
Media library should reflect whatever you chose — empty, or preserved
Plugins page should show your plugins active (or deactivated, depending on your choice)
Active theme should still be active and configured
Site URL and site title should be unchanged

Visit the front end: the site should render, even if it’s empty. A white screen or fatal error usually means a plugin expected data that no longer exists — reactivate plugins one at a time to isolate.

Step 6 — Clear Caches

Flush every caching layer: object cache (Redis/Memcached), page cache, CDN, and browser cache. Stale caches post-reset can show deleted content for hours and send you chasing bugs that don’t exist.

Special Cases: WooCommerce, Multisite, and Custom Tables

Resetting a WooCommerce Store

WooCommerce stores a lot of data across multiple tables — not just wp_posts but wp_woocommerce_order_items, wp_woocommerce_order_itemmeta, wp_wc_orders (HPOS), wp_wc_customer_lookup, and more. A generic reset plugin that only clears wp_posts and wp_postmeta leaves orphaned data behind.

Use a reset tool that is explicitly WooCommerce-aware, or run WooCommerce’s own built-in tools first (WooCommerce → Status → Tools) to clear orders, customers, transients, and sessions, then run a general reset on top.

Resetting a WordPress Multisite Network

Multisite adds per-site tables (wp_2_posts, wp_2_postmeta, etc.) plus network-level tables (wp_blogs, wp_site). Most single-site reset plugins don’t know about these. On multisite, either:

Reset a single subsite while leaving the network intact (use a multisite-aware reset tool)
Reset the entire network (rare — usually faster to reinstall at that point)

Resetting Sites with Custom Tables

Some plugins (form builders, analytics tools, learning management systems) create their own database tables outside the WordPress core schema. A reset that only targets core tables leaves these behind, sometimes with orphaned references to posts that no longer exist.

List your custom tables before resetting: SHOW TABLES LIKE 'wp_%'; in your database shows everything. Decide for each one: drop it, truncate it, or leave it. Backup Migrate Reset surfaces these tables automatically and lets you choose per-table.

Reset vs Fresh Install vs Restore from Backup

Three overlapping tools for three different jobs:

Reset — fastest. Keeps infrastructure, wipes content. Good for staging-to-production, clearing test data, starting over with the same configuration.
Fresh install — most thorough. New WordPress, new database, empty everything. Good when the existing infrastructure is the problem (hacked, corrupted, unmaintainable).
Restore from backup — precision. Roll back to a specific point in time. Good for recovering from a mistake, failed update, or discovered bug.

Picking the wrong tool turns a five-minute task into a day of cleanup. Match the tool to the need.

Common Mistakes and How to Avoid Them

Resetting without a backup — no undo. Always back up.
Running the reset on the wrong site — easy mistake if you have staging and production bookmarked similarly. Verify the site URL before confirming.
Forgetting to clear caches after — leads to “the reset didn’t work” panic when in fact you’re looking at a cached old page.
Leaving orphaned media files — clearing database records doesn’t remove files from disk. Use a tool that cleans both, or manually clear wp-content/uploads.
Not resetting WooCommerce HPOS tables — leaves ghost orders that show up in reports weeks later.
Resetting with maintenance plugins active — some maintenance plugins block login by IP, and if you reset user settings you may not recognize yourself. Disable maintenance-mode-locking plugins before reset.

Frequently Asked Questions

Will resetting WordPress delete my plugins?

A proper reset does not uninstall plugin files or delete their database entries; it wipes content (posts, comments, users) while leaving plugin code and settings alone. You can choose to also deactivate plugins as part of the reset, but the files remain.

Can I reset WordPress without deleting images?

Yes. Good reset tools let you keep or wipe the media library independently. Choose “keep media” to preserve uploaded files on disk, though the attachment records in the database will still be cleared — you may need to re-attach them to new content.

How long does a WordPress reset take?

Seconds to a couple of minutes for most sites. The operation is dropping and recreating tables, not copying data. WooCommerce stores with millions of orders may take longer; very large media libraries (if you’re also clearing files on disk) take longer still.

Can I reset WordPress without a plugin?

Yes — drop all tables in phpMyAdmin or via wp db reset (WP-CLI), then re-run wp core install. This gives you the most control but also the most room for error. For most people, a plugin-based reset with a safety net is the better choice.

Is resetting WordPress the same as reinstalling?

No. Reinstalling replaces WordPress core files. Resetting clears content from the database. Most people say “reinstall” when they mean “reset” — make sure you know which one you actually need before starting.

Keep the Infrastructure, Clear the Content

Resetting WordPress is one of those tools that feels dangerous until you’ve done it twice and boring after that. The important parts are the safety rails: take a real backup, verify it, make deliberate choices about what to keep, and confirm the result before declaring the job done.

Our Backup Migrate Reset plugin bundles backup, migration, and reset in one tool so you never reset without a current backup available. The Pro version adds WooCommerce-aware resets, scheduled backups with off-site storage, and one-click migration between environments. Try it on a staging site first — that’s exactly what it’s for.