Disable Gutenberg Autosave vs Classic Editor

Head-to-head on the signals that matter, from the public WordPress.org data.

Disable Gutenberg Autosave

by ska-dev

Health A85

Classic Editor

by WordPress.org

Health A92

Active-install trajectory

Disable Gutenberg Autosave Classic Editor

Active installs, each indexed to 100 at the start of the window. A line above 100 is growing its install base, below 100 is shrinking.

Metric	Disable Gutenberg Autosave	Classic Editor
Active installs Modeled from the public "N+" band and recent downloads.	2K–3K	8M–9M ✓
Install trend Change in active installs across the charted window.	0% ✓	-11%
Overall health	A · 85	A · 92 ✓
Maintenance How recently the plugin was updated.	100/100	100/100
Rating quality Volume-adjusted review quality.	78/100	98/100 ✓
Support Share of forum threads marked resolved.	70/100	70/100
Rating (adjusted)	4.12★	4.89★ ✓
Reviews	11	1,246 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	92/100 ✓	83/100
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	Low	Low
Last updated	9d ago ✓	3mo ago
Downloads · 30d	1.7K	843.8K ✓
Category	Blocks	Blocks

✓ marks the stronger plugin on each row. Rows where they're level show no marker.

Release activity

Disable Gutenberg Autosave Classic Editor

7-day average daily downloads. Downloads spike for about a week after each release as the install base re-downloads, so read this as release cadence, not growth.