Frequently asked questions

About the product

Do I still need WPML?

Yes. WPML manages multilingual content in WordPress: the language switcher, the URL structure, which post is a translation of which. We do not replace any of that. We do the part WPML asks a translator to do, and hand the result back in the format WPML expects.

Do I have to install a plugin?

No. Nothing is installed in WordPress and nothing runs on your server. You export files, we translate files, you import files. Your site is unchanged until you import.

What happens to my translations if I stop paying?

Nothing. They are already in your WordPress install as ordinary WPML translations, and the XLIFF files are yours to keep. There is no subscription to lapse and nothing that expires or is withdrawn. This is the main structural difference from proxy-based translation services, where cancelling can take your translated site with it.

Which languages are supported?

Translation targets are driven by your WPML export, and the engine covers the major European languages. The free demo is limited to a smaller set - English, Spanish, German, French and Italian - because it runs synchronously in your browser.

The source language is read from the file itself. WPML always records it, so you do not choose it.

What file formats do you support?

XLIFF as exported by WPML, which is XLIFF 1.2. That includes content with Gutenberg blocks, shortcodes, custom fields and custom post types - the formatting is preserved rather than merely tolerated.

Quality

How good are the translations?

Good enough that the work becomes reviewing rather than rewriting, which is the honest bar. They are not a substitute for a professional human translator on copy where a single sentence carries real commercial weight.

The most useful thing you can do is try the demo on your own content. It runs the real engine, so what you see is what you would get.

How do I know a translation did not break my page?

Every translation is checked against its source before it is accepted: matching markup, intact shortcodes and placeholders, protected terms still present, plausible length. A unit that fails is retried once under stricter instructions, and if it still fails it is flagged for review rather than shipped quietly. See How it works.

Will it keep my brand names intact?

If you tell it which ones they are. Add them as protected terms and they are declared before translation and verified afterwards. Without a glossary, product names get translated - fluently and wrongly. See Brand voice.

Can I edit a translation I do not like?

Yes, inline, at any point. Edits are stored immediately and every download is rebuilt from the current stored translations, so what you download always matches what you see on screen. You can also ask for a single unit to be translated again.

Cost

How does pricing work?

Pay as you go, per page, from EUR 0.02 - cheaper at volume. No subscription, no monthly minimum, no credit packs to buy up front. You are billed for translation work actually performed, which is why duplicates and cache hits cost you nothing.

Why is my second run so much cheaper?

Duplicate detection within an upload, and caching across uploads. Re-translating a site after editing three paragraphs bills you for roughly three paragraphs. See Why the second run costs less.

Can I see the cost before committing?

Yes. Every upload shows an estimate - upper and lower bound - before anything runs, along with the unit and duplicate counts behind it. Nothing is spent until you confirm.

Can I use my own AI provider account?

Not currently. The per-page price includes the translation itself, so there is no separate API bill and no keys to manage.

Your content

Do you keep my content?

Your uploads and translations are stored so that jobs can be resumed, reviewed, re-downloaded and served from cache on later runs. That storage is what makes the second run cheap. Demo content submitted without an account is held only briefly and then removed.

Is my content used to train models?

No.

Can two of my sites share translations?

No, and deliberately. Translations are scoped to a project, and a project is one website with one voice. Sharing them across sites would mean one site's tone leaking into another's pages.

Practical

How long does a batch take?

Roughly a minute per file, running sequentially - a pace chosen to stay well inside rate limits rather than to win a benchmark. A hundred-file batch is something you start and come back to. Progress is reported per unit, and you can close the tab.

What if a run stops halfway?

Continue it. It resumes exactly where it stopped and does not re-bill anything already translated. A run that ended early for any reason - a stopped job, an interrupted batch, an allowance running out - is picked up the same way.

Can I bring in translations done elsewhere?

Yes. Import already-translated XLIFF and it becomes reviewable here, and reusable as cache on later runs. It performs no translation and costs nothing.

Something is not covered here

The rest of these docs go deeper: How it works for the pipeline, Getting started for the round trip, and Glossary of terms if a word here was unfamiliar.