Convert to Blocks

76 Quality Score

Active Installs

15/30

With only 2,000 active installs, the plugin has a modest footprint, though it solves a problem most sites only face once during a transition period.

Update Freshness

25/25

The plugin was updated within the last release cycle and requires recent PHP and WordPress versions, signalling an actively maintained codebase.

User Rating

14/15

A 94 out of 100 rating from 10 reviewers is strong, though the small sample size means the score should be read with some caution.

Support Health

8/15

There are zero support threads on record, which means there is no public track record of how the developer handles troubleshooting or edge cases.

WP Compatibility

15/15

The plugin is tested with WordPress 7.0 and requires PHP 8.0 plus WordPress 6.6, indicating forward-looking compatibility requirements.

Scores higher than 51% of indexed plugins

About

Convert to Blocks transforms classic editor content to blocks on-the-fly.

Active Installs 2k+

Rating ★★★★½ 4.7/5

Last Updated 2026-09-15 12:28am GMT

Requires WordPress 6.6+

Tested Up To 7.1

Requires PHP 8.0+

Security History

1 known vulnerability, all patched

1 Critical

Most recent: March 18, 2022

View details ▸

What It Does

Convert to Blocks takes content written in the WordPress classic editor and renders it as Gutenberg blocks dynamically, without requiring editors to manually re-save every post. It acts as a translation layer so legacy posts display cleanly inside the block-based editor and on the front end.

Who It's For

This is a sensible pick for site owners with large archives of classic editor content who want Gutenberg compatibility without a costly manual migration. Agencies maintaining multiple legacy client sites will also benefit, since the plugin handles conversion transparently on the front end.

Who Should Skip It

If your site was built entirely in the block editor from day one, or you prefer to perform a one-time manual conversion and clean up legacy markup, this plugin adds no value. Sites with very small post counts (under a few dozen) will not see meaningful benefit from automating what could be done by hand.

The Bottom Line

Convert to Blocks does one specific job well and earns a 76.38 out of 100 overall quality score, helped by strong maintenance and compatibility marks but held back by a small user base and zero public support history. It is worth considering for legacy content-heavy sites that want a low-effort path to Gutenberg, but anyone needing a broader block toolkit should look at higher-install alternatives like Spectra.

Pick Spectra when you need a full block library and design toolkit rather than just a classic-to-block conversion utility.

Breadcrumb NavXT 88/100

Choose this when breadcrumb navigation is your primary concern, as it is a purpose-built SEO utility, not a migration tool.

PDF Embedder 86/100

Opt for PDF Embedder if embedding documents is the real goal, since it targets a completely different use case.

Flexible Table Block 83/100

Pick this when your migration pain point is specifically tables created in the classic editor that need proper block representation.

The Icon Block 83/100

Choose The Icon Block if you simply need a reliable icon block to supplement your Gutenberg setup after migration.