InPage Translate is a no-.po-file alternative to Loco Translate for plugin and theme text. Click a text, type the translation or let a free service write it, and save. No second site per language.

A shop plugin's "Add to cart" button becomes French. This is the whole job: open, click, type, save.
Right-to-left scripts such as Arabic and Hebrew flip the page for you.
Icons are from each plugin's WordPress.org page and belong to their owners. InPage Translate is not affiliated with them.
Open a screen in wp-admin or on your site, turn on InPage Translate, and click any text on it. It works the same on every plugin.



The example uses an online shop. The same steps work for any plugin or theme that uses WordPress translations.
Upload the plugin and activate it. A "InPage Translate" item appears in the WordPress toolbar, in the admin and on your site.
Every text the page can translate gets a dashed outline. Green ones are already translated, with a small language tag.
Type the translation, or press Generate and a free service writes a draft. Drafts stay "needs review" until you approve them.
The text changes on the page at once and stays after you leave. Every change keeps the earlier text, so a mistake is one click from undone.
Most tools switch a whole site from one language to another. InPage Translate lets each text keep the language you gave it, so one page can mix Spanish, German, Japanese and Arabic while you work, or while your customers read.
Everything you translate on the page lands in one tidy place, with progress for every plugin and language.
| Original text | Translation | Status |
|---|---|---|
| Add to cart | Ajouter au panier | Approved |
| Sale! | Angebot! | Approved |
| Your cart is currently empty. | Tu carrito está vacío. | Needs review |
| Proceed to checkout | 注文手続きへ | Approved |
Search, filter by plugin, language or status, and approve in bulk.
The scanner reads a plugin's code to count every text it can translate, so you always know how far you are.
Loco Translate, WPML and TranslatePress are great tools. WPML and TranslatePress turn a whole website into a multilingual one, and Loco Translate edits language files. InPage Translate does one job, fast: change the words your plugins and theme show, where you see them.
| Type | InPage Translate | Loco Translate | WPML | TranslatePress |
|---|---|---|---|---|
| Click a text on the page to translate it | Yes | No, edit in a file editor | Mostly in a separate editor | Yes |
| Each text keeps its own language on one page | Yes | No | No | No |
| No .po or .mo files to edit, upload or update | Yes | No, file based | Yes | Yes |
| Free machine translation, no key needed | Yes, with review status | Needs a key | Paid credits | Needs a key |
| Placeholder checks (%s, %d) before saving | Yes | Partly | Partly | No |
| Translates posts, pages and menus | No, by design | No | Yes | Yes |
| Price | Free | Free and Pro | Yearly plans | Free and Premium |
you want to fix or localise the words of plugins and themes, quickly, without touching files.
you need your own posts, pages and menus in several languages, with a language switcher and translated URLs.
Comparison from each product's public information. Plans and features change, so check their sites before you decide.
A translation with an extra %s or %d would break your site, so it is refused. A missing one is saved with a warning.
Google, DeepL, Microsoft and MyMemory. Add your own keys for the paid ones. Nothing is sent until you agree.
Every change keeps the text before it. Undo a mistake in one click, even a deleted translation.
CSV, JSON, PO and MO. Move translations between sites or hand them to a translator.
See how much of each plugin is translated, per language, and translate the missing texts a few at a time.
Administrators always. Let editors translate too, while keys, imports and settings stay with admins.
Arabic, Hebrew, Persian and Urdu pages turn right to left on their own.
Tab to a text, Enter to open it, Escape to close. Dialogs and lists are labelled for screen readers.
Translations live in your database. Only the one text you choose to generate is ever sent out, and only after you say yes.
Install InPage Translate, open the plugin's screen in wp-admin or on your site, and click InPage Translate in the toolbar. Click any outlined text, pick a language, type the translation or press Generate, and save. The translation is stored in your database, so there is no .po or .mo file to edit, upload or update.
For translating the text of plugins and themes, yes. Both tools do that job. Loco Translate edits .po and .mo language files in an editor, while InPage Translate lets you click the text where it appears on the page and keeps the translation in your database. They do different jobs, so they can also sit side by side.
Only for plugin and theme text. WPML and TranslatePress also translate your posts, pages and menus, and InPage Translate does not, by design. If you need a fully multilingual site with translated pages and URLs, use one of them. If you only need to change the words your plugins and theme show, InPage Translate is quicker and free.
With any plugin or theme whose texts go through WordPress translation functions, which is nearly all of them, WooCommerce, Yoast SEO, Elementor and WPForms included. Text typed straight into a template, or stored in the database, is not covered.
The plugin is free, with no account and no subscription. Machine translation works without a key through free services (MyMemory and the Google Translate web endpoint). You can add your own DeepL, Google Cloud or Microsoft Translator key for better quality and limits.
No. Translations are saved in your own database and applied as the page is built, so there is no file to edit, upload or update. You can still export a PO, MO, CSV or JSON file whenever you want one.
Yes. They live in your database, not in the plugin's folder, so updating a plugin or theme does not overwrite them.
They do different jobs, so they can sit side by side. InPage Translate changes the words you see on a page, one text at a time. Loco Translate edits language files. WordPress loads the language files first, then InPage Translate replaces the texts you translated.
Saved translations show for visitors once the cache is cleared. If a translation does not show, clear your page cache and CDN first.
Write to us. We read everything, and we answer.
[email protected]Free. No account. Install it, click the toolbar item, click a text.