A healthy WordPress database size typically sits between 10 MB and 100 MB for standard content sites, and 100 MB to 500 MB+ for active WooCommerce stores. When your database balloons well beyond that range, often hitting 800 MB or several gigabytes on sites with modest traffic, the culprit is rarely your actual blog posts or product pages. Instead, silent table bloat from post revisions, expired transients, orphaned metadata, and Action Scheduler logs is weighing down every query.
In this guide, you will learn four ways to check your exact WordPress database size in under two minutes, identify which tables are consuming the most disk space, and safely shrink your database without risking live site data.
What Is a Normal WordPress Database Size?
Before deleting anything, compare your current database footprint against typical benchmarks for WordPress installations:
| Site Type | Typical Database Size | Warning Signs of Bloat |
| Small Blog / Brochure Site (< 200 posts) | 10 MB – 50 MB | Over 150 MB with few media/post entries |
| Established Content / Membership Site | 50 MB – 250 MB | wp_postmeta or wp_options larger than wp_posts by 5x+ |
| Active WooCommerce Store | 150 MB – 1 GB+ | Tens of thousands of expired _transient_ rows or completed actionscheduler_logs |
Size alone does not slow down WordPress, unindexed bloat inside high-traffic tables does. Even a 40 MB database will crawl if wp_options carries several megabytes of autoloaded transient data on every page load.
4 Ways to Check Your WordPress Database Size
1. Check Inside WordPress Site Health (No Tools Required)
WordPress includes a built-in storage breakdown directly inside the admin dashboard:
- Log in to your WordPress dashboard and go to Tools > Site Health.
- Click the Info tab at the top.
- Expand the Directories and Sizes section.
- Look at the Database size row to see your total database footprint alongside your uploads and theme directories.
Limitation: Site Health only shows the combined total, it will not tell you whether wp_postmeta, wp_options, or an abandoned plugin table is causing the spike.
2. Inspect Individual Table Sizes in phpMyAdmin
If you host on cPanel, Namecheap, or a standard LAMP/LiteSpeed stack, phpMyAdmin gives you a table-by-table breakdown:
- Open phpMyAdmin from your hosting control panel and select your WordPress database in the left sidebar.
- Click the Size column header twice to sort all tables from largest to smallest.
- Check the Overhead column as well, high overhead indicates fragmented free space left behind after repeated row deletions.
3. Run an information_schema SQL Query (Exact MB Breakdown)
To see both Data Size, Index Size, and Row Count per table in a single query, query the MySQL INFORMATION_SCHEMA.TABLES metadata table in phpMyAdmin’s SQL tab (replace your_database_name with your actual DB_NAME from wp-config.php):
SELECT
table_name AS `Table`,
table_rows AS `Approx_Rows`,
ROUND((data_length + index_length) / 1024 / 1024, 2) AS `Total_Size_MB`,
ROUND(data_length / 1024 / 1024, 2) AS `Data_MB`,
ROUND(index_length / 1024 / 1024, 2) AS `Index_MB`
FROM information_schema.TABLES
WHERE table_schema = 'your_database_name'
ORDER BY (data_length + index_length) DESC;
(Tip: If you customize or combine SQL audit queries before running them on production, validate the syntax first with our free SQL Query Checker so a typo never disrupts your session.)
4. Check via WP-CLI Over SSH
If you have SSH access to your server, the official WP-CLI wp db size command returns your total database size and individual table sizes in seconds:
# Total database size in human-readable format
wp db size --human-readable
# Table-by-table size breakdown
wp db size --tables --human-readable
The 5 Biggest Causes of WordPress Database Bloat
When one or two tables dominate your size report, the extra megabytes almost always come from five sources:
- Unlimited Post Revisions (
wp_posts): Every time you click Save Draft or Update, WordPress stores a complete copy of the post. A 2,000-word article edited 40 times creates 40 full duplicate rows. - Orphaned Post & User Metadata (
wp_postmeta): Deleting posts, products, or plugins often leaves behind thousands of orphaned meta rows that no longer belong to any active record. (See our guide on How to Clean wp_postmeta: Fixing Orphaned WordPress Post Meta.) - Expired Transients (
wp_options): Plugins cache temporary API responses and status checks inwp_options. When transients expire without being purged, or get markedautoload = 'yes', they bloat both disk size and TTFB. (Learn more in How to Speed Up a WooCommerce Database: Clearing Transients and wp_options Bloat.) - Action Scheduler Logs (
wp_actionscheduler_logs&wp_actionscheduler_actions): WooCommerce, Rank Math, and backup plugins queue background tasks via Action Scheduler. On busy sites, completed and failed log rows easily pass 500,000 entries. - Leftover Tables from Uninstalled Plugins: Deactivating and deleting a plugin rarely drops the custom tables it created, leaving dead data behind permanently.
How to Reduce Your WordPress Database Size Safely
Before running any cleanup on a live database, take a full database backup so you can roll back immediately if needed. (If you prefer running manual queries, follow our checklist in How to Safely Run a WordPress SQL Cleanup Script.)
Step 1: Audit & Sweep Junk Rows with DWV Database Bloat Cleaner
Running raw DELETE queries on wp_postmeta or wp_options carries real risk if a JOIN condition or prefix is slightly off. Instead, you can scan and clean known bloat categories safely with DWV Database Bloat Cleaner:
- Install and activate DWV Database Bloat Cleaner in your WordPress dashboard.
- Open the plugin dashboard and run a Dry-Run System Bloat Scan to preview exact row counts across Post Revisions, Auto-Drafts, Expired Transients, and Orphaned Postmeta before touching a single row.
- Click Execute Batch Cleanup to remove the confirmed junk data in safe AJAX batches without timing out or locking tables on shared hosting.
- (Optional) If you manage high-traffic WooCommerce sites, DWV Database Bloat Cleaner PRO adds automated daily/weekly cron sweeps, orphaned postmeta deletion, and Action Scheduler / WooCommerce meta cleanup on autopilot.
Step 2: Reclaim Disk Space with OPTIMIZE TABLE
In InnoDB (the default MySQL/MariaDB storage engine), deleting 50,000 rows frees space inside the table file, but the file size reported by information_schema may not drop until you reclaim unused space with MySQL’s OPTIMIZE TABLE statement:
OPTIMIZE TABLE wp_posts, wp_postmeta, wp_options;
Run OPTIMIZE TABLE during low-traffic hours, as rebuilding large tables briefly locks writes while MySQL reorganizes the index pages.
Step 3: Cap Future Revisions in wp-config.php
Prevent wp_posts from bloating again by capping stored revisions to 5 per post. Add this line to your wp-config.php file right above /* That's all, stop editing! Happy publishing. */:
define( 'WP_POST_REVISIONS', 5 );
Frequently Asked Questions (FAQ)
Does a large WordPress database slow down my website?
Yes, when the extra size lives inside frequently queried tables like wp_options (especially autoloaded rows), wp_postmeta, or wp_actionscheduler_logs. Larger tables require more memory for index scans, increasing Time to First Byte (TTFB) and slowing down both frontend pages and /wp-admin/ searches.
How often should I clean my WordPress database?
For a standard blog, a monthly cleanup of revisions, auto-drafts, and expired transients is enough. For active WooCommerce stores or membership sites generating daily orders and background jobs, a weekly automated sweep keeps table size and autoload overhead flat.
Will reducing my WordPress database size delete my posts or products?
No, as long as you only target non-essential bloat (revisions, auto-drafts, expired transients, spam comments, and verified orphaned metadata). Published posts, pages, WooCommerce orders, and active plugin settings remain completely untouched.
