WordPress stores nearly all of a site’s content and configuration in a MySQL or MariaDB database. Posts, pages, media records, revisions and custom post types are centered in wp_posts; site-wide settings are in wp_options; and accounts are split between wp_users and wp_usermeta. Managing the database safely means understanding those relationships, exporting a backup before changes, controlling autoloaded options, and cleaning only on a tested copy.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The examples below use the conventional wp_ prefix. Your installation may use another prefix, so substitute the prefix shown in your database. Never run destructive SQL on a production site until a restorable backup and a staging test are in place.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →The WordPress database in one sentence
A WordPress request combines PHP code with rows in MySQL or MariaDB. The database supplies content, settings, users, taxonomy relationships, comments and metadata; WordPress then turns that data into an HTML response or an administrative screen. Plugins and themes normally add their own rows rather than creating an entirely separate content system, which is why a small number of core tables can become very large over time.
The table names are not a permanent contract. Core tables and autoload behavior have changed between releases, and plugins can create additional tables. Treat the list below as the core model, not a promise that every installation has exactly the same schema.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Core tables and how they relate
| Table | What it stores | How it is used |
|---|---|---|
wp_posts |
Posts, pages, custom post types, attachments, revisions and autosaves | The central content table. A page, an uploaded image record and a revision are different rows distinguished by fields such as post type and status. |
wp_options |
Site-wide settings and other key/value data | WordPress and plugins read options for configuration. The autoload column controls whether an option is loaded on every request. |
wp_users |
Login names, password hashes, email addresses and core account details | Identifies each account. Passwords are stored as hashes, not readable passwords. |
wp_usermeta |
Roles, capabilities, preferences and other per-user metadata | Links additional values to a user ID in wp_users. |
| Comments and comment metadata tables | Comments and values attached to comments | Comments reference content and can carry plugin-specific metadata. |
| Terms, term-taxonomy, term-relationships and taxonomy metadata tables | Categories, tags, custom taxonomies and their metadata | Relationship rows connect a post to one or more categories, tags or custom taxonomy terms. |
A single-site guide describes 12 default tables, but the exact set depends on the WordPress release and installed extensions. Multisite installations have additional network and per-site table groups, so a fixed table count is not a reliable way to audit a current site.
Why wp_posts is broader than its name
The name suggests blog posts, but WordPress uses the same table for pages, custom post types, attachment records, revisions and autosaves. Deleting a visible page does not necessarily remove every related row elsewhere: taxonomy relationships, metadata, comments and media references may remain. Conversely, a revision is not a separate table that can be ignored when estimating database growth.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhy wp_options deserves special attention
Options are key/value records. A theme might store its settings there, while a plugin can store caches, feature flags, credentials, schedules or serialized configuration. Because many options are read during bootstrap, the table can affect every front-end request even when a visitor never opens the plugin that created them.
What happens during a normal request
- WordPress loads configuration from
wp-config.php, includingDB_HOST,DB_NAME,DB_USERandDB_PASSWORD. - Core establishes a database connection and loads the options marked for autoload.
- WordPress queries the content and relationships needed for the requested page, such as a post row, author data, taxonomy terms and metadata.
- Plugins and themes issue their own option and content queries, often using the same tables and sometimes their own tables.
- The resulting data is assembled into the response. Administrative screens follow the same principle but query different rows and expose editing operations.
This model explains two common symptoms. A damaged or unavailable database can take down the whole site, while an oversized set of autoloaded options can slow every request before the page-specific query even begins.
Back up before you inspect or change anything
A database backup is a copy you can restore independently of the live server. Do not rely only on a host’s daily snapshot: keep at least one copy off the server and verify that it can be read. Files and the database are separate; a complete WordPress recovery normally needs both the database and the wp-content files, especially uploads and plugin or theme configuration.
WP-CLI export
With shell access and WP-CLI, export the database before maintenance:
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
wp db export backups/site-2026-10-14.sqlThe command invokes mysqldump using the database settings in wp-config.php and accepts valid mysqldump flags. A focused export is also possible:
wp db export --tables=wp_options,wp_usersUse --exclude_tables when a dump must omit selected tables. A partial export is not a substitute for a full pre-change backup; it is useful for inspection or a narrowly defined recovery task.
Backup plugin or hosting interface
A GUI backup tool is appropriate when you do not have shell access or need scheduled off-server storage. Confirm what it includes, where it stores copies, how long they are retained and how a restore is performed. Download a copy before maintenance rather than leaving the only backup inside the same hosting account as the live database.
Prove the backup is usable
- Check that the export file exists and has a plausible size.
- Store a copy outside the production server.
- Test a restore on a staging installation when the site is business-critical.
- Record the WordPress version, PHP version, database credentials location and table prefix needed for recovery.
Autoloaded options: the main database performance checkpoint
WordPress loads autoloaded options on every page request. The WordPress Optimization handbook advises keeping their combined size below 800 KB. WordPress 6.6 added a Site Health check that reports the critical issue Autoloaded options could affect performance when the total exceeds 800 KB. The threshold is a warning signal, not proof that one specific option is defective: a busy site can still have a slow option set below it, and a site over it may continue to function while using more memory and query time.
Measure before deleting
For a first-pass estimate, run a read-only query with your actual table prefix:
SELECT SUM(LENGTH(option_value)) AS autoload_bytes
FROM wp_options
WHERE autoload IN ('yes','on','auto-on','auto');This sums stored value bytes for the common autoload values. Interpret it as an inventory figure, not a complete performance diagnosis: serialized values, database encoding and the behavior of your WordPress release still matter. Inspect the largest individual rows and identify the owning plugin or theme before changing anything.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
From WP-CLI, inspect one option’s flag with:
wp option get-autoload option_nameReplace option_name with the real key. The command reads the current setting; it does not tell you whether the option is safe to remove.
Understand the autoload values
A WordPress support moderator reports that core recognizes yes, on, auto-on and auto, while yes and no are deprecated for new use since WordPress 6.7 and newer entries are stored as on or off. Because this guidance comes from a support response rather than a schema reference, check the behavior of the WordPress version you operate before writing bulk updates.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Changing an option from autoloaded to non-autoloaded is a performance change, not deletion. Code that expects the value during early bootstrap can break if it is no longer loaded when that code runs. Make one change at a time, test logged-out and logged-in pages, and keep a rollback record.
Change one option with WP-CLI
wp option set-autoload option_name noOn releases that use the newer vocabulary, the equivalent target may be off. Use the value reported by wp option get-autoload and your release’s documentation. If a plugin fails after the change, restore the prior value immediately and investigate the plugin’s bootstrap assumptions on staging.
Large options and newer core behavior
Core changes reported in 2024 mean that large options are no longer autoloaded by default unless the developer explicitly passes true. That protects new data from automatically increasing the bootstrap payload, but it does not repair an existing oversized option set or justify changing an option whose owner still requires early loading.
Cleaning database growth without breaking the site
Database cleanup has two separate goals: remove data that is genuinely obsolete, and reclaim storage occupied by tables after rows are removed. Do the logical cleanup first, test, then consider physical optimization. Keep a written list of every row class or option you changed.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Revisions and autosaves
Revisions and autosaves are legitimate rows in wp_posts. They support editorial recovery, so deleting them can remove a useful safety net. Set a deliberate revision-retention policy with the WP_POST_REVISIONS setting in wp-config.php, or use a maintenance tool that lets you preview and retain the number of revisions your editors actually need. Apply the policy on staging first and avoid deleting revisions that are subject to legal, editorial or compliance requirements.
Expired transients
Transients are temporary values stored in wp_options. Expired entries are not guaranteed to disappear immediately, and plugins may recreate them. Inspect the option name and owner before removal; never delete every row that merely resembles a cache without checking whether a plugin uses it for locks, queues or scheduled work.
Orphaned metadata
When content, users or comments are deleted improperly, metadata rows can remain without a parent. A common LEFT JOIN pattern illustrates the relationship:
DELETE pm
FROM wp_postmeta AS pm
LEFT JOIN wp_posts AS p ON p.ID = pm.post_id
WHERE p.ID IS NULL;Equivalent checks can be designed for wp_usermeta joined to wp_users and wp_commentmeta joined to wp_comments. Treat these statements as high-risk SQL, not a universal cleanup recipe. Export first, run a SELECT using the same joins to review candidate rows, check for plugin-owned data, and execute only on a staging copy before production.
Recommended Free Tools
Optimize table storage
wp db optimize can rebuild tables and recover unused space, but it does not remove revisions, spam or other WordPress data. Run it after logical cleanup, during a low-traffic window, and confirm that your database user has the required privileges. A smaller file is not evidence that the application is faster; measure page response and error logs after the operation.
Manual SQL versus a maintenance plugin
| Approach | Strengths | Risks and safeguards |
|---|---|---|
| WP-CLI and SQL | Scriptable, repeatable and precise; suitable for version-controlled runbooks | Requires shell or database expertise. A wrong prefix, join or WHERE clause can delete unrelated data. Use read-only previews, transactions where supported, backups and staging. |
| GUI maintenance plugin | Accessible to administrators without shell access; often provides previews and scheduled jobs | Capabilities vary. Some tools combine several cleanup actions or remove data more broadly than intended. Review each checkbox, export first and test the restore path. |
Choose the method that matches your recovery skills. Precision is valuable only when the operator can identify the rows and restore the result.
A safe management workflow
- Inventory. Record the WordPress version, whether the site is single-site or multisite, the table prefix, database size and the plugins or themes that own unusual tables or options.
- Export. Create a full database dump with WP-CLI or a GUI backup, copy it off-server and verify the file.
- Clone. Reproduce the site on staging, including the database and relevant files. Disable public indexing and use test accounts.
- Measure. Check the autoload total, inspect large options and identify revision, transient and metadata growth. Do not delete based only on table size.
- Change narrowly. Alter one option or one cleanup class at a time. Keep the exact command or SQL and the previous value in a change log.
- Test. Check the home page, representative posts and pages, search, forms, media, logins, scheduled tasks and the editor. Test both anonymous and administrator sessions.
- Promote cautiously. Repeat the tested change in production during a maintenance window, with the backup available and monitoring enabled.
- Verify and monitor. Watch error logs, Site Health, response times and plugin behavior. If a regression appears, restore the previous option value or the backup rather than layering more untested edits.
Troubleshooting common database-management failures
WP-CLI cannot connect
Check that you are running the command from the WordPress installation, that wp-config.php is readable, and that DB_HOST, DB_NAME, DB_USER and DB_PASSWORD point to the intended database. A successful shell command against the wrong environment is still a failure, so confirm the site URL and table prefix before exporting or changing anything.
Site Health reports oversized autoloaded options
Measure the total, list the largest options and identify their owners. Do not mass-switch every large row to non-autoloaded. Remove only data that is demonstrably obsolete, or change one option after confirming that its plugin does not require it during bootstrap. Recheck the report after cache expiration and a normal request cycle.
Free tools Windows power users keep installed
One-click scans. No signup required.
A plugin breaks after autoload is disabled
Restore the previous autoload value, record the error and reproduce the problem on staging. The failure indicates a timing assumption in the plugin or theme, not necessarily corrupt data. Keep the option autoloaded until the owner provides a compatible fix or a tested alternative.
Optimization did not reduce the database file
Physical optimization cannot remove live rows. Revisions, expired transients, spam and orphaned metadata require separate, reviewed cleanup. Some storage engines or hosting configurations may also handle reclaimed space differently, so judge the operation by verified table statistics and site behavior rather than file size alone.
Content disappears after cleanup
Stop further writes, preserve logs and restore the affected database on staging from the pre-change export. Compare the deleted IDs and relationships before attempting a production restore. If only a setting changed, revert that option; if rows were deleted, a full or table-level restore may be necessary.
Version and installation caveats
Autoload labels, Site Health checks and default tables evolve. The 800 KB guidance is documented by the WordPress Optimization handbook, and the Site Health warning was introduced in WordPress 6.6. The reported deprecation of yes and no for new autoload entries applies from WordPress 6.7, but older sites can still contain those values. Check current release documentation before automating a database-wide update.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not assume a particular storage engine, table count or legacy table is present simply because another installation has it. Sources disagree about when InnoDB became the default, and the exact multisite table count varies. Inspect your own schema and back up before changing engine settings or removing a table that appears unused.
A practical maintenance checklist
- Keep a full, off-server database export and know how to restore it.
- Use staging for every destructive or performance-related change.
- Confirm the table prefix before writing SQL.
- Measure autoloaded options before changing them; keep the total below the documented 800 KB guideline where practical.
- Identify the plugin or theme that owns each large option.
- Set a revision policy that preserves the recovery history editors need.
- Review transients and metadata for ownership and parent rows before deletion.
- Use
wp db optimizeonly for storage maintenance after logical cleanup. - Record commands, previous values, test results and rollback steps.
- Recheck Site Health and front-end behavior after production changes.
Bottom line
WordPress database management is controlled change management, not routine table emptying. Understand the roles of wp_posts, wp_options, wp_users and their relationship tables; export before editing; keep autoloaded options under the 800 KB guidance; and remove revisions, transients or orphaned metadata only when ownership and recovery are clear. The safest optimization is the one you can reproduce on staging and reverse from a verified backup.
Quick Recap
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.
