Disable Gutenberg Autosave

75 Quality Score

Active Installs

15/30

The popularity score is modest relative to similar editor tools because only around 2,000 active installs use it, indicating it serves a narrow but engaged audience rather than mass-market users.

Update Freshness

25/25

Maintenance is excellent given the recent last-updated date and confirmed compatibility with WordPress 7.0, signalling that the author is actively tracking core changes.

User Rating

13/15

The 88 out of 100 rating from 11 reviewers is solid, though the small sample size means sentiment could shift quickly and should not be taken as broadly validated.

Support Health

8/15

Support health is average at best since there are no public support threads or resolved tickets, leaving unanswered how responsive the author is when issues arise.

WP Compatibility

15/15

Compatibility is perfect on paper, with verified WordPress 7.0 support, a clean PHP 7.4 baseline, and no conflicting requirements reported in the metadata.

Scores higher than 43% of indexed plugins

About

Allows to control Gutenberg autosave interval or disable autosave completely.

Active Installs 2k+

Rating ★★★★ 4.4/5

Last Updated 2026-08-20 4:53am GMT

Requires WordPress 5.0+

Tested Up To 7.1

Requires PHP 7.4+

✓ No known vulnerabilities

What It Does

Disable Gutenberg Autosave lets site administrators configure or completely turn off the autosave and revision behaviour in the WordPress block editor. It targets a single, well-defined problem: reducing database write frequency, lowering revision clutter, and freeing up editor resources that autosave can consume on busy sites.

Who It's For

This plugin is a good fit for sites where editors produce long-form or structured content and find autosave disruptive, as well as for agencies and developers running low-resource servers who want predictable database behaviour. It is also useful for teams where multiple authors hit the editor simultaneously and revs pile up quickly.

Who Should Skip It

If you rely on autosave as a safety net against browser or connection crashes, or if your editorial workflow benefits from a full revision history, you should skip this plugin and disable it only after careful consideration.

The Bottom Line

Disable Gutenberg Autosave is a narrow, well-maintained utility that does one job and does it cleanly, earning a 75.48 overall quality score. It is worth installing for teams that find autosave disruptive or for sites straining under heavy revision load, but most casual bloggers will not notice enough benefit to justify another plugin. The lack of public support threads is the main reason it does not score higher.

Pick Spectra when you need a full block library, starter patterns, and design tooling rather than just autosave controls.

Kadence Blocks — Page Builder Toolkit for Gutenberg Editor 89/100

Choose Kadence Blocks if you want richer layout controls, responsive settings, and a 600,000-install user community behind the toolkit.

Starter Templates – AI-Powered Templates for Elementor & Gutenberg 89/100

Opt for Starter Templates when you primarily need ready-made site designs and AI-assisted imports rather than editor performance tuning.

MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites 89/100

Select MainWP Child when managing many client sites from a single dashboard is your priority, since autosave is outside its scope.

Classic Widgets 89/100

Go with Classic Widgets if reverting to the legacy widget UI is your goal, as autosave control is unrelated to widgets.