Every plugin you've ever installed left something behind. Bloated options, dead cron jobs, orphaned database tables, leftover transients \u2014 years of \"uninstalled\" plugins that never actually cleaned up after themselves. This bloat slows down every page load, because WordPress autoloads a lot of it on every single request. If Site Health told you that you have too many autoloaded options, this is what to do about it.<\/p>\n\n
Attic finds it. Safely.<\/p>\n\n
The problem with every other cleanup plugin:<\/strong> they delete first and ask questions later. One false positive and you've lost site settings.<\/p>\n\n How Attic is different \u2014 Quarantine, Never Delete:<\/strong>\n- Tables you quarantine are renamed, not dropped \u2014 restorable by default for 30 days (configurable)\n- Every option is backed up before removal\n- Nothing is called orphaned with confidence until Attic has confirmed the owning plugin's actual files<\/em> are gone from disk and searched your code for references \u2014 weak evidence stays at \"review\" rather than becoming a recommendation<\/p>\n\n What Attic finds:<\/strong><\/p>\n\n Two rules outrank every feature:<\/p>\n\n Every finding shows its evidence inline: which rule fired, what it attributed to and whether that plugin exists on disk, how many code references were found, and the size. A finding you cannot audit is a finding you should not act on.<\/p>\n\n Who this is for:<\/strong>\n- Site owners who've installed\/removed a lot of plugins over the years\n- Agencies maintaining client sites and doing housekeeping\n- Anyone whose Site Health page flags \"autoloaded options\" and doesn't know what to do about it<\/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 for automation and CI\/CD pipelines:<\/p>\n\n Catch regressions without manual triggers. Schedule scans via WP-Cron or system cron, and receive an email digest when complete:<\/p>\n\n Visualize your database health over time:<\/p>\n\n Network admin dashboard for managing database health across all sites:<\/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 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
\n
wp_attic_quarantined_*<\/code>), never dropped until a purge window passes.<\/li>\nwp-config.php<\/code>, looking for every candidate name before promoting anything to high confidence. (PHP, JS, JSON and .inc<\/code> files; node_modules<\/code>, vendor<\/code>, dist<\/code> and build<\/code> directories are skipped.)<\/li>\n<\/ol>\n\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<\/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\nScheduled Scans<\/h4>\n\n
\n
Trend Charts<\/h4>\n\n
\n
Multisite Support<\/h4>\n\n
\n
Attribution 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\nFilters<\/h3>\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
Is 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.0.0<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n