In WordPress 7.0, the post editor canvas will always run inside an iframe, even if older blocks registered with Block API version 1 or 2 are present.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Program transcript

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from February 9 to 15, 2026.

In WordPress 7.0, the post editor canvas will always be inside an iframe, even if there are older blocks registered with Block API version 1 or 2.

Until now, the editor was already an iframe in the Site Editor and the Template Editor, but in the post editor there was an inconsistency. The presence of blocks using API v2 could “force” the legacy non iframe mode, resulting in two different behaviors depending on context and therefore two separate compatibility surfaces for users, plugins, and extensions.

WordPress has been preparing this change for years, first by using the Template Editor as a testing ground, then adding transitional measures and notices in 6.9, and finally closing the inconsistency in 7.0 with a single operating mode.

It matters for three practical reasons.

First, ...

iframed!