Plugin info

Total downloads: 121,655
Active installs: 2,000
Total reviews: 10
Average rating: 4.7
Support threads opened: 2
Support threads resolved: 0 (0%)
Available in: 8 language(s)
Contributors: 8
Last updated: 7/15/2025 (168 days ago)
Added to WordPress: 2/15/2021 (4 years old)
Minimum WordPress version: 6.6
Tested up to WordPress version: 6.8.3
Minimum PHP version: 8.0

Maintenance & Compatibility

Maintenance score

Maintained • Last updated 168 days ago • Support resolved 0% • 10 reviews

44/100

Is Convert to Blocks abandoned?

Likely maintained (last update 168 days ago).

Compatibility

Requires WordPress: 6.6
Tested up to: 6.8.3
Requires PHP: 8.0

Similar & Alternatives

Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.

No similar plugins found yet.

Description

Convert to Blocks is a WordPress plugin that transforms classic editor content to blocks on-the-fly. After installing Gutenberg or upgrading to WordPress 5.0+, your content will be displayed in “Classic Editor Blocks”. While these blocks are completely functional and will display fine on the frontend of your website, they do not empower editors to fully make use of the block editing experience. In order to do so, your classic editor posts need to be converted to blocks. This plugin does that for you “on the fly”. When an editor goes to edit a classic post, the content will be parsed into blocks. When the editor saves the post, the new structure will be saved into the database. This strategy reduces risk as you are only altering database values for content that needs to be changed.

Note that Inner Blocks Transforms is only supported with the Gutenberg Plugin 10.9.0+.

Installation

Manual Installation

  1. Upload the entire /convert-to-blocks directory to the /wp-content/plugins/ directory.
  2. Activate Convert to Blocks through the ‘Plugins’ menu in WordPress.

Frequently Asked Questions

How Do I Know It’s Working?

Find a classic editor in the post, try to navigate away from the page. You will get an error saying your changes will be discarded. This is because Convert to Blocks converted your content to blocks on the fly and those changes will be saved when you update the post.

Will Convert to Blocks Handle My Custom Blocks?

By default it will not.

Will Convert to Blocks Handle Nested Blocks?

Nested / Inner Block support does not work with Gutenberg bundled with WordPress Core <=5.7.2. This feature needs the Gutenberg Plugin >=10.9.0.

Review feed

Mehedi Hasan
7/3/2023

Handy!

Works as expected.. very useful tool.
Adrian
11/6/2023

Very good, bulk is slow and error prone, but not developers fault

Very good plugin, which helps to migrate a lot of posts. We have a project with ~8000 posts, which needs to be converted. Only standard text and images... Unfortunatly WordPress itself is pushing Gutenberg, but not providing tools for this task. This plugin is helping a lot. Basically it opens the browser, clicks the button, saves the post, opens the next post ... A quite clever solution, which unfortunately is slow and sometimes breaks.. Means you have to monitor the task and reload the tab from time to time...
megane9988
5/20/2024

It works like a magic!

When you run a command and open a URL, the browser opens articles one after another and converts them into blocks. It magically automatically converts blocks quickly and accurately.

Screenshots

  1. Bulk migration using the <code>wp convert-to-blocks start</code> WP-CLI command that converts posts iteratively in the browser without requireing any manual input.

    Bulk migration using the wp convert-to-blocks start WP-CLI command that converts posts iteratively in the browser without requireing any manual input.

Changelog

1.3.4 – 2025-07-15

1.3.3 – 2025-07-14

  • Added: Link to settings page from the plugin list page (props @badasswp, @dkotter via #195).
  • Changed: Bump WordPress “tested up to” version 6.8 (props @jeffpaul via #199, #200).
  • Changed: Bump WordPress minimum supported version to 6.6 (props @jeffpaul via #199, #200).
  • Fixed: Fix PHP warning due to undefined array key (props @sksaju, @dkotter via #202).
  • Fixed: i18n functions being called too early, causing PHP Notices (props @stormrockwell, @dkotter, @dsawardekar via #203).
  • Security: Bump cookie from 0.4.2 to 0.7.1, express from 4.21.0 to 4.21.2, @wordpress/e2e-test-utils-playwright from 1.7.0 to 1.18.0, serialize-javascript from 6.0.0 to 6.0.2 and mocha from 10.4.0 to 11.1.0 (props @dependabot, @Sidsector9 via #194).
  • Security: Bump axios from 1.7.4 to 1.8.3 (props @dependabot, @iamdharmesh via #196).
  • Security: Bump http-proxy-middleware from 2.0.6 to 2.0.9 and tar-fs from 3.0.8 to 3.1.0 (props @dependabot, @dkotter via #206).

1.3.2 – 2025-02-03

1.3.1 – 2024-08-20

1.3.0 – 2024-05-14

View historical changelog details here.