Meta tags:
description=Your WordPress database collects junk automatically and never cleans itself. Here s how to remove revisions, transients, and spam safely using DB Optimizer.;
author=Joella Dunn;

Headings (most frequently used words):

database, your, step, cleanup, the, clean, wordpress, to, up, my, back, after, cleaning, and, how, doesn, that, without, don, wp, admin, get, on, health, score, site, post, revisions, is, it, safe, delete, what, resources, best, beginner, guide, removing, junk, why, often, should, you, troubleshooting, when, go, as, expected, frequently, asked, questions, faqss, stay, way, plan, let, another, day, pass, unprotected, wait, miss, yourexclusive, deal, slows, down, backups, bigger, migrations, riskier, autoload, data, loads, every, page, request, bloat, compounds, databasse, install, db, optimizer, check, adjust, retention, settings, optimize, tables, verify, worked, didn, improve, something, broke, keep, coming, still, feels, slow, will, speed, website, do, need, before, difference, between, optimizing, can, plugin, are, transients, them, popular, company, products, backup, migration, features, integrations, our, content, table, of, contents, optimization, services, tools, worth, money, in, 2026, 10, staging, practices, prevent, live, disasters,

Text of the page (most frequently used words):
the (156), and (85), you (80), #wordpress (77), your (70), database (66), #cleanup (51), duplicator (47), site (41), that (41), plugin (36), step (34), with (32), clean (30), backup (27), optimizer (26), get (23), score (23), every (21), before (20), data (20), this (19), how (19), backups (19), pro (18), health (18), for (17), new (17), revisions (17), what (16), see (15), from (15), autoload (15), but (14), can (14), table (14), size (14), back (13), migration (13), most (13), post (13), something (13), doesn (13), check (13), after (13), plugins (13), restore (12), server (12), click (12), cloud (12), when (12), transients (12), time (11), without (11), storage (11), one (11), tables (11), off (10), website (10), optimize (10), are (10), over (10), revision (10), admin (10), install (9), don (9), full (9), sites (9), junk (9), removes (9), tool (9), all (9), now (8), content (8), more (8), migrations (8), like (8), expired (8), retention (8), has (8), cleaning (8), rows (8), space (8), tab (8), included (8), free (7), activity (7), optimization (7), here (7), need (7), preview (7), run (7), behind (7), have (7), directly (7), transient (7), anything (7), settings (7), spam (6), only (6), started (6), resources (6), drive (6), recovery (6), log (6), first (6), years (6), means (6), working (6), any (6), those (6), problem (6), also (6), not (6), threshold (6), where (6), once (6), created (6), request (6), bloat (6), categories (6), through (6), overhead (6), clone (5), pre (5), features (5), media (5), performance (5), dashboard (5), next (5), joella (5), handles (5), both (5), use (5), stored (5), add (5), store (5), comments (5), bloated (5), will (5), days (5), default (5), won (5), some (5), page (5), should (5), there (5), posts (5), been (5), why (4), customer (4), 2026 (4), large (4), best (4), contact (4), getting (4), dropbox (4), google (4), amazon (4), drag (4), installs (4), fast (4), live (4), worth (4), may (4), safe (4), slow (4), wrong (4), stay (4), out (4), work (4), way (4), delete (4), them (4), active (4), queries (4), shows (4), fragmented (4), left (4), deleted (4), configuration (4), minutes (4), was (4), show (4), running (4), pages (4), low (4), wp_options (4), still (4), remove (4), adjust (4), edit (4), gets (4), than (4), checking (4), open (4), three (4), verify (4), worked (4), each (4), items (4), place (4), available (3), exclusive (3), manually (3), migrate (3), support (3), stories (3), changelog (3), faqs (3), documentation (3), blog (3), ftp (3), sftp (3), cloudflare (3), digital (3), ocean (3), vultr (3), microsoft (3), onedrive (3), integrations (3), drop (3), import (3), configured (3), woocommerce (3), multisite (3), points (3), secure (3), compare (3), plans (3), products (3), about (3), risk (3), growth (3), name (3), 000 (3), copy (3), safely (3), beginner (3), guide (3), staging (3), writer (3), experience (3), maintenance (3), make (3), ready (3), bio (3), dunn (3), warning (3), owners (3), fix (3), monthly (3), think (3), other (3), goes (3), million (3), protect (3), their (3), against (3), somewhere (3), becomes (3), much (3), keep (3), adds (3), verified (3), gone (3), plan (3), deletion (3), never (3), cleaned (3), unless (3), ones (3), already (3), yes (3), sql (3), deleting (3), query (3), drafts (3), then (3), depends (3), bottleneck (3), version (3), recently (3), frequently (3), culprit (3), look (3), load (3), ran (3), panel (3), feels (3), later (3), expected (3), usually (3), around (3), issue (3), which (3), troubleshooting (3), five (3), high (3), changes (3), higher (3), process (3), bulk (3), recommend (3), exactly (3), select (3), cache (3), across (3), read (3), trash (3), loads (3), breaks (3), down (3), 100 (3), elite (3), using (3), needs (3), john (3), turner (3), login (3), view (3), ever (2), try (2), wait (2), limited (2), miss (2), move (2), quickly (2), our (2), services (2), hour (2), costs (2), let (2), day (2), complete (2), right (2), others (2), widget (2), custom (2), practices (2), prevent (2), disasters (2), tools (2), certain (2), she (2), specializes (2), basic (2), scale (2), her (2), ultimate (2), goal (2), sure (2), signs (2), quarterly (2), repair (2), steps (2), took (2), needed (2), these (2), integration (2), broken (2), didn (2), significant (2), removal (2), quick (2), two (2), catch (2), own (2), take (2), again (2), stack (2), uninstall (2), leave (2), isn (2), done (2), hard (2), part (2), green (2), temporary (2), cached (2), values (2), automatically (2), they (2), non (2), phpmyadmin (2), lets (2), built (2), confirmation (2), production (2), unnecessary (2), auto (2), optimizing (2), reclaims (2), defragging (2), difference (2), looks (2), remote (2), lives (2), response (2), speed (2), front (2), end (2), hosting (2), published (2), protects (2), last (2), edited (2), touched (2), asked (2), questions (2), faqss (2), common (2), entirely (2), loading (2), scored (2), improved (2), number (2), fine (2), reasonable (2), frequent (2), count (2), behavior (2), keeps (2), safety (2), net (2), recent (2), happens (2), stores (2), reset (2), red (2), scoring (2), touch (2), barely (2), moved (2), always (2), catching (2), months (2), major (2), same (2), takes (2), know (2), looking (2), publishing (2), comment (2), build (2), shape (2), month (2), drops (2), below (2), often (2), category (2), errors (2), spot (2), into (2), were (2), shown (2), starting (2), real (2), bigger (2), runs (2), zero (2), gaps (2), used (2), deletions (2), confirm (2), individual (2), item (2), trashed (2), counts (2), tells (2), mostly (2), within (2), set (2), knew (2), sitting (2), whether (2), saved (2), good (2), download (2), activate (2), standalone (2), files (2), help (2), create (2), tutorial (2), databasse (2), reclaim (2), point (2), path (2), today (2), databases (2), longer (2), transfer (2), until (2), starts (2), had (2), removing (2), pricing (2), track (2), redirect, pros, trust, discount, deal, coupon, sitemap, privacy, policy, terms, service, copyright, registered, trademark, snap, creek, llc, very, affiliates, press, careers, company, proper, puts, delayed, another, pass, unprotected, follow, subscribe, email, please, enable, javascript, browser, form, tips, inbox, along, creating, perfect, 101, peace, mind, introducing, folders, popular, money, previous, reader, supported, links, receive, commission, checklist, weekly, myself, developer, library, helped, sides, professionals, reduces, eliminate, scenario, critical, belong, slips, changed, habits, accumulation, its, hand, writes, publish, revise, tends, undo, neglect, normal, optimized, supposed, expire, uses, lazy, requests, schedule, pile, leaves, alone, commands, methods, neither, lot, cli, equivalent, between, deletes, permanently, format, could, break, sideways, creates, improvement, consistent, gains, caching, infrastructure, replace, rest, image, clarification, useful, roll, earlier, satisfied, serve, purpose, unrelated, theme, heavy, assets, backend, healthy, elsewhere, too, many, factor, making, affects, successfully, sluggish, caps, per, going, forward, far, less, define, wp_post_revisions, address, source, line, config, php, file, week, climbed, existing, saving, coming, restored, raised, wider, isolate, patch, known, state, bad, exists, finished, stopped, disappeared, threw, error, broke, disable, just, replaced, identify, contributing, searching, alongside, monitor, inspect, indicator, information, tell, separately, almost, improve, cleanups, hitch, yours, early, easier, digging, uninstalling, recurring, reminder, calendar, routine, updating, traffic, rarely, updated, stretch, checks, daily, volume, weeks, faster, busy, solid, hold, trouble, enough, comfortable, target, light, stare, constantly, regularly, problems, compound, section, despite, successful, specifically, forcing, amount, troubleshoot, blind, start, diagnostic, missing, visit, few, poke, during, total, stats, noted, recovered, unmanaged, jump, maintained, return, refresh, finishes, column, near, closes, makes, efficient, reason, list, commit, proceed, executing, hit, button, buttons, selected, oembed, pingbacks, trackbacks, ratings, organizes, removable, groups, reclaimable, head, setting, completely, dormant, stable, lower, revised, raise, find, area, draft, matter, safeguard, note, moving, decide, prioritize, test, damage, since, edits, unlimited, focus, folder, versions, session, orange, meaningful, addressing, immediately, color, coded, account, upload, period, avoid, dedicated, orphaned, finish, building, chose, uploads, locally, preset, includes, everything, corrupted, storing, native, well, upgrading, however, want, lite, yet, directory, actively, afterthought, calling, nothing, disappears, being, caught, window, access, bundled, touching, verification, plateau, manageable, level, grows, received, activated, felt, six, ago, compounds, write, enabled, single, seen, transfers, mean, exposure, timeouts, mid, connection, riskier, tied, 50mb, shaved, future, sift, swell, thousands, year, feel, slows, invisible, affecting, attention, contents, habit, especially, removals, negotiable, ways, key, takeaways, 200mb, recoverable, thought, walk, assess, actually, notice, slowly, long, halfway, saves, task, president, business, development, his, downloaded, times, reviewed, written, min, jun, continue, reading, bloating, join, close, learn, save, unused, updates, change, action, announcing, restores, bold, consequences, customers, offer,

Text of the page (random words):
y future backup over time that adds up in both transfer time and cloud storage costs migrations get riskier a bloated database takes longer to back up and transfer longer transfers mean more exposure to timeouts and connection errors mid migration i ve seen migrations on clean databases complete in minutes that took over an hour on bloated ones autoload data loads on every page request some plugins write data to the wp_options table with autoload enabled wordpress loads all of it on every single page request whether the plugin needs it right now or not you won t see this in your revision count but it shows up in your site s response time bloat compounds bloat doesn t plateau at some manageable level and stay there it grows with every post edit comment received and plugin activated a database that felt fine six months ago can be a real problem today how to clean up your wordpress database here s the full process of cleaning your database from backup to verification here s what you ll do step 1 back up your site with duplicator create a verified backup and store it in cloud storage before touching anything if cleanup breaks something this is your only recovery path step 2 install db optimizer get the cleanup tool in place or access it through duplicator pro if it s already bundled with your plan step 3 check your database health score read the 0 100 score across five categories so you know where the bloat is step 4 adjust your retention settings set the threshold that protects recently created data from being caught in the cleanup the default 7 day window is a good starting point for most sites step 5 run the cleanup remove revisions spam transients and other junk in bulk with a preview step before each deletion so nothing disappears without confirmation step 6 optimize your database tables reclaim the fragmented space left behind after deletions step 7 verify the cleanup worked confirm the health score improved check the before after database size and spot check the live site before calling it done step 1 back up your databasse if you delete something a plugin was actively using your only way back is a working backup that s why this is the first step and not an afterthought duplicator is a wordpress backup and migration plugin used by over 1 5 million site owners the free version handles full site backups and is available directly from the wordpress plugin directory if you re not on duplicator pro yet install the free version now and it ll get you through this step we ll be using db optimizer later in this tutorial which is included with duplicator pro so it s worth upgrading however you can also get db optimizer as a standalone plugin if you want to work with duplicator lite install and activate duplicator on your wordpress site to create your backup go to backups and click add new i recommend storing a copy somewhere off your server duplicator pro has native duplicator cloud storage as well as amazon s3 google drive dropbox and more if your server goes down or gets corrupted a backup sitting on the same server won t help you with a cloud copy in place duplicator pro lets you restore directly from cloud storage with one click select the full site preset this includes everything on your website finish building the backup if you chose cloud storage duplicator automatically uploads your files there if you saved the backup locally download both files step 2 install db optimizer db optimizer is duplicator s dedicated database cleanup plugin it handles revisions transients spam orphaned cache data and table optimization here s what you ll get with db optimizer 0 100 database health score pre cleanup backups with duplicator integration bulk database cleanup removes table overhead transients revisions autoload size and trash items individual database table cleanup and repair custom retention period to avoid deleting recent data the plugin is included free with duplicator pro or elite plans it s also available as a standalone plugin for 29 yr once you get the plugin download it from your duplicator account upload it as a new plugin in wordpress and activate it step 3 check your database health score open db optimizer you ll immediately see your database health score a number from 0 to 100 color coded green means the database is in good shape orange or red means there s meaningful bloat worth addressing the score breaks down across five categories table overhead fragmented space left behind after rows have been deleted transients expired cached values plugins stored but never cleaned up revisions saved versions of posts and pages from every edit session autoload size data wordpress loads on every page request whether it s needed or not trash items posts pages and comments sitting in the trash folder my test site scored a 61 on the first run most of the damage was in revisions since there were three years of post edits with wordpress s default unlimited revision storage once i knew that i knew exactly where to focus note which categories are scoring low before moving on you ll use that to decide what to prioritize in the cleanup step 4 adjust your retention settings before running any cleanup set your retention threshold this is the safeguard that keeps db optimizer from deleting something you created or edited recently find it in the settings area within db optimizer the default is 7 days any revision draft or transient created in the last 7 days won t be touched no matter what you select in the cleanup step if you re running a stable production site with mostly published content you can lower it to 3 5 days if your site has active drafts or content that gets revised frequently keep it at 7 or raise it higher i don t recommend setting it to 0 that removes the safety net entirely and unless the site has been completely dormant you risk catching data that s still in use step 5 clean up your database now head over to the cleanup tab this is where the data removal happens db optimizer organizes removable items into three groups before you click anything read the item counts and reclaimable space shown next to each category that tells you exactly what s about to go you ll see ratings across these categories posts pages post revisions auto drafts and trashed posts comments spam comments trashed comments pingbacks and trackbacks transients cache expired transients and oembed cache hit the select all button and then clean selected items you can also use individual clean buttons next to each item when you proceed to cleanup db optimizer shows you a preview of exactly what will be deleted confirm it before executing this preview step is the reason i recommend this tool over running sql queries manually you can see the list before you commit step 6 optimize your database tables cleanup removes rows this step reclaims the space those deletions left behind think of it like defragging a hard drive the data is gone but the database still has fragmented gaps where those rows used to be table optimization closes those gaps and makes queries more efficient open the tables tab db optimizer shows each table s name size and overhead click optimize on any table with significant overhead you can also click optimize all tables with overhead to clean in bulk the process runs quickly on most tables after it finishes the overhead column should show 0 or near zero step 7 verify the cleanup worked return to the dashboard tab and refresh the health score it should be higher than when you started how much higher depends on how bloated the database was a site with three years of unmanaged revisions will see a bigger jump than one that s been maintained check the total database size shown in the stats panel compare it to what you noted before starting that difference is real storage recovered then spot check your site visit the front end log into wp admin open a few posts and poke around any plugins that were active during the cleanup you re looking for anything broken missing content plugin errors settings that have reset if something is wrong don t troubleshoot blind restore the duplicator backup you created in step 1 and start the diagnostic from there if the health score barely moved despite a successful cleanup look at the autoload size category specifically a high autoload score means a plugin is forcing wordpress to load a large amount of data on every page request that s a plugin configuration issue not something cleanup removes see the troubleshooting section below how often should you clean your database think of the health score like a warning light you don t need to stare at it constantly but checking it regularly means you catch problems before they compound for most sites checking once a month is enough clean when the score drops below a threshold you re comfortable with somewhere around 70 is a reasonable target if the site is in solid shape after a cleanup it ll hold for a month without much trouble high activity sites with daily publishing high comment volume or frequent plugin changes may need a check every two weeks the revision and transient categories build up faster on busy sites low traffic sites or ones rarely updated can stretch to quarterly checks without issue add a recurring reminder to your calendar make it part of the same routine as checking backups and updating plugins it takes about five minutes once you know what you re looking at you should also run a quick health score check after any major plugin install or uninstall new plugins can add autoload data and uninstalling plugins doesn t always clean up their database tables catching that early is easier than digging it out months later troubleshooting when the cleanup doesn t go as expected most cleanups run without a hitch here s what to do when yours doesn t the health score didn t improve after cleanup you ran through every cleanup step and the score barely moved the culprit is almost always autoload size autoload data is information plugins store in the wp_options table and tell wordpress to load on every page request it doesn t show up in the revision or transient categories it lives separately and cleanup doesn t touch it check the autoload size indicator on the dashboard tab if it s red or low scoring that s your bottleneck identify which plugins are contributing the most by searching wordpress autoload bloat alongside the plugin name or use a tool like query monitor to inspect wp_options directly the fix is usually in the plugin s own settings some plugins let you disable autoload for certain data and others just need to be replaced something on the site broke after cleanup you finished the cleanup and something stopped working a widget disappeared a plugin threw an error or settings reset to default this happens when a plugin stores configuration data as a transient or stores it in a way that looks like junk to a cleanup tool it s bad plugin behavior but it exists restore the duplicator backup you created in step 1 don t try to patch around the issue first a full restore gets you back to a known working state in minutes once you re restored run the cleanup again with the retention threshold raised to 14 or 30 days that wider safety net will protect more recent data and usually isolate the problem post revisions keep coming back you cleaned out the revisions and a week later the count has climbed back up that s expected behavior cleanup removes the existing stack but wordpress keeps saving new revisions with every edit the cleanup fix is temporary unless you address the source add this line to your wp config php file define wp_post_revisions 3 that caps revision storage at 3 per post going forward your next cleanup will have far less to remove you can adjust the number but 3 is fine for most sites and 10 is reasonable for sites with frequent content revisions wp admin still feels slow after cleanup the cleanup ran successfully and the health score improved but the admin panel still feels sluggish database size is one factor if autoload size scored low on your dashboard tab a bloated wp_options table is making wordpress load unnecessary data on every request and that affects admin performance directly the other common culprit is unrelated to the database entirely too many plugins running on admin pages slow hosting or a theme loading heavy assets in the backend if the autoload size score is healthy after cleanup the database isn t the bottleneck and you ll need to look elsewhere frequently asked questions faqss is it safe to delete post revisions yes with one clarification revisions are only useful if you need to roll back a post to an earlier version once a post is published and you re satisfied with it those revisions serve no purpose db optimizer s retention threshold protects anything created in the last 7 days by default so recently edited content won t be touched will cleaning my database speed up my website it can but the improvement depends on how bloated the database was and where the bottleneck lives the most consistent gains show up in wp admin response time and backup speed front end performance depends more on caching hosting infrastructure and image optimization a clean database removes one drag on performance it doesn t replace the rest of the work do i need to back up before cleaning my database yes a database cleanup deletes rows permanently if a plugin stored configuration data in a format that looks like junk to a cleanup tool you could break something without a backup to restore from duplicator pro creates a full site backup in minutes and you can store it directly to cloud storage for a remote restore if anything goes sideways what s the difference between cleaning and optimizing a database cleaning removes unnecessary rows revisions spam comments expired transients and auto drafts optimizing reclaims the fragmented space left behind after those rows are deleted the database equivalent of defragging a drive db optimizer handles both cleanup in the cleanup tab and table optimization in the tables tab do the cleanup first then optimize can i clean my database without a plugin yes phpmyadmin lets you run sql queries directly against the database and wp cli has built in transient deletion commands both methods work but neither shows you a preview before deleting one wrong query in phpmyadmin and the data is gone a plugin like db optimizer adds a confirmation step that sql queries don t have that preview is worth a lot when you re working with a production database what are transients and is it safe to delete them transients are temporary cached values that plugins store in your database wordpress is supposed to delete them automatically when they expire but it uses lazy deletion it only removes them when something requests them not on a schedule that means expired transients pile up over time and never get cleaned unless you do it manually db optimizer s retention threshold leaves active non expired transients alone and only removes the ones that ...