On This Page: [hide]
Three WordPress reset plugins are now closed on WordPress.org, the most recent shut on 19 July 2026 pending review. You have to reach for a plugin at all because WordPress core has never shipped a reset of its own. The button people mistake for one sits on Dashboard > Updates. Re-install swaps your core files and leaves every row of your database exactly where it was. Resetting a site is therefore a choice between four methods. The one you pick decides whether your uploads, your users and your plugin files survive.
Quick answer: Install WP Reset (free, 300,000 active installs), create a snapshot, then reset from Tools > WP Reset. It finishes in about two seconds and leaves your theme and plugin files on disk. Have SSH access? Run wp db reset –yes followed by wp core install instead, and skip the plugin entirely. Cleaning up after a hack? Neither method is enough on its own, because a full reset does not delete a single file.
Last reviewed: Sept. 2026. Plugin versions, install counts, ratings and CVE records verified against WordPress.org and NVD this month.
What “Reset to Default” Actually Means
Three different jobs hide behind that phrase, and mixing them up is how people lose work they wanted to keep.
The first job is a database reset. Your posts, pages, comments, users and every option every plugin ever saved get dropped, and WordPress rebuilds the default tables. Your files never move. Your theme and plugin folders sit exactly where they were, ready to be reactivated. This is what most reset plugins do, and for most people it’s the right job.
Second comes the core file reinstall. WordPress downloads a fresh copy of itself and overwrites wp-admin, wp-includes and the loose PHP files in your web root. Your database is untouched. So is wp-content, and so is wp-config.php. That’s the Dashboard > Updates button, and it fixes a corrupted core, not a messy site.
Third, and bluntest, is a full wipe and reinstall. Files and database both go, and you run the installer from scratch. Nothing survives except what you deliberately copied out first.
Here’s the practical test. Ask what you want back: a blank site with your plugins still installed, or a blank server with nothing on it. The first is a database reset and takes seconds. The second means deleting files, and it takes longer than you think.
Where These Numbers Come From
Every install count, rating and version number below was pulled from the WordPress.org plugin API on 31 August 2026, not from a vendor marketing page. The two CVE records were queried from the NIST National Vulnerability Database the same day. That makes the severity scores the official ones, not a security vendor’s paraphrase. Command syntax was checked against the WP-CLI handbook. And the core versions are whatever the WordPress.org version-check API served that day: 7.1 and 7.0.4.
Our exclusions were blunt. Any reset plugin closed on the directory was cut, which removed three of them. Any plugin not tested against WordPress 7.0 or later was flagged rather than recommended. Version 7.0 shipped in May 2026, and 7.1 followed on 19 August 2026. And we read every changelog to the bottom, not just the top entry. That’s the only reason the discontinuation notice below turned up at all.
What we did not do, and won’t pretend otherwise: run these resets against a live production site with real traffic. The behaviour described for each tool comes from vendor documentation, plugin readmes and official command references. One thing we could not confirm cleanly is the exact free-versus-PRO feature split on wpreset.com. That page builds its pricing and feature table in the browser. Where the readme and the sales page disagree, we quote the readme. SiteGround’s menu paths come from their knowledge base, not from our own account.
Before You Reset: The Two Things That Take Five Minutes
Confirmation prompts are the only thing standing between you and a wiped database. On the command line, a –yes flag removes even those. So build your own undo before you start.
So take a real backup first. Not a snapshot, a backup. The distinction matters more than most guides admit. WP Reset’s snapshots copy database tables into the same database they came from, and the readme says so plainly. Files are not included in any way. If the disk dies or the account gets suspended, the snapshot dies with the site. Snapshots are an undo button for a reset you just ran. Exactly what you want at 2am, and exactly what you don’t want when the server catches fire. They aren’t insurance. Our guide to backing up a WordPress site properly covers the offsite half, and it takes about ten minutes to set up.
Second, write down what you’ll need afterwards. Your admin email and username survive a WP Reset reset, but almost nothing else does. Licence keys, your permalink structure, your Search Console verification method, the SMTP settings behind your contact form. All of it lives in the options table, and all of it goes. Five minutes of copy-paste now saves an afternoon later (ask anyone who has emailed a plugin vendor for a licence key on a Sunday).
Method 1: WP Reset, the 300,000-Install Default
WP Reset holds 300,000 active installs and a 96/100 rating from 1,011 reviews. WebFactory shipped WP Reset 2.08 on 19 July 2026, and that release declares compatibility with WordPress 7.1. The plugin has been in the directory since 17 May 2016. For scale, that install base is 30 times larger than either of its two nearest maintained rivals, both of which sit at 10,000.
The steps take about a minute:
- Install and activate WP Reset from Plugins > Add New, then open Tools > WP Reset.
- Click Create Snapshot and name it. On an average install this takes one to two seconds.
- Scroll to Site Reset, tick the post-reset options you want (reactivate current theme, reactivate WP Reset itself).
- Type reset into the confirmation field. Nothing happens until you do.
- Click Reset Site and confirm the second prompt.
You get logged out, logged back in automatically, and dropped on a clean dashboard. It’s a strange feeling the first time. What’s gone: all posts, pages, custom post types, comments, media library entries and users, plus every default WordPress table and any custom table sharing your wp-config.php prefix.
What survives is the part people misread. No files are touched at all. Your plugins, themes and the entire uploads folder stay on disk byte for byte. Your media files are still there; they just stop appearing under Media in the admin, because the database rows that pointed at them are gone. Site title, WordPress address, site address, language and search engine visibility all come back. So does the account you were logged in as, with the same password.
Pros
- Reset completes in one to two seconds on most sites
- Snapshots give a true one-click undo, downloadable as gzipped SQL
- Free tier includes WP-CLI support and seven separate partial-reset tools
- Security reports run through the Patchstack disclosure programme
Cons
- Vendor states it is not fully tested on multisite
- Snapshots live in the same database, so they are not a backup
- Declares support for PHP 5.2, a floor no supported host still runs
Pricing: the free version does a complete site reset with no limits. WP Reset PRO is listed at USD 49/year for one site, USD 79/year for five and USD 119/year for 100, with a 7-day refund window. You do not need it to reset a site. It buys snapshot offloading to cloud storage, plugin and theme collections, and a multi-site dashboard, which is agency tooling rather than reset functionality.
Best for: anyone who wants a blank site with the plugins and theme still installed, on a single-site WordPress install.
Skip if: you’re on multisite. WebFactory’s own readme says the plugin “has yet to be completely tested with multisite” and advises against resetting the main site.
Verdict: Use WP Reset if you have dashboard access and no SSH, which describes most people reading this. If you do have SSH, Method 2 does the same job in two commands and leaves nothing installed afterwards. And if you’re on multisite, take the vendor’s warning seriously and go straight to the manual route in Method 3.
Method 2: WP-CLI, Fastest If You Have SSH
Two commands and you’re done. No plugin, no dashboard, no confirmation dialogs unless you want them.
The core of it is wp db reset, which runs a DROP DATABASE followed by a CREATE DATABASE using the credentials already in your wp-config.php. Add –yes to skip the prompt. Then wp core install re-runs the five-minute setup from the command line. You pass the site URL, title, admin username, password and email as flags.
The difference from Method 1 is what’s left behind. Method 1 walks you through five GUI steps and finishes with WP Reset still installed and reactivated. This is two commands, and it leaves a database that has never heard of WP Reset. That’s cleaner if you’re handing the site to someone else. Both leave every file on disk untouched, so your plugin and theme folders are still there and just need reactivating.
There’s a softer command worth knowing. wp site empty truncates posts, comments, terms and their metadata while keeping your options and your users. Add –uploads and it deletes the files in the uploads directory too. That’s the right tool when you want to clear content but keep a configured site. No reset plugin’s free tier does quite the same thing. The WP-CLI docs carry one warning: flush your persistent object cache afterwards, or you’ll be reading stale values.
One trap catches people running WP Reset through the command line rather than the dashboard. In the browser, the reset restores the user you were logged in as. Under WP-CLI there is no logged-in user, so it restores the first account with admin privileges it finds in the database. That may not be you.
Pros
- Two commands, no plugin installed and none left behind
- wp site empty covers the “keep settings, drop content” case cleanly
- Same two commands on any host with SSH and WP-CLI
Cons
- No snapshot and no undo of any kind
- Needs SSH, which most entry-level shared plans still don’t include
- Custom tables outside the standard set need hooks to be emptied
Best for: developers resetting a staging or local site between test runs.
Skip if: this is a live site and you haven’t taken a backup, because there is nothing to roll back to.
Verdict: This is the right method for anyone comfortable in a terminal, and the wrong one for everybody else. If typing wp db reset on a production site makes you nervous, that instinct is correct. Use WP Reset instead and take a snapshot first, which gives you the undo this method lacks.