Translation is quoted three ways — per source word, per page, or as a subscription or volume plan — and each shifts risk differently: per-word passes document length straight through to you, per-page smooths it but rewards the vendor on sparse pages, and subscription pricing trades unit economics for predictability once volume is steady. None of these is the real cost. The real cost adds the hours someone spends rebuilding formatting, the review time the output demands, coordination overhead, and rework when a document comes back wrong. On structured documents, that second half often exceeds the invoice.
This guide covers how each model behaves, what the quoted rate leaves out, and how to build a total-cost figure you can actually compare across vendors.
Per-Word Pricing and What It Assumes
Per-word is the trade's default. You are charged for source words — occasionally target words, which matters, since translating into German or Spanish typically inflates word count relative to English, and into Chinese deflates it. Always confirm which end is counted.
Per-word pricing is transparent for flowing prose and honest about length. Its assumptions break on documents. A word count treats a 40-page rate table with 900 words the same as a 900-word memo, though one takes minutes and the other can take a day of layout work. It ignores repetition unless the vendor applies fuzzy-match discounts against a translation memory, which is a discount worth asking for explicitly and getting in writing — our guide to translating contracts without terminology errors covers why repetition in legal text is high and worth pricing.
It also creates an incentive you should watch: nothing in a per-word rate pays anyone to preserve your table structure. If the contract prices words and says nothing about formatting fidelity, you have bought words.
Per-Page Pricing and Where It Distorts
Per-page pricing is common in certified, court and immigration work, where the deliverable is a page-for-page document rather than a body of text. It has a genuine virtue: it prices the artefact, so the vendor carries the cost of a dense page.
Watch the definition. "Page" can mean a physical page of the source, a notional page of 250 words, or a target-side page count that grows when the text expands. Those three definitions can differ by a factor of two on the same file. Get it defined in the agreement with a worked example, and note that certified and sworn work carries its own service requirements under ISO 17100, which covers human translation services and explicitly excludes post-editing of machine output.
Where it distorts: sparse documents. A 60-page deck with 15 words per slide costs the same per page as dense prose, and a scanned annex of mostly-blank forms becomes expensive. Where it helps: certified filings, documents where layout fidelity is the deliverable, and any set where you need a predictable number before the word count exists.
Subscription and Volume Models
Subscription or platform pricing charges for capacity — seats, monthly page or character allowances, API volume — rather than per job. The economics invert: the marginal cost of the next document falls towards zero, so behaviour changes.
That behavioural shift is usually the point. When each translation carries a per-word charge, people ration. They translate the twelve documents someone can justify and leave the other three hundred in the data room unread, which is a risk decision made by a budget line. When translation is effectively unmetered, teams translate everything and read what matters — a materially better diligence posture, and one whose value never shows on the invoice.
Subscription favours the buyer at steady, moderate-to-high volume with unpredictable timing. It favours the vendor when volume is low or lumpy. Model your own last twelve months against the plan before signing, and check what happens at the allowance ceiling: overage rates, throttling, or a renegotiation.
The Sticker Price Is Not the Cost
Every quote covers the linguistic transfer. Your actual expenditure includes at least four other lines, and they are borne by staff whose time is not billed to the translation budget — which is precisely why they stay invisible.
Reformatting labour. Someone reconstructs the document when the layout does not survive.
Review time. Someone reads the output against the source, at a cost per hour that usually exceeds the translation rate.
Coordination overhead. Preparing files, splitting and merging, chasing status, handling queries, receiving and filing the return.
Rework. The second pass when something came back wrong, plus the delay it caused.
A vendor whose per-word rate is a third lower and whose output requires four hours of reformatting per document is not cheaper. Total cost is the only figure that can be compared, and it is the one nobody quotes.
Reformatting Is the Line That Hides
This is the largest and most consistently underestimated cost in document translation, because it lands on the person who receives the file rather than on the department that bought it.
The mechanics are mundane and expensive. A translated PDF returns as flowed text and the numbered clause hierarchy is gone. A table's merged cells collapsed, so the totals row no longer sits under its column. Expanded German text pushed a table onto two pages and broke the header repeat. Cross-reference fields became static text, so "see clause 12.4" now points nowhere. A deck's text was translated but the master was not, so half the slides are bilingual. Someone rebuilds all of that by hand, in the evening, before a filing.
Designers and paralegals describe this work constantly — a thread on wasting hours copy-pasting between Word and InDesign is the same labour under a different job title. Measure it before you price anything else: time three real documents, end to end, from receipt to usable.
Turning Review Time into a Number
Review is not a fixed overhead. It scales with how much the reviewer distrusts the output, which is why quality and cost are the same conversation.
Measure it directly. On the same document, in the same conditions, record minutes of review per thousand words for each candidate output, and record how many of the reviewer's changes were substantive rather than stylistic. A system that produces a clean, terminology-compliant draft can cut review to a verification pass; one that produces fluent text with unreliable defined terms forces a full bilingual comparison, which is several times slower.
Then decide how much review each document class actually needs, rather than applying one depth to everything. Post-editing effort in the sense used by ISO 18587 is a defined scope, and defining it lets you cost it. Enforced terminology is the biggest single lever here, which is why our notes on glossary enforcement sit next to the pricing conversation rather than after it.
Building a Comparable Total-Cost Figure
Put every vendor through the same arithmetic on the same document set — ideally the set from your bakeoff, so the quality data and cost data describe the same files.
For each vendor, per document: the quoted charge; measured reformatting minutes multiplied by a loaded internal hourly rate; measured review minutes at the reviewer's loaded rate; coordination minutes; and an expected rework cost, which is the rate of documents requiring a second pass multiplied by the cost of that pass.
Sum it, then divide by pages to get a cost per finished, usable page. That is the number to compare, and it frequently reorders the ranking that the quoted rates produced.
Two adjustments are worth making explicit. Add turnaround as a cost where delay has consequences — a filing deadline missed is not a rounding error. And note capacity: a vendor that cannot absorb 400 documents in a week has a cost you will discover during the transaction rather than during procurement, as our notes on batch translation set out.
Negotiating With the Total in Hand
Once you have cost per usable page, the conversation changes shape.
You can ask a vendor to price the reformatting they cause: if their output needs three hours of rebuild per document, that work has a market rate and belongs in the quote. You can ask for fuzzy-match and repetition discounts as a term rather than a favour. You can move volume between models — subscription for the high-volume readable-draft tier, per-page for the small set of certified filings that must be page-perfect.
And you can price the option value of unmetered translation honestly, instead of pretending the three hundred untranslated documents in the data room were a considered decision.
Bluente's position in that arithmetic is deliberate: the pipeline preserves tables, numbering and cross-references across 120+ languages and 22+ file types, which is a direct attack on the reformatting line rather than the quoted rate. It is the line most worth attacking, because it is the one your own people pay.
Sources and Further Reading
ISO 18587 — post-editing of machine translation output, useful for scoping review effort
ISO 17100 — translation services requirements, which explicitly exclude post-editing of MT
ISO 30042 (TBX) — term base exchange, relevant to repetition and reuse discounts
Copy-pasting translated Word text into layout, r/indesign — the reformatting hours that never appear on a translation invoice
Related Reading
How to translate financial reports without losing table formatting
Automated versus human document translation in regulated industries
Last reviewed 24 August 2026 by the Bluente document engineering team, who build and test the pipeline described here. We update these guides when the underlying standards, regulations or file formats change.
Compare cost per usable page, not cost per word. Try BluTranslate free.