AI Translation Engine by Volade
LLM drafts with glossary, routing stays yours.
AI Translation Engine by Volade prepares translation drafts with glossary protection — complements Polylang and WPML; does not replace multilingual routing.
3-step workflow
- 1Open Volade → AI Translation Engine
- 2Load glossary · apply FR→EN blog or EN→ES commerce
- 3Queue drafts — export JSON / hand off to agency
Multilingual reality 2026
Routing is solved — glossary-safe drafts are not
Teams buy WPML, wire Polylang+DeepL, or overlay TranslatePress — without an offline draft queue that protects brand terms.
~$99–399+/yr
Typical multilingual / MT stack
Translation drafts, glossary lock, 4 presets, offline prep — optional LLM; Polylang/WPML keep routing.
Glossary
Term protection
4
Workflow presets
Offline
Draft prep free
JSON
Free export
At a glance
WPML and TranslatePress sell the full multilingual stack; DeepL bills per character. AI Translation Engine by Volade v1.0.0 complements Polylang/WPML: protected glossary, translation queue, target drafts (offline prep), four presets (FR→EN blog, EN→ES commerce, agency handoff, glossary-only) and JSON export — optional OpenAI-compat, without replacing multilingual routing.
Screenshots
Full-page real admin UI — presets, diagnostics and detailed settings.
2026 pricing comparison
Pay for a full multilingual suite, or ATE at $0
WPML is expensive. Polylang needs DeepL. TranslatePress overlays. ATE drafts offline — optional LLM on V+.
Core free · glossary · queue · JSON export
~$99–399+
WPML / MT / overlay / yr
$0
AI Translation Engine Volade
Why buying a full multilingual stack is often the wrong first move
WPML sells the full stack. Polylang needs DeepL. TranslatePress overlays the site. You still need glossary-safe drafts without replacing routing.
The multilingual lock-in problem
You need drafts + glossary — not a forced stack swap.
WPML sells the full multilingual stack. Polylang needs DeepL for MT. TranslatePress overlays the front end. DeepL plugins translate without a Volade-style draft queue. None give offline glossary-safe prep that complements routing you already have.
- WPML: powerful but expensive full-stack multilingual CMS
- Polylang + DeepL: routing + API costs, limited glossary workflow
- TranslatePress: visual overlay — different editorial model
- DeepL for WP plugins: MT only — no draft queue / agency handoff
- No FR→EN blog / EN→ES commerce / Glossary only presets
- Many tools require cloud MT — brand terms leave unprotected
The Volade answer
Draft, protect, export — from wp-admin.
ATE is an LLM translation engine with glossary protection — not a multilingual router. Offline draft prep, 4 presets and JSON export — optional LLM translate on V+. Keep Polylang or WPML for language routing.
- Dedicated Volade → AI Translation Engine dashboard
- Complements Polylang / WPML — does not replace routing
- Offline draft prep — no API required for queue & glossary
- 4 presets: FR→EN blog, EN→ES commerce, Agency handoff, Glossary only
- Optional LLM translate (V+)
- Free JSON export — queue, glossary, health
- Glossary lock for brand and legal terms
- wp ate status | glossary | queue | translate | preset | export
4 translation presets
FR→EN blog, EN→ES commerce, Agency handoff or Glossary only — one click, terms protected.
FR→EN blog
Editorial tone for articles — glossary terms locked across the draft queue.
EditorialEN→ES commerce
Product and category copy — SKUs and brand names protected.
CommerceAgency handoff
Export-ready draft packs for freelancers and agencies — review flags included.
AgencyGlossary only
Sync and validate glossary entries without running a full translate pass.
Glossary4 translation statuses
Queued, Translating, Draft ready and Glossary locked — scored from queue state and term protection.
Source selected — waiting in the draft queue.
Draft generation in progress (heuristic or LLM).
Translation draft prepared — editor can review.
Protected terms enforced — low rewrite risk.
Statuses reflect queue and glossary locks at check time — refresh after preset or glossary changes.
Same post, glossary-safe draft
FR→EN blog preset — brand terms locked while the draft queue fills.
Glossary
Brand & legal terms loaded — lock enabled.
Preset
"FR→EN blog" applied — editorial tone.
Queue
Offline draft prep — optional LLM on V+.
Export
ate-queue.json for audit or handoff.
Translate preview
FR→EN blog — post #482
Queued drafts and exported JSON for the agency folder or editor board.
Real scenarios
What changes after activation.
FR blog → EN
Before: Copy-paste into DeepL · brand terms drift
After: FR→EN blog + glossary lock → draft queue
Fewer rewrites
EN catalog → ES
Before: SKU names mangled by raw MT
After: EN→ES commerce preset → protected terms
Commerce-safe
Agency delivery
Before: Spreadsheets + lost context
After: Agency handoff preset → JSON export
Clean handoff
Polylang site
Before: Routing OK, no draft engine
After: Keep Polylang + ATE drafts
$0 core
What a multilingual suite doesn't offer alone
LLM drafts, glossary protection, offline prep, presets and export — without replacing Polylang or WPML routing.
Draft translation engine
LLM-ready drafts — not a language router.
Glossary protection
Lock brand, legal and SKU terms across the queue.
4 presets
FR→EN blog, EN→ES commerce, Agency handoff, Glossary only.
Offline draft prep
Queue and glossary without an API key.
Optional LLM translate
Cloud/LLM on V+ — never mandatory.
JSON export
Queue, glossary and health — free.
WP-CLI + REST
wp ate status / glossary / queue / translate / preset / export.
Complements Polylang/WPML
Routing stays in your multilingual plugin.
Complements Polylang/WPML: they route languages — ATE drafts translations with glossary protection; it does not replace multilingual routing.
What teams pay for translation
Public pricing July 2026 — full-stack multilingual vs draft engine + glossary.
WPML Multilingual CMS
~$99–199/yr
Full stack: routing, translation UI, addons — expensive for draft-only needs.
Polylang + DeepL
~$0–99+ / API
Routing free or Pro; DeepL API or plugin for machine translation.
TranslatePress
~$99–299/yr
Visual overlay translator — different model than draft queue + glossary.
DeepL for WordPress plugins
API credits
MT quality — no built-in draft queue or Volade glossary workflow.
AI Translation Engine by Volade
$0
Draft queue, glossary protection, 4 presets, REST + WP-CLI. Optional LLM on V+.
WordPress translation landscape 2026
Full-stack multilingual, overlays and raw MT vs a glossary-safe draft engine — ATE complements routing, it does not replace it.
WPML
Full multilingual CMS — routing, UI, addons.
Limit: Expensive stack when you only need glossary-safe drafts.
Polylang + DeepL
Popular routing + machine translation combo.
Limit: API costs · limited draft queue / glossary workflow.
TranslatePress
Visual front-end overlay translator.
Limit: Overlay model — not draft queue + agency export.
DeepL for WP
High-quality MT via DeepL plugins/API.
Limit: MT only — no Volade glossary / offline prep.
Agency-only workflow
Spreadsheets and email handoffs.
Limit: No queue status, no glossary lock, slow cycles.
Do nothing
Ship one language only.
Limit: Missed markets — no draft pipeline.
Comparison table — 5 approaches
ATE vs WPML, Polylang, DeepL and TranslatePress.
| Feature | ATE Volade | WPML | Polylang | DeepL for WP | TranslatePress |
|---|---|---|---|---|---|
| Glossary-protected drafts | ~ | ~ | ~ | ||
| Offline draft prep (no API) | ~ | ~ | |||
| Complements Polylang/WPML routing | ~ | ||||
| Does not replace language routing | |||||
| 4 translation presets | ~ | ~ | |||
| Draft queue + agency export | ~ | ~ | |||
| Optional LLM translate (V+) | V+ | ~ | ~ | ||
| Built-in WP-CLI | ~ | ||||
| No account (core) | ~ | ~ | ~ | ||
| Typical annual cost | $0 | $99–199 | $0–99+ | API | $99–299 |
Multilingual routers remain useful — ATE complements with glossary-safe drafts without replacing language routing.
Three tiers, one plugin
Queue, glossary, presets and JSON export free. Volade account for REST. V+ for optional LLM translate.
No account
- Draft queue
- 4 statuses
- Glossary protection
- 4 presets
- Offline prep
- JSON export
- Queue log
Volade account
- REST ate/v1
- Glossary sync via API
- Scheduled export
V+ Premium
- Optional LLM translate
- wp ate network status
- Multisite glossary rollup
WP-CLI `wp ate` and REST `ate/v1` for status, glossary, queue, translate, preset and export across staging and production.
WP-CLI
status, glossary, queue, translate, preset and export over SSH — `wp ate preset --name=fr-en-blog`.
wp ate status wp ate glossary wp ate queue wp ate translate wp ate preset wp ate export
Multisite
Glossary and queues per site; harmonized rollup on V+.
- Per-blog glossaries
- Consolidated JSON export
- Agency network defaults
Download
Install the ZIP, open Volade → AI Translation Engine, pick a preset — queue drafts with glossary protection.
ZIP with Volade SDK — Volade → AI Translation Engine.
- 1Plugins → Add New → Upload → ZIP → Activate
- 2Volade → AI Translation Engine
- 3Load glossary → pick preset → queue → export drafts
First draft queue in under 60 seconds
FAQ
Polylang, WPML, DeepL, glossary, offline prep, multisite and Volade account.
No. ATE is a translation draft engine with glossary protection. Keep Polylang/WPML (or similar) for multilingual routing.
Free vs V+ Premium
The extension works without an account. V+ unlocks premium on this extension and the full catalog.
| Feature | Free | V+ |
|---|---|---|
| Protected glossary & translation queue | ||
| Offline target drafts (review) | ||
| 4 presets & JSON export | ||
| Batch capped at 3/run without account | ||
| OpenAI-compat + ate/v1 REST | ||
| Unlimited, Polylang/WPML stubs & multisite |
Reviews, discussions & updates
Share your experience with AI Translation Engine by Volade and follow the latest releases.
Ready to queue glossary-safe drafts?
Download AI Translation Engine by Volade v1.0.0 — presets + glossary, no signup.
Download v1.0.0