admin-plugins author calendar category facebook post rss search twitter star star-half star-empty

Tidy Repo

The best & most reliable WordPress plugins

3 WordPress Plugins for Resetting a Website After Switching from Elementor to Gutenberg

3 WordPress Plugins for Resetting a Website After Switching from Elementor to Gutenberg

Ethan Martinez

November 4, 2026

Blog

Use WP Reset first, then clean the database, then audit unused media. That order gives you the safest reset path after moving from Elementor to Gutenberg. Elementor is still used on over 10 million WordPress installs, so many site owners face this cleanup after rebuilding pages with blocks [source: WordPress.org].

TLDR: Start with WP Reset if you need to reset a staging site, remove test content, or roll back bad cleanup work. For example, if a 60 page site has 18 Elementor pages rebuilt in Gutenberg, you can reset the staging copy, test the new block pages, and avoid touching the live site. Use Advanced Database Cleaner for leftover database clutter, then use Media Cleaner to find images no longer used by Elementor layouts. Do not run any of these on a live site without a full backup.

Why resetting matters after leaving Elementor

Switching from Elementor to Gutenberg is not just a design change. It often leaves behind old templates, revisions, shortcodes, unused CSS, custom fields, and media files. Some of it is harmless. Some of it slows admin work and bloats backups.

The annoying part is that a page can look “clean” in the editor while the database still holds old Elementor data. It drives me crazy that a simple page rebuild can leave dozens of unused images and revisions behind. That is why a reset plan is better than random deletion.

1. WP Reset

WP Reset is the best first plugin for this job because it is built for controlled resets, test cleanup, and recovery work. It is especially useful if you are rebuilding the site on staging after removing Elementor layouts.

The official site, WP Reset, explains the plugin’s broader reset and recovery tools. For this use case, the key value is simple: you can clean out development clutter without manually hunting through every setting screen.

Best uses after switching to Gutenberg:

  • Reset a staging site before rebuilding pages with blocks.
  • Remove test posts, pages, comments, and demo content.
  • Create snapshots before cleanup steps.
  • Recover faster if a cleanup breaks layouts or settings.
  • Clear transients and other temporary data.

Use it when the site feels messy before the rebuild has even started. If you imported demo content, tested three themes, and built trial Elementor pages, WP Reset can save hours.

The catch is simple. A full reset is serious. It can remove content and settings. Do not click reset because a page looks ugly. Use it on staging first. Check backups. Then check them again.

2. Advanced Database Cleaner

Advanced Database Cleaner is a strong second step once your Gutenberg pages are in place. It focuses on database cleanup. That makes it useful after Elementor has been disabled or removed.

Elementor sites often collect revisions, drafts, expired transients, orphaned metadata, and old options. Some come from Elementor. Some come from themes and add ons used with it. Either way, they can make the database heavier than it needs to be.

What it helps clean:

  • Post revisions from old Elementor pages.
  • Auto drafts created during redesign work.
  • Trashed posts and comments.
  • Expired transients.
  • Unused database tables from removed plugins.

This plugin is not as dramatic as a reset tool. That is a good thing. It lets you clean in smaller steps. Expect to waste time if you skip that approach and try to delete database rows by hand.

Before using it, take a database backup. Then clean one category at a time. After each step, open key pages, forms, menus, and the block editor. If something breaks, you will know which action caused it.

3. Media Cleaner

Media Cleaner is useful when the visual rebuild is finished. Elementor pages often use background images, section images, icons, and duplicate uploads. Once those pages are rebuilt in Gutenberg, many files sit unused in the media library.

This plugin scans your site and flags media files that may no longer be used. That can reduce storage, shrink backups, and make the media library easier to manage.

Use it for:

  • Old Elementor background images.
  • Duplicate design assets.
  • Unused landing page graphics.
  • Images from deleted sections and templates.

Be careful here. Media detection is not perfect. Some images may be used in custom fields, widgets, theme settings, or block patterns. Always review the results before deleting files. If the plugin offers a trash or quarantine feature, use it first instead of permanent deletion.

A safe cleanup order

  1. Clone the live site to staging.
  2. Back up files and the database.
  3. Use WP Reset if the staging site needs a clean base.
  4. Rebuild key pages in Gutenberg.
  5. Disable Elementor only after testing.
  6. Clean the database with Advanced Database Cleaner.
  7. Scan media with Media Cleaner.
  8. Test forms, menus, search, mobile pages, and checkout.

Final recommendation

If you want the least risky path, use WP Reset on staging before any major rebuild work. Then use Advanced Database Cleaner to remove database leftovers. Finish with Media Cleaner to clear unused assets.

That sequence is practical. It avoids blind deletion. It also respects the biggest rule of WordPress cleanup: reset only what you understand, and always keep a way back.