Now works on WordPress 5.6+ and PHP 7.4+. Fixes a blank screen after quarantining and correctly flags leftover tables from deleted plugins. Run a new scan after updating.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3721616,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3721616,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3721616,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3721616,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{"blueprint.json":{"filename":"blueprint.json","revision":3721619,"resolution":false,"location":"assets","locale":"","contents":"{\"$schema\":\"https:\\\/\\\/playground.wordpress.net\\\/blueprint-schema.json\",\"meta\":{\"title\":\"Attic demo\",\"description\":\"A site with leftovers from deleted plugins, ready to scan.\",\"author\":\"rainynewt\"},\"landingPage\":\"\\\/wp-admin\\\/tools.php?page=attic-safe-database-audit\",\"preferredVersions\":{\"php\":\"8.3\",\"wp\":\"latest\"},\"steps\":[{\"step\":\"login\"},{\"step\":\"installPlugin\",\"pluginData\":{\"resource\":\"wordpress.org\\\/plugins\",\"slug\":\"attic-safe-database-audit\"},\"options\":{\"activate\":true}},{\"step\":\"runPHP\",\"code\":\" 'USD' ), '', 'yes' );\\n\\n\\\/\\\/ Orphaned tables.\\n$wpdb->query( \\\"CREATE TABLE {$wpdb->prefix}yoast_indexable ( id bigint(20) unsigned NOT NULL AUTO_INCREMENT, permalink text, PRIMARY KEY (id) )\\\" );\\n$wpdb->query( \\\"CREATE TABLE {$wpdb->prefix}e_events ( id bigint(20) unsigned NOT NULL AUTO_INCREMENT, event_data text, PRIMARY KEY (id) )\\\" );\\nfor ( $i = 0; $i < 200; $i++ ) {\\n\\t$wpdb->insert( $wpdb->prefix . 'yoast_indexable', array( 'permalink' => home_url( '\\\/?p=' . $i ) ) );\\n\\t$wpdb->insert( $wpdb->prefix . 'e_events', array( 'event_data' => str_repeat( 'e', 512 ) ) );\\n}\\n\\n\\\/\\\/ Ghost cron event with no callback.\\nwp_schedule_event( time() + 3600, 'hourly', 'elementor_1_elementor_updater' );\\n\\n\\\/\\\/ Expired transient that was never cleaned up.\\nadd_option( '_transient_timeout_wc_report_sales_by_date', time() - DAY_IN_SECONDS, '', 'no' );\\nadd_option( '_transient_wc_report_sales_by_date', str_repeat( 'r', 4096 ), '', 'no' );\\n\\n\\\/\\\/ Post meta whose post no longer exists.\\n$wpdb->insert( $wpdb->postmeta, array( 'post_id' => 999999, 'meta_key' => '_elementor_data', 'meta_value' => '[]' ) );\\n\"}]}"}},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1","2.0.0","2.1.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3721616,"resolution":"1","location":"assets","locale":"","width":2342,"height":1662},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3721616,"resolution":"2","location":"assets","locale":"","width":2420,"height":1747},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3721616,"resolution":"3","location":"assets","locale":"","width":1492,"height":420},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3721616,"resolution":"4","location":"assets","locale":"","width":2342,"height":1658},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3721616,"resolution":"5","location":"assets","locale":"","width":2344,"height":1610}},"screenshots":{"1":"Scan results: every finding shows its rule, confidence, size and the plugin it belongs to.","2":"Finding evidence: whether the owning plugin is on disk and how many code references were found.","3":"Quarantine: restore a whole batch in one click within the 30-day window.","4":"Autoload trend chart against Site Health's 800 KB limit.","5":"Settings: scan thresholds, quarantine purge window and scheduled scans."}},"plugin_section":[],"plugin_tags":[3786,153,17806,247,151481],"plugin_category":[52,54,59],"plugin_contributors":[271439],"plugin_business_model":[],"class_list":["post-359443","plugin","type-plugin","status-publish","hentry","plugin_tags-cleanup","plugin_tags-database","plugin_tags-database-cleanup","plugin_tags-performance","plugin_tags-site-health","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-rainynewt","plugin_committers-rainynewt"],"banners":{"banner":"https:\/\/ps.w.org\/attic-safe-database-audit\/assets\/banner-772x250.png?rev=3721616","banner_2x":"https:\/\/ps.w.org\/attic-safe-database-audit\/assets\/banner-1544x500.png?rev=3721616","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/attic-safe-database-audit\/assets\/icon-128x128.png?rev=3721616","icon_2x":"https:\/\/ps.w.org\/attic-safe-database-audit\/assets\/icon-256x256.png?rev=3721616","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/attic-safe-database-audit\/assets\/screenshot-1.png?rev=3721616","caption":"Scan results: every finding shows its rule, confidence, size and the plugin it belongs to."},{"src":"https:\/\/ps.w.org\/attic-safe-database-audit\/assets\/screenshot-2.png?rev=3721616","caption":"Finding evidence: whether the owning plugin is on disk and how many code references were found."},{"src":"https:\/\/ps.w.org\/attic-safe-database-audit\/assets\/screenshot-3.png?rev=3721616","caption":"Quarantine: restore a whole batch in one click within the 30-day window."},{"src":"https:\/\/ps.w.org\/attic-safe-database-audit\/assets\/screenshot-4.png?rev=3721616","caption":"Autoload trend chart against Site Health's 800 KB limit."},{"src":"https:\/\/ps.w.org\/attic-safe-database-audit\/assets\/screenshot-5.png?rev=3721616","caption":"Settings: scan thresholds, quarantine purge window and scheduled scans."}],"raw_content":"\n
Site Health says \"Autoloaded options could affect performance\"? Attic shows you exactly what's causing it, and lets you remove it without risking your site.<\/strong><\/p>\n\n https:\/\/youtu.be\/C8nLYrIFiVk<\/p>\n\n Every plugin you've ever installed left something behind: oversized options, dead cron jobs, orphaned database tables, stale transients. Deleting the plugin doesn't delete its data. WordPress loads a lot of that leftover data on every single page request, so years of \"uninstalled\" plugins quietly slow your site down.<\/p>\n\n Attic finds it, shows you the evidence, and removes it the undo-friendly way<\/strong>:<\/p>\n\n Which rule fired, which plugin the data belongs to, whether that plugin is still on disk, how many code references were found, and how big it is. A finding you can't check is a finding you shouldn't act on.<\/p>\n\n Those are established cleanup tools with direct delete\/optimize actions. Attic takes a different default: nothing is permanently deleted up front \u2014 flagged tables are renamed ( Run scans from the command line, across client sites or in CI\/CD pipelines:<\/p>\n\n A curated map of plugin prefixes to their owning plugin, used to attribute\norphaned data. The map ships with the plugin and is updated with plugin\nreleases \u2014 Attic makes no outbound network requests.<\/p>\n\n Attic bundles Chart.js 4.4.4 (MIT) at Protecting things from ever being flagged:<\/p>\n\n Attribution and scanning:<\/p>\n\n Behaviour:<\/p>\n\n Install Attic, go to Tools \u2192 Attic and run a scan. The autoload findings list every large autoloaded option by size, with the plugin it belongs to and whether that plugin is still installed. Quarantine the ones left behind by plugins you've deleted. Your autoload size drops right away, and anything you remove can be restored for 30 days.<\/p><\/dd>\n If your autoloaded options are large, yes: WordPress loads them on every page request, so shrinking them cuts work on every page. Orphaned tables and meta mostly cost disk space and backup size rather than page speed. Attic shows sizes up front so you can see what's worth removing.<\/p><\/dd>\n Only if the plugin that created them is really gone and nothing on your site still reads them. Some plugins share tables, and some keep data you'd want back if you reinstall. That's why Attic never drops a table straight away: it renames it to The scan is read-only. Nothing changes until you take an explicit, confirmed action. Core options like Tools \u2192 Attic \u2192 Quarantine. Every action creates a batch; restore a whole batch in one click. Batches auto-purge after 30 days (configurable).<\/p><\/dd>\n For most rules, high confidence requires the owning plugin to be absent from disk (or the option to be size-flagged and<\/em> unread), and<\/strong> zero literal and<\/strong> zero prefix references anywhere in your code. Dynamic option names never literal-match, so even a weak signal keeps a finding at \"review\". If your filesystem could not be read, everything is marked unverified rather than guessed at.<\/p>\n\n Two rules are exceptions, because a code search cannot tell you anything useful about them: an expired transient and a meta row whose parent is gone are facts about your database, not guesses about your code. Those are reported as high confidence on their own evidence.<\/p><\/dd>\n Yes \u2014 when Redis\/Memcached is active, transients never touch the options table, and Attic says so instead of showing a meaningless clean bill of health.<\/p><\/dd>\n Yes. Single-site, subdirectory multisite, and subdomain multisite installs all work. Network-wide fleet scanning is available via the network admin dashboard.<\/p><\/dd>\n Attic works with all WordPress plugins<\/strong> \u2014 it's a read-only cleanup tool that doesn't touch plugin data unless you explicitly quarantine it. The attribution map helps identify which plugin owns which database entries, but the scan works regardless of whether a plugin is in the map.<\/p>\n\n Plugins with known prefixes in the attribution map get named attribution, and the \"leftovers from a deleted plugin\" rule relies on the map to know which prefixes belonged to which plugin.<\/p>\n\n Data belonging to a plugin that is not in the map is still found by the other rules \u2014 an oversized autoloaded option, an orphaned table or a dead cron event is detected either way. It just shows its owner as \"unknown\". You can add your own entries with the No. Attic quarantines data (renames tables, copies options), never deletes. You can restore anything from Quarantine within the purge window (default 30 days, configurable).<\/p><\/dd>\n Attic correctly detects network-active plugins and never flags their data as orphaned, even if they're deactivated on individual sites.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
What Attic finds<\/h4>\n\n
\n
Every finding shows its evidence<\/h4>\n\n
Who it's for<\/h4>\n\n
\n
Also included<\/h4>\n\n
\n
wp attic scan<\/code>, wp attic findings<\/code>, wp attic quarantine<\/code><\/li>\nHow is this different from WP-Optimize or Advanced Database Cleaner?<\/h4>\n\n
wp_attic_quarantined_*<\/code>) and options are backed up first, with one-click restore inside the purge window (default 30 days, configurable). Permanent removal only happens once a quarantined batch passes the purge window un-restored, or if you purge it yourself on purpose. Attic also checks plugin files on disk and searches your code for references before promoting findings to high confidence, so uncertain items stay at \"review.\"<\/p>\n\nWP-CLI commands<\/h4>\n\n
\n
wp attic scan<\/code> \u2014 run a full database audit<\/li>\nwp attic findings<\/code> \u2014 list and filter findings<\/li>\nwp attic quarantine<\/code> \u2014 manage quarantine batches<\/li>\nwp attic status<\/code> \u2014 check plugin status<\/li>\nwp attic map status<\/code> \u2014 inspect the bundled attribution map<\/li>\n<\/ul>\n\nAttribution Map<\/h4>\n\n
\n
wp attic map status<\/code> \u2014 show the bundled map version and entry count<\/li>\nattic_prefix_map_entries<\/code> filter<\/li>\n<\/ul>\n\nThird-party libraries<\/h4>\n\n
assets\/vendor\/chart.umd.min.js<\/code>, used\nonly to draw the autoload trend chart in the admin. It is served from your own\nsite. Attic makes no outbound network requests of any kind.<\/p>\n\nDeveloper filters<\/h4>\n\n
\n
attic_protected_options<\/code> \u2014 additional never-flag option names<\/li>\nattic_protected_cron_hooks<\/code> \u2014 additional never-flag cron hooks<\/li>\nattic_protected_tables<\/code> \u2014 additional never-flag tables<\/li>\nattic_protected_transients<\/code> \u2014 additional never-flag transient names<\/li>\n<\/ul>\n\n\n
attic_prefix_map_entries<\/code> \u2014 add or override attribution map entries<\/li>\nattic_prefix_map_path<\/code> \u2014 load the attribution map from a different file<\/li>\nattic_reference_scan_roots<\/code> \u2014 where the code search looks; for unusual layouts and custom content directories<\/li>\nattic_scan_rules<\/code> \u2014 add or remove detection rules<\/li>\n<\/ul>\n\n\n
attic_manage_capability<\/code> \u2014 which capability may scan and quarantine (default manage_options<\/code>)<\/li>\nattic_purge_after_days<\/code> \u2014 override the quarantine purge window<\/li>\nattic_tracked_autoload_options<\/code> \u2014 which options usage tracking watches<\/li>\nattic_track_autoload_usage<\/code> \u2014 return false to disable usage tracking entirely<\/li>\n<\/ul>\n\n\n\n
\n
How do I fix \"Autoloaded options could affect performance\" in Site Health?<\/h3><\/dt>\n
Will this make my site faster?<\/h3><\/dt>\n
Is it safe to delete leftover plugin tables?<\/h3><\/dt>\n
wp_attic_quarantined_*<\/code>, so your site behaves as if it were deleted. If nothing breaks during the purge window, it's removed for good. If something does break, restore it in one click.<\/p><\/dd>\nIs this safe?<\/h3><\/dt>\n
siteurl<\/code>, active_plugins<\/code> and cron<\/code> can never be flagged, and neither can anything on your own protected list or the attic_protected_options<\/code> filter.<\/p><\/dd>\nHow do I undo something?<\/h3><\/dt>\n
Why does my finding say \"review\" instead of \"high\"?<\/h3><\/dt>\n
Does it work with external object caches?<\/h3><\/dt>\n
Multisite?<\/h3><\/dt>\n
Which plugins does Attic work with?<\/h3><\/dt>\n
attic_prefix_map_entries<\/code> filter.<\/p><\/dd>\nDoes Attic delete plugin data?<\/h3><\/dt>\n
What about multisite network-active plugins?<\/h3><\/dt>\n
2.1.0<\/h4>\n\n
\n
wp attic scan<\/code> command (for people who manage sites from the command line) could crash while showing its progress bar.<\/li>\n2.0.0<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n