Every WordPress site collects database clutter over time. Revisions pile up, transients expire without being removed and deleted content leaves metadata behind. The DualFix database scanners find this clutter and remove it through the same classification, verification, Safety Snapshot and audit stages as every other scope. They are included in both editions.
Where to find it: Cleanup Launcher → Cleanup Flow. In DualFix Free, this flow is the database cleanup. In DualFix Pro, the database scanners run as part of Full Cleanup.
What the database scanners find
| Scanner | What it finds | What cleanup does |
|---|---|---|
| Revisions | Stored older versions of posts | DualFix Pro: removed after verification. DualFix Free: listed for review, not removed |
| Autosaves | Automatic drafts WordPress saves while you edit | Listed for your review; never deleted by DualFix |
| Trashed items | Posts in the trash | Listed for your review; never deleted by DualFix |
| Expired transients | Temporary cache values whose expiry has passed | Removed after verification |
| Orphaned post, comment and user meta | Metadata rows whose parent post, comment or user no longer exists | Comment meta: removed after verification. Post and user meta: DualFix Pro removes them after verification; DualFix Free lists them for review, not removed |
| Stale cron hooks and inactive widgets | Scheduled tasks and widget entries left behind by removed code | Reported for your review; never deleted by DualFix |
| Heavy autoloaded options | Options WordPress loads on every page request, analysed by size | Reported for your review; never deleted by DualFix |
DualFix does not change autoload flags, delete cron events or remove widget entries. These findings come with their reason, and the decision stays with you.
Autosaves and trashed posts stay in review on purpose: an autosave can hold edits that were never saved, and WordPress empties the trash on its own, after 30 days by default. Deleting a revision does not change the post it belongs to.
Clean the database
- Make sure the Setup Wizard profile is confirmed and a recent backup is restore-ready.
- Open Cleanup Launcher and click Run First Scan (or Run Scan) under Cleanup Flow.
- Read the findings by class. Items of active plugins are marked protected.
- Click Create Preview, then Run Verify, and read the reason for any blocked item.
- Click Confirm Cleanup. DualFix takes a database backup (while Backup before cleanup is on, the default) and a Safety Snapshot, and removes only the items Verify approved as safe.
- Read the audit and check your site.
Each item is checked again at the moment it is deleted. A post that left the trash after the scan, or a transient that is no longer expired, is skipped.
Data of active plugins stays protected
Even inside the database scope, data that belongs to an active plugin is protected. The plugin registry knows the meta keys, options and tables of WordPress core, the block editor, page builders (Elementor, Divi, WPBakery), WooCommerce, custom field plugins (ACF, Meta Box, Pods), SEO plugins (Yoast SEO, Rank Math), multilingual plugins (WPML, Polylang) and the ARN Smart plugins WebPix, Linkix and Clonex. Data of plugins the registry does not know still goes through the dependency checks of the verification stage.
Keep clutter from coming back
Cleaning once is the easy part; revisions and transients return within weeks.
- Schedule the same guarded cleanup with Auto Mode. See Automate maintenance with Auto Mode.
- In DualFix Pro, Smart Policies can limit stored revisions and clean expired transients on a throttled schedule. See Prevent clutter with Smart Policies (Pro).