Machine translation post-editing โ MTPE โ is the workflow where a machine translates first and a human linguist then reviews and corrects the output to an agreed quality level. It has quietly become the default production model for a large share of professional translation volume, yet buyers often encounter it only as a line item they do not understand, or worse, receive MT output sold as human translation.
Understanding what MTPE is โ and what it should cost and deliver โ puts you back in control of that conversation.
How the MTPE workflow actually runs
A professional MTPE project has more structure than “run it through an engine and fix typos”:
- Preparation: Source text is cleaned and segmented; terminology glossaries and translation memories are loaded so the engine respects your established terms.
- Engine selection and configuration: Different engines handle different language pairs and domains differently. A legal text in German and a software UI in Korean do not belong on the same default engine. Custom-trained or domain-adapted engines improve raw output substantially for technical content.
- Machine translation: The batch run โ the fast, cheap part.
- Post-editing: A professional linguist reviews every segment against the source, correcting meaning errors, terminology, grammar, register, and anything the machine handled badly โ not merely polishing what reads oddly in the target language.
- QA and delivery: Automated checks (numbers, tags, terminology consistency) plus, for higher-stakes content, a second reviewer.
The two quality levels โ and why the distinction matters
The industry recognizes two service levels, and quotes vary widely because vendors mean different things by “post-editing”:
| Light post-editing | Full post-editing | |
|---|---|---|
| Goal | Understandable, factually accurate | Comparable to human translation |
| What gets fixed | Meaning errors only | Meaning, style, grammar, register, terminology |
| Best for | Internal docs, support tickets, gisting, content with short shelf life | Customer-facing content, manuals, marketing, anything published |
| Relative cost | ~40โ60% of human translation | ~60โ80% of human translation |
| Risk if misused | Awkward but harmless internally | Public credibility damage |
The critical question to ask any vendor quoting MTPE: which level, and what exactly does the editor correct? A quote without that answer is not comparable to any other quote.
Where MTPE fits โ and where it does not
Strong fit:
- Technical documentation with repetitive, constrained language (manuals, specs, knowledge bases)
- High-volume content where human translation is economically impossible (support articles, product data, user-generated content)
- Frequently updated content where speed beats elegance
- Content already controlled by good terminology management โ machines follow glossaries well
Poor fit:
- Marketing copy, slogans, brand voice โ the machine produces grammatically fine, persuasively dead text, and fixing it takes longer than translating fresh
- Content with wordplay, humor, or cultural metaphor
- Highly ambiguous or badly written source text โ machines amplify source problems
- Regulated content where liability demands full human accountability (though MTPE with expert review is gaining acceptance here case by case)
This mirrors the broader human vs. machine translation decision โ MTPE is not a third option so much as a dial between the two, set per content type.
What MTPE should cost you
The economics are real but often oversold. Honest expectations:
- Savings of 20โ40% versus full human translation are typical for suitable content in mature workflows โ not the 70โ90% sometimes promised. The editing is skilled labor, and on poor machine output it can take as long as translating from scratch.
- Savings grow over time. As your translation memory and terminology database accumulate, both the machine output and the editing speed improve. Year two of an MTPE program is meaningfully cheaper than year one.
- The metric that matters is cost per published word, not cost per machine-translated word. If post-editing to your quality bar erases the savings, MTPE is the wrong tool for that content โ regardless of what the quote says.
How to start
The sensible entry point is a pilot: one representative document type, one language pair, both quality levels defined in writing, results measured against a human-translated baseline for accuracy and turnaround. A competent localization partner will propose exactly this rather than a blanket MTPE contract โ and will tell you which of your content types should stay fully human.
If you are evaluating MTPE for technical documentation or multilingual content at scale, talk to our team โ we will assess fit content type by content type. We respond within one business day.