The safe way to clean a WordPress database is to make and verify a complete backup, identify the installation’s actual table prefix, inspect records and table ownership, remove only data you can positively classify as disposable, optimize during a quiet period, and test the site afterward. Routine cleanup is not the same as repairing corruption: repair tools are for reported table errors and should be used only with a fresh backup.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What database cleaning can—and cannot—do
A WordPress database stores posts, pages, revisions, comments, users, settings, plugin data and cached values. Over time, revisions, auto-drafts, trashed comments, expired cache rows and data left by removed plugins can make tables larger and harder to manage. Cleaning removes confirmed disposable records and helps you understand what is consuming space.
As an Amazon Associate I earn from qualifying purchases.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteIt does not guarantee a particular speed increase. No authoritative source establishes a universal table-size threshold, cleaning interval or percentage improvement. A site can remain slow because of an inefficient query, an overloaded server, a poorly behaved plugin, missing indexes or external services even after old rows are deleted. Treat cleanup as data housekeeping and risk management, then use query profiling and error logs for performance diagnosis.
- Cleanup: removes records that your retention policy and plugin ownership checks identify as unnecessary.
- Optimization: asks the database engine to reorganize table storage after changes; it is not a substitute for backups or query tuning.
- Repair: attempts to fix a crashed or corrupt table after the database reports a problem.
Back up the whole site before changing a row
WordPress advises keeping a current database backup. A database export alone is not a complete restore of a site: the database and the WordPress files belong together as one backup set. Keep the export with copies of wp-content (including uploads), core files, the active theme and configuration, and retain at least one copy away from the live server.
#1 Best Overall
- 110 Sheets Log Book: This vehicle maintenance log book includes 110 record sheets to track repairs, services, fuel costs, and other vehicle-related expenses. It also comes with 36 convenient “Service Due” stickers to help remind you of upcoming maintenance schedules. Everything you need to keep your car records organized in one place.
- Detailed Information: Each page is carefully structured with dedicated sections for date, mileage, service description, parts replaced, vehicle information, cost, and additional notes. The clear and organized format allows you to maintain accurate records, monitor repair history, and better manage long-term vehicle performance and expenses.
- Enough Writing Space: The record sheets provide ample space for clear and thorough entries. Whether you’re documenting routine oil changes or major repairs, there’s plenty of room to write detailed information without feeling cramped.
- Easy to Use: The spiral binding allows the notebook to lay flat for comfortable writing, making entries quick and convenient. The included 36 “Service Due” stickers can be placed inside the book or on visible surfaces like your windshield or dashboard, helping you keep important maintenance reminders in sight.
- Proper Size: This compact logbook measures 5.5” x 7.1”, which fits easily in your glove compartment, center console, backpack, or desk drawer. Its portable size ensures you can access and update your vehicle records anytime, whether at home, in the garage, or at the service center.
Export with phpMyAdmin
- Open the database assigned to the site in phpMyAdmin.
- Choose Export, select all WordPress tables, and use the SQL format.
- Use the custom export options when available so routines, structure and data are included as appropriate for your host.
- Download the file. A compressed
.gzor.bz2dump is normal and saves storage; do not edit the compressed file by hand. - Record the export date, WordPress/PHP/MySQL or MariaDB versions and the table prefix in a separate note.
Export with WP-CLI
From the WordPress installation directory, run:
wp db export /secure/path/site.sqlUse a path that is not publicly served. Confirm that the file exists, has a plausible size and can be read by your backup process. A backup is not verified merely because an export command completed; periodically restore a copy to staging and check that it opens.
Prepare a safer maintenance window
- Clone the site to staging or take a hosting snapshot before destructive work.
- Pause imports, queue workers, scheduled bulk edits and other high-write jobs so the before-and-after comparison is meaningful.
- Keep the pre-cleanup export until the site has operated normally through a representative period.
- Never perform the first deletion pass on a production database when a staging copy is available.
Find the real table prefix before inspecting anything
Do not assume tables begin with wp_. WordPress stores the prefix in $table_prefix inside wp-config.php. A custom prefix is common for security, and multisite installations use additional site-specific table names. Sites sharing one database can contain several unrelated prefixes.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRead the value in the configuration file, then list tables rather than guessing names. WP-CLI provides an inventory without requiring you to hand-write SQL:
wp db tables
wp db size
wp db columnsIn phpMyAdmin, sort the table list by size and note row counts. Match every table to the prefix you found. A table with a familiar suffix but a different prefix may belong to another application and must not be altered.
Inventory the tables and identify ownership
Make a before-and-after record of table name, engine, approximate size, row count and suspected owner. Core tables commonly include posts, post metadata, comments, comment metadata, terms, term relationships, users, user metadata and options, but plugins and themes can create their own tables. The name alone is not proof of ownership.
Use the active and retired plugin list
Compare custom table names with the active plugins, previously installed plugins and theme documentation. Check whether a plugin has an uninstall routine or a setting that controls data removal. A plugin that was deactivated may still be required for historical records, a custom post type or a migration. Export a table before removing it, and delete leftovers only when you know no current code reads them.
Inspect before deleting
- Look at representative rows and column names, not just the table size.
- Search option names and metadata keys for the component that created them.
- Check timestamps and status fields against the site’s retention policy.
- Confirm that no scheduled job, integration, custom post type or legal requirement depends on the records.
- Prefer the WordPress admin’s moderation and deletion controls when they exist; they apply application-level checks that a raw SQL delete bypasses.
Never run a broad DELETE without a narrowly tested condition and a restorable backup. If you must use SQL, first run the equivalent SELECT, save the result, and check the affected row count.
Rank #2
- All In One Equipment Maintenance Log Book With Detailed Fields：This equipment maintenance log book is designed for complete tracking of machinery and equipment performance Featuring pre-printed sections for Equipment Name Manufacturer Name Model Number Serial Number Purchase Date Item Location and Additional Information this repair log book ensures accurate and consistent service records
- Includes Maintenance Schedule Fields for Time and Task Recording：Each page includes dedicated spaces for Date and Time Maintenance Task or Remarks Performed By and Cost helping you record maintenance frequency track service intervals and monitor expenses Ideal for preventive maintenance logs and repair history documentation
- Large Format Repair Log Book With Continuation Pages：Sized at 8.5 x 11 inches this equipment service record notebook provides generous space for writing and includes 110 Pages with continuation pages to extend entries when needed Ensures that even complex service reports are kept complete and organized
- Durable Spiral Bound Construction for Long Term Use：Built with a 300gsm laminated cover and strong spiral binding this maintenance log notebook lies flat for easy writing and endures frequent handling in demanding environments from factory floors to fieldwork sites
- Ideal for Industrial Commercial and Personal Equipment Tracking：Whether you’re managing heavy machinery in construction agricultural tools in farming or facility systems in schools or warehouses this maintenance record book helps technicians engineers and facility managers maintain consistent and accessible logs
Clean the main growth areas
wp_options: autoloaded settings and transient rows
The options table is loaded frequently, so large autoloaded values can consume memory on many requests. Inspect the option name, serialized value, size and owner. An unfamiliar name is not a reason to delete it: active plugins may use opaque keys, and removing one can reset configuration or break a feature.
Transients are temporary cached values exposed through WordPress’s Transients API. Without persistent object caching, they are typically stored in wp_options. Expiring transients are generally not autoloaded by default, while transients created without an expiration are autoloaded. Persistent object caching can move transient storage outside the database, so an empty search in wp_options does not prove that no transients exist.
- Remove an expired transient only after confirming its key and owner.
- Do not delete a non-expiring option merely because it resembles a transient; it may be deliberate configuration.
- Use the plugin’s own cache-clearing or uninstall procedure when available.
- After deleting cache rows, expect them to be recreated as pages and jobs run.
wp_posts: revisions, auto-drafts and trash
Review old revisions, abandoned auto-drafts and posts or pages in the trash according to the site’s retention policy. Revisions can be useful for editorial recovery, audits and compliance, so choose a retention period deliberately rather than deleting every revision by default. Check custom post types as well as standard posts; a plugin may store important workflow history there.
Free tools Windows power users keep installed
One-click scans. No signup required.
Auto-drafts that are clearly abandoned and trash that has passed the site’s retention period are usual candidates, but verify status, author and dates before removal. Take extra care on membership, ecommerce, learning and support sites where a post-like record may represent an order, lesson or ticket.
wp_postmeta: orphaned metadata
Metadata becomes orphaned when its referenced post no longer exists, but a row that looks orphaned can still be part of a migration or a custom relationship. Identify the metadata key and the code that reads it before deleting anything. A safe review compares the metadata’s post IDs with existing posts and then checks active plugins and custom post types for legitimate use.
Comments and comment metadata
Use WordPress moderation screens to process spam and trash. Preserve comments required for legal, contractual, support or editorial reasons. Comment metadata can be reviewed after the parent comment is confirmed gone, but do not assume every unrecognized key is disposable.
Plugin and theme tables
Custom tables often contain logs, form entries, analytics, queues or settings that are not represented in core tables. Determine the owner from active and previously installed code, read its uninstall documentation and export the table before removal. If ownership is uncertain, leave the table in place and monitor its growth rather than guessing.
Repeatable WP-CLI checks and operations
WP-CLI makes inventory and exports repeatable and easier to document:
wp db check
wp db tables
wp db size
wp db columns
wp db export /secure/path/site.sql
wp db optimizeRun wp db check before and after maintenance to ask the database server to check table health. Run wp db optimize only after confirmed disposable data has been removed and during a low-traffic window. Review the command output and your host’s database-engine guidance first; optimization can require temporary locks or additional disk space.
Commands that remove tables or reset a database are exceptional, destructive operations:
wp db clean
wp db drop
wp db resetDo not use them as routine housekeeping. They can remove plugin tables or the entire database, and recovery depends on a tested backup.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Optimize tables without mistaking it for a cure-all
- Finish the backup and verification steps.
- Complete the inspection and deletion pass, recording every table and condition changed.
- Confirm the database engine and hosting provider’s guidance on optimization and available disk space.
- Run
wp db optimizeor the equivalent maintenance action during a quiet period. - Clear application, page and object caches so you test current data rather than stale responses.
- Compare table sizes, autoloaded data and error logs with the baseline you recorded.
Optimization does not repair a plugin that continually writes junk data, add a missing index, fix a slow external request or replace query profiling. If the same table grows rapidly again, identify the writer and change its retention or logging settings.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When and how to repair a damaged table
Repair is for an error such as a crashed or corrupt table, not for routine cleanup. Take a fresh backup before attempting it. In phpMyAdmin, select the affected table or tables and choose Repair Table. Read the result and check the site rather than assuming that a successful message means every application-level problem is resolved.
Emergency WP_ALLOW_REPAIR procedure
WordPress documents an emergency repair page at /wp-admin/maint/repair.php. To enable it, add define( 'WP_ALLOW_REPAIR', true ); to wp-config.php, visit the repair page on the site, and choose the appropriate repair action. This page can be reachable without a normal login, so enable it only for the shortest possible window, restrict access at the server if feasible, and remove the setting immediately after the attempt. Take another backup before trying a second repair method.
If repair fails, the database server reports continuing corruption, or multiple tables are affected, stop destructive experimentation and involve the host or a database professional. Restore the known-good backup to staging first, then plan a controlled production recovery.
Manual tools, plugins and hosting automation
Manual phpMyAdmin and WP-CLI work gives you direct review and a clear audit trail. A maintenance plugin can make discovery, scheduling and common cleanup tasks more convenient, but its suggested deletion list still requires human validation, particularly for orphaned options and custom tables. WordPress housekeeping documentation names WP-Sweep as one plugin option. WP-Optimize advertises cleanup features and requires a full database backup before first use or major upgrades.
| Approach | Strengths | Risks and checks |
|---|---|---|
| phpMyAdmin | Visual table sizes, row inspection, exports and the Repair Table action. | Easy to select the wrong prefix or run an irreversible query; verify the database and export first. |
| WP-CLI | Repeatable inventory, exports, health checks and scripted maintenance. | Commands run with powerful privileges; protect paths and treat clean, drop and reset as destructive. |
| Cleanup plugin | Convenient review screens, common cleanup rules and possible scheduling. | Ownership detection can be imperfect; review every proposed deletion and confirm restore capability. |
| Hosting snapshot or backup service | Can provide off-site retention and a broader file-plus-database restore point. | Confirm retention, encryption, access controls, support response and that restores are actually tested. |
Choose the method that gives you a restorable backup, a review or dry-run step, ownership visibility, multisite awareness, logging and a practical way to undo a mistake. Convenience is not a reason to skip those controls.
Post-cleanup verification checklist
After cleanup, optimization or repair, clear relevant caches and exercise the workflows that write to or read from the database:
- Open the homepage, several representative content pages and the search function.
- Log in and out, open the dashboard and edit, save, schedule and publish a test item.
- Upload media and confirm thumbnails and attachment metadata are available.
- Submit forms and verify that entries, notifications and integrations still work.
- Check comments, spam moderation and trash behavior.
- Run an ecommerce checkout or other transaction test when the site handles payments or orders.
- Review scheduled events, queue workers, imports, REST/API integrations and webhooks.
- Inspect PHP, web-server and database error logs for new warnings.
Keep the original export until these checks pass and the site has completed a representative cycle of scheduled jobs and normal editorial activity.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →How often should you clean?
There is no authoritative universal interval. Base the review on write volume and change cadence: a busy publishing or ecommerce site may need more frequent observation than a small brochure site. Monitor table growth, autoloaded data, query performance, backup success and error logs. Schedule a review when those signals or a known migration indicate a need, rather than deleting rows on an arbitrary calendar.
Quick Recap
A safe decision sequence
- Can you restore? If not, stop and create a complete, verified database-and-files backup.
- Is the table yours? Confirm the configured prefix and ownership before selecting it.
- Do you know what each row represents? Inspect names, statuses, dates and references; unfamiliar does not mean useless.
- Is deletion required? Prefer retention settings, WordPress moderation tools and plugin uninstall routines.
- Can you test the result? Use staging where possible, run the verification checklist and retain rollback evidence.
- Is there an actual corruption error? Only then use Repair Table or the temporary emergency repair page.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
