Convert to Blocks transforms classic editor content to blocks on-the-fly.
As of April 2026, Convert to Blocks is a WordPress block plugin with 2.0K+ active installations and a 4.7/5 rating from 10 reviews. It has been downloaded 131K+ times in total. Requires WordPress 6.6+ and PHP 8.0+. Available on WordPress.org since 2021. Recently updated within the last 3 months. Download volume is stable this week. Top alternative: Spectra Gutenberg Blocks – Website….
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 th…
You might wonder why you need this plugin when the “Convert to blocks” button is right there at the top of every Classic block. Well, click that and it will eff up any images you had using the <figure class=”alignleft”> (or alignright) code. The default WP “convert to blocks” strips out the figure code entirely and POOF your alignment class is gone and your caption is off god knows where. But not this plugin! Add this and when you open your classic page in the block editor, it preserves the figure tag and alignment class. Saved me having to redo image settings on 600 post. Thank you 10up.
All this does is convert posts into HTML blocks, same as happens if you manually tell WordPress to convert a classic HTML post to blocks. Ok, it saves a single mouse click… why install a plugin to save one mouse click?
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.
Saves me a lot of time. Used it two times on large projects.
I did not try the bulk option, but I just read that it can have bugs or crashes. Probably due to server load or unusual post content?
What I did instead was create a button that that when pressed automatically opens in a new tab the 20 posts from the Posts Table view.
I then waited for them to load.
After they were all loaded I went to each page and updated the page.
I then waited a while for all of them to be saved and double checked in the Posts Table if all the posts were converted to the Block editor. The little icon showing if the post is Classic or Block comes very handy!
Once I confirmed that all 20 posts from the Posts Table view were converted I moved to the next page and repeated the process.
This semi-automated process helps prevent “bugs” or perhaps random server spikes.
I was running this on my own private cloud server with little resources. Surprisingly saving 20 posts at once was possible without any crashes.
I did not have any bugs or issues.
Thank you for creating this plugin!
I have a load of old posts and pages done in the original WP editor which desperately needed converting to blocks in order to play nicely with a child theme I was working on. We know the block editor has the facility to go through posts/pages one-by-one and convert to blocks – but this is painful….
This plugin seems to do that job for you, but silently in the background.
Once I’d activated it and saved the settings, nothing happened….at least, not visually. It was only when I started to look at the entries made in the legacy editor that I could see they had been converted to block format – silently!
The only improvement I can suggest is a message on the plug-in interface page which says something like, “when you have ticked the checkboxes, press the save button and your conversion will commence as a background task.”
I don’t know if that would make sense in keeping with the way the plug-in works. I only have a couple of hundred posts so it did the job quickly. I don’t know how it would perform on a site with thousands of old posts in legacy editor format. Either way, thanks to the author for saving me the time.
| WordPress | 6.6+ requiredTested up to 6.9.4 |
| PHP | 8.0+ required |
Plugin data sourced from WordPress.org. Analysis and metrics by PluginSift.