Lang Forge gives you two visual editors — a split-screen view inside the WordPress admin for focused translation work, and a frontend click-to-translate toolbar that appears directly on your live site. Use whichever one fits the task.
If you’ve translated a WordPress site with a classic translation plugin, you know the pain. You’re translating a blog post and suddenly you realize you don’t remember which field you’re in. You translated the excerpt, but what about the Yoast meta description? Did you do the featured image alt? What about that Elementor button label you didn’t realize existed?
A visual editor fixes this by showing you everything at once — either side-by-side in the admin, or in place on the page as your visitors see it.
Open any post’s translation and you get a two-column view. The source language is on the left — read-only — and your translation is on the right. Each column is a mirror image: the same fields in the same order, so you never lose your place.
What you get inside the split-screen editor:
A prominent button at the top of the editor runs AI translation on every remaining field in one batch. Cost is estimated first. After the AI finishes, the quality-check pass highlights any flagged sentences so you can focus your review on the parts that need attention.
The split-screen editor is great for long-form content. But if you’re tweaking a button label, a widget heading, or a menu item, you want to see it on the page. That’s what the frontend visual editor is for.
Switch your site to the frontend editor view, and a toolbar appears at the top of every page. Click any piece of text on your live site. A popup opens with:
This is the same workflow TranslatePress popularized, but Lang Forge implements it on top of our full integration stack — so it works on Elementor, Divi, WPBakery, WooCommerce, and every custom field we support.
If you have a glossary entry — for example, “Lang Forge” marked as “do not translate” — the editors highlight any translation that violates the rule. You see the problem immediately, not after you publish.
The visual editor isn’t a generic textarea wrapper. It understands:
| Use the split-screen editor when… | Use the frontend editor when… |
|---|---|
| You’re translating a full blog post | You’re fixing a single button or label |
| You need to see all fields at once | You want to preview the result in context |
| You’re working through a long post methodically | You’re doing small fixes across many pages |
| You want keyboard-driven workflow | You want to click things |
| You need to AI-translate an entire post | You’re reviewing translations on the live site |
Both editors are included in every paid plan.
Get Lang Forge — from $54/year →
Every paid plan includes both editors, AI Translate All, and glossary validation.
We use analytics and marketing cookies (Google Analytics, Google Ads, Meta) to understand traffic and improve the site. Strictly-necessary cookies are always on. See our Privacy Policy.