WordPress 7.2 Will Lay Groundwork for Native Multilingual — What It Actually Means

With WordPress 7.0 shipped and 7.1 planned for August, attention turns to WordPress 7.2 (expected December 2026) — the release the roadmap pencils in for laying groundwork toward native multilingual support, the fourth and final phase of the Gutenberg project.

What Phase 4 covers

Phase 4 is about core understanding that a post can exist in multiple languages: data model, admin UI, switching. It is the plumbing layer that today’s plugins each reinvent.

What Phase 4 does not cover

Even a complete Phase 4 will not translate anything. Connecting Google or DeepL, managing per-character costs, caching translations, emitting hreflang clusters, visual post-editing — these are product decisions core has never intended to absorb. The likely outcome mirrors block themes: core ships primitives, plugins ship the experience.

What to do meanwhile

Waiting for native multilingual means conceding years of international traffic to competitors who ship languages now. A string-table approach like Transxlate’s is also low-risk: your source content stays untouched, so any future core migration starts from a clean position.