Your CAT tool doesn't do LLM pre-translation properly — or at all.

PTI does — one payment, free upgrades, no subscription. It's one page. One mandatory file, two optional ones, one button. Everything else — locked segments, fuzzies, repetitions — is there if you need it, out of the way if you don't.

You are doing MTPE you didn't choose. Your CAT tool's LLM integration either doesn't exist, costs extra, or doesn't work. You need something that runs upstream of your workflow — before you start working in your CAT tool — using the LLM of your choice.

What PTI does

Pre-translate your XLIFF, SDLXLIFF, MQXLIFF, DOCX, XLSX, JSON or HTML file with the chosen LLM — then open them in Trados, memoQ, or any CAT tool that can work with XLIFF 1.2, XLIFF 2.0, or TMX files, or any editor that can take DOCX, XLSX, JSON or HTML files. Your workflow doesn't change.

PTI calls the LLM API directly from your machine — OpenAI, Anthropic, Mistral, Google, xAI, or a local model running in Ollama or LM Studio. No intermediate server. No vendor infrastructure handling your content in between.

33,130 words of legal and financial text, extensive style guide, 200-term termbase. 40 minutes. $2.69 in API costs using Claude Sonnet 4.6. That's a real production run, not a demo.

Need more? The termbase cap is user-configurable — tested up to 844 terms on the same file.

Where does your CAT tool stand?

Your setup What your vendor offers PTI
Trados Studio 2026 AI Bridge — GPT, Claude, Gemini and more. Upgrade required. ✓ Works upstream
Trados Studio 2024 OpenAI only natively — broken in practice. ✓ Works upstream
Trados Studio 2022 and older Nothing from RWS. ✓ Works upstream
memoQ Translator Pro (freelance) Nothing. AGT is TMS-only, starts at €2,904/year. ✓ Works upstream
Wordfast Pro Neural and adaptive MT via Custom MT connector. No native LLM pre-translation. ✓ Works upstream
CafeTran Espresso BYOK AI integration — GPT, Claude, Gemini and more. ✓ Works upstream

PTI is CAT-tool agnostic. It pre-translates your file before you start working on it — in Trados, memoQ, Wordfast, CafeTran, or any other tool that works with XLIFF 1.2, XLIFF 2.0, or TMX files or any editor that can take DOCX, XLSX, JSON or HTML files.

We tested PTI against Trados Studio 2024 SR1 on a 1,710-word file with an 844-term termbase and an extensive style guide. Trados crashed on the first attempt. On the second, it took 6 minutes and translated two thirds of the segments. PTI processed the same file with the same inputs in 4 minutes — full output, all segments.

You control where your content goes

PTI runs on your machine. When you hit Translate, the request goes from your computer directly to the API endpoint of the provider you chose — OpenAI, Anthropic, Mistral, Google, or xAI — or to a local model running entirely on your own hardware via Ollama or LM Studio. There is no PTI server in between. No one at PTI sees your content. With a local backend, no request leaves your machine at all.

You supply your own API key. That means you are a paying business customer of your chosen provider — not a consumer using a free tier. Business API customers have different contractual data handling terms. Each provider publishes these. You can read them before you choose.

What happens inside the provider's infrastructure is governed by their terms — not ours. Read them before you choose a provider. That part is in your control too.

One thing to be clear about: if your client contracts prohibit sending content to third-party APIs, using your own key doesn't change that. BYOK means the content goes to your chosen provider — not to us — but it still leaves your machine via API. If that's a constraint for specific work, use Ollama or LM Studio instead. With a local backend, nothing leaves your machine.

Try PTI for free

Download the zip. Unpack. Run start.bat. No installation, no account.

Claim a free 3-day trial key to unlock the full app including output downloads.

Download PTI — Windows
Start your free 3-day trial
Buy a licence — €65

Licence