Interpres user guide

What it does

Interpres puts the admin screens of your installed plugins and themes into your language. It never touches plugin code: it writes the language files WordPress already looks for (wp-content/languages/plugins/{domain}-{locale}.mo). Bundled translations and wp.org language packs are kept; Interpres only fills the gaps. Unlike a browser translator it does not break layouts, and it works in every browser and on every device.

	Free	Pro
Translation packs, coverage audit, PO import/export and bundles, editor, source tooltip, JS text swap	✓	✓
AI translation of any plugin (your own key or Interpres Cloud), change-only re-translation after updates, batch queue, cost estimate, glossaries, sharing	–	✓

First setup

1. Settings → Interpres → Settings tab: choose the target language (defaults to the site language).
2. If the site language differs from the target (say, an English site with a Korean admin), turn on Admin screens in the target language only.
3. Turn on Translation packs to look up packs for your installed plugins on api.interpres.ing. Only text domains and versions, the locale and a hash of your site URL are sent, and nothing is sent until you turn it on.
4. Every settings card collapses when you click its header.

Reading the list

Column	Meaning
Green dot before the name	A translation made by Interpres is applied
Status chip	Bundled / wp.org pack / No existing translation / Translated · not applied / In progress
Coverage bar	Share of admin strings translated, from any source. "Coverage" at the top is site-wide
"Pack available · N strings"	A pack for this exact version. "Pack for v6.2.0 available" is a nearby version (only overlapping strings)
"Gaps" filter	Items with untranslated strings, largest gap first
Sort	Top right of the list: themes first · name, applied by Interpres first, lowest coverage first, …

What you can do

• Install pack: downloads and applies in one click. Only packs reviewed by the Interpres team are offered. After a plugin update, Auto-update packs (Settings) fetches the matching newer pack.
• Request pack: tell us which plugins you want; the most requested get built first.
• Import PO: upload a .po or a .zip bundle exported from another site. The target is matched by the text domain inside the file; "apply right after import" is optional.
• Export bundle: every translated item as one .zip of .po files. A new site is "install Interpres → upload the bundle".
• View · Edit: fix any string in place; edits apply immediately and survive re-translation and re-install.
• Edit suggestions: when you correct a string of an installed pack, the correction is sent to the server as a suggestion (with packs on). Once accepted it reaches every site using that pack; accepted fixes are pulled in on install and daily. Strings you edited yourself are never overwritten.
• Source tooltip (Settings): hover a translated phrase to see the original; Alt-click opens it in the editor.
• Unapply: removes the generated language files. The translation itself stays and can be applied again.

Pro

1. Settings → License: paste the key from your purchase email (it starts with IP-) and activate. The key is sent once and never stored; each site gets its own site key. The site limit depends on your plan.
2. LLM service: Interpres Cloud (credits, no key needed) or your own Anthropic, OpenAI or Gemini key (perpetual licenses only; yearly subscriptions translate with Interpres Cloud). With Cloud, strings another site already translated are free and only new strings use credits (1 credit = 1,000 strings). Large jobs run as a server batch in 10–30 minutes; small changes finish right away.
3. Translate on a row shows an estimate (strings, cost, time) and starts. Check several rows and use Translate selected to queue them.
4. After a plugin update, Translate changes re-translates only what changed. "Auto-translate after plugin updates" (Settings) does it in the background.
5. Hard-coded JS strings (Settings, on by default): React screens and alert messages that language files cannot reach are extracted, translated and swapped in when the screen renders.
6. Share translations (Settings, on by default): when you apply a translation you made, the pack and how it was made (model, token cost, versions) go to the Interpres server, get reviewed, and are then offered to other sites as a pack. Rows show "Shared · in review / published / not published". Translations installed from a pack or imported from a bundle are not sent.
7. Updates: Pro announces new versions in the WordPress plugins screen (checked daily). Until the free plugin is on wp.org it is announced the same way.

FAQ

• Some strings went back to English after a plugin update — those are new strings. A refreshed pack fills them automatically; Pro fills them at once with "Translate changes".
• Will wp.org language packs overwrite Interpres translations? — Domains applied by Interpres are skipped by automatic translation updates, and re-applied after a manual one. Unapply, and the wp.org pack is used as usual.
• What leaves my site? — Free: text domains, versions, locale and a site-URL hash, only after you turn packs on. Pro: the plugin strings being translated (to your provider or Interpres Cloud) and, with sharing on, the applied translation and how it was made. Never content, user data or keys.
• Uninstalling — settings and work files are removed; language files stay so the admin keeps its translations. To remove those too, add define('INTERPRES_UNINSTALL_REMOVE_LANGUAGE_FILES', true) to wp-config.php.
• Contact — hello@interpres.ing