With TranslatePress, translating is the easy part. The hard part is everything after — a brand name that got translated when it shouldn’t have, a client who wants one term changed across 400 strings, a backup you need before migrating hosts, or a test run that filled your database with thousands of junk translations.
Doing any of that by hand means clicking through the TranslatePress editor string by string, or running raw SQL against the wp_trp_gettext_* tables and hoping you don’t break the site.
Hybrid AI Translator for TranslatePress Pro adds three management tools that handle exactly these jobs from the WordPress admin — no phpMyAdmin, no SQL, no plugin surgery.
Key takeaways
- Find & Replace fixes a wrong term across every translated string in one operation, instead of one at a time.
- Export / Import saves translations and settings as JSON — your rollback point and your staging-to-live path.
- Delete ALL gives you a safe, scoped reset instead of truncating database tables by hand.
- The human-reviewed flag stops future automatic runs from overwriting wording you already approved.
1Edit Translations + Find & Replace
This is the bulk editor TranslatePress doesn’t ship with.
Instead of opening the visual editor and hunting for a string, you get a searchable table of every stored translation for a language. Filter it, edit values inline, and — the part that saves hours — run find & replace across all translations at once.
What it actually solves
- Brand names that got translated. Your product is called “Awning Kits” in every language. The AI helpfully turned it into “Markisen-Sets” in German. One find & replace, fixed everywhere.
- Terminology changes. A client decides the German site should say “Warenkorb” instead of “Einkaufswagen” — 300 strings, one operation.
- Post-migration cleanup. Old domain or old company name baked into translated strings? Replace the string, not the strings one at a time.
- Tone fixes. Swap formal “Sie” phrasing for informal “du” across a whole language.
2Export / Import Translations & Settings
Every translation you’ve paid an API to generate is an asset. This feature treats it like one. Export writes your translations and your plugin settings to a JSON file. Import loads them back.
Why that matters
- Backups before a risky run. About to re-translate a whole language with a new model? Export first. If the output is worse, import the old file and you’re back where you were.
- Staging to live. Translate on staging, review, edit, then export and import into production. Your live site never runs an untested translation pass.
- Host migration. Moving hosts or rebuilding the site doesn’t mean paying for translation twice.
- Multi-site reuse. Same product catalog on several domains? Translate once, import everywhere.
- Settings portability. Provider chain, tone and style rules, glossary configuration — the whole setup travels with the file, so you’re not reconfiguring from memory on every site.
Because it’s plain JSON, the file is readable and diffable if you want to inspect exactly what changed between two runs.
3Delete ALL Translations
A deliberate, one-click reset for a language.
Sometimes the right move isn’t fixing translations — it’s throwing them away. You tested three providers and the database is full of half-finished output. You changed your tone-and-style settings and want a clean run. You’re switching from Google Translate to a proper LLM and don’t want old strings blended in with new ones.
The manual alternative is truncating TranslatePress’s tables by hand. This does it safely from the dashboard, scoped to what you choose.
Where these fit in the bigger plugin
The three tools above are the management layer. Underneath, Hybrid AI Translator connects TranslatePress to translation engines your way:
| Capability | What it does |
|---|---|
| Multiple providers | Google Translate, OpenAI-compatible APIs, Groq, OpenRouter, DeepSeek |
| Local AI | LM Studio and Ollama — translate on your own machine, no per-word API cost, no data leaving your network |
| Provider chain | Set a fallback order so a rate limit or outage on one provider doesn’t stop the run |
| Tone & style control | Professional, casual, simple, technical, or your own brand-voice instructions |
| Glossary | CSV import (DeepL-compatible) for exact-match terms the AI must not paraphrase |
| Translation logs | See every provider call — essential when debugging why one string came back wrong |
| Human-reviewed flag | Protect approved wording from being overwritten |
| License & auto-updates | Standard activation, updates delivered in wp-admin |
The reason to combine an LLM with a glossary and a bulk editor is simple: machine translation gets you 90% of the way at near-zero cost, and these tools let you own the last 10% instead of paying a translator to redo everything.
A practical workflow
- Build the glossary first. Add product names, brand terms, and technical vocabulary before translating anything.
- Set tone & style to match your site’s voice.
- Configure a provider chain — a fast cheap model first, a stronger one as fallback.
- Run the translation in TranslatePress.
- Export immediately. That’s your baseline backup.
- Spot-check the output. Use Find & Replace for anything systematically wrong.
- Mark corrected strings human-reviewed so they survive future runs.
- Export again — this is your good copy.
If a later run goes badly: Delete ALL, import the good copy, try again.
Requirements and pricing
You need the TranslatePress plugin installed, plus your own API key from whichever provider you choose. Keys aren’t included — or run LM Studio / Ollama locally and skip API costs entirely.
All plans include a 14-day money-back guarantee through Freemius.
Frequently asked questions
Can I undo a Find & Replace?
Not as a single undo step — which is exactly why Export exists. Export before any bulk operation and you always have a restore point.
Does Delete ALL remove my original content?
No. It clears stored translations, not the source posts and pages. Export first anyway.
Will my manual edits get overwritten the next time I run automatic translation?
Not if you mark them human-reviewed. That’s exactly what the flag is for.
Can I move translations from a staging site to live?
Yes — export JSON on staging, import on live. Your settings travel with the file.
Do I need an API key to use the plugin?
You need either an API key from a supported provider, or a local model running in LM Studio or Ollama. The plugin does not resell translation credits.
Is this an official TranslatePress product?
No. Hybrid AI Translator is an independent add-on and is not affiliated with TranslatePress, Google, OpenAI, Groq, OpenRouter, DeepSeek, LM Studio, or Ollama.
Stop fixing translations one string at a time
Bulk editing, JSON backups, a safe reset, and eight AI providers — from $5 a year, with a 14-day money-back guarantee.
Hybrid AI Translator for TranslatePress Pro is developed independently and is not affiliated with or endorsed by TranslatePress, Google, OpenAI, Groq, OpenRouter, DeepSeek, LM Studio, or Ollama. All trademarks belong to their respective owners.
