Translation Cost per Word: What You Will Pay in 2026

In the US today, human translation costs roughly $0.09 to $0.40 per word, depending on language pair, subject matter, and required turnaround time. Alternatively, AI workflows for machine translation with human post-editing (MTPE) are often more cost-efficient but are still billed under the same pricing model.

Unfortunately, the per-word pricing model was designed for finished documents, not for websites. Websites are ever-changing and often need monthly, if not weekly, updates, and when translations are charged per word, the cost can increase exponentially, regardless of whether you’re using human translators, AI tools, or a combination of both.

If you ask any translation vendor “how much per word,” you’ll probably get a different answer each time, and those answers don’t cover what happens when you need to edit a page. 

So what’s the true cost of translation per word in 2026?

We’ve broken down what it costs to translate a website, what per-word invoicing leaves out for a live website, and how to realistically think about your bill when your content is never truly “done.”

What translation really costs per word

Let’s start with the plain numbers. The Translation Company’s 2026 pricing guide puts US rates at $0.09 to $0.40 per word depending on the project. Smartling’s 2026 rate breakdown narrows the professional band further, to $0.15 – $0.30 per word for US-based translators. Smartling also notes that AI-assisted translation typically starts at $10 to $20 per million characters rather than a per-word fee. Wordly cites a similar range for document translation, $0.08 to $0.30 per word.

These numbers only tell you what the buyer pays, not what the translator earns.

But why does that matter?

Most freelance translators report take-home rates closer to $0.05 to $0.10 per word, less than half of what agencies quote clients. The price difference covers project management, quality review, tooling, and margin. This is worth knowing because it shows which side of that gap a quote is describing before you compare vendors.

Where you land, as the buyer, in that range depends on several factors. For example, English to Spanish translation costs sit near the bottom of the pricing range because it’s a common translation pair and translators are abundant. However, when you ask for something rarer, such as English to Icelandic, the price will climb because fewer translators can do the job.

Subject matter will also push rates up. Legal, medical, and technical content commands a premium price because mistranslations and the specialists needed to handle changes are costly and hard to find. Additionally, turnaround time plays a role. Smartling lists urgency among its seven core rate factors, and agencies routinely add a surcharge for compressed deadlines. Volume, however, can cut the other way. Sometimes bigger projects earn a per-word discount, though minimum fees often erase savings on small jobs.

Finally, the quality tier can change pricing. Oftentimes, machine translation, MTPE, and full human translation with review are all priced in entirely different tiers, rather than points on a sliding scale. Additionally, certified or sworn translations, the kind required for legal and immigration paperwork, always carry a premium of their own and are usually priced separately from the general document rate.

So how do these pricing factors play out in reality?

The Translation Company’s guide prices a 5,000-word employee handbook translated into Spanish at $0.14 per word, costing about $700 before a repetition discount. However, if you translate that same handbook into Spanish and French, the bill roughly doubles to about $1,400.

Finally, required turnaround time, alongside volume and complexity, changes rates because they’re so volatile. A project split across a small team of translators and reviewers will move faster than one assigned to a single person. However, adding a review pass will stretch that timeline, but improve quality, and change pricing. Overall, even with a seemingly simple “cost per-word” fee, it’s almost impossible to guess the final cost for a project.

What per-word pricing hides on a website project

The standard per-word pricing model works if you’re translating a single document because it assumes a fixed, finished piece of text. Unfortunately, a website is neither fixed nor finished.

This means that per-word quotes can overlook a lot of key information:

• Which word count you’re paying for matters. Buyers don’t often check whether they’re billed for source words or translated words, and the two differ significantly by language pair (i.e., German expansion vs English). Make sure you know which one you’re paying for because these numbers are rarely the same.
• New content will accrue new bills. Every new blog post, product description edit, or pricing page update is a new billable word under per-word models. If your website is growing, your invoicing will never really stop.
• Website variants and plurals will cost more. Any website with product options, size names, or color names will pile up as near-duplicate text, and a strict per-word count will treat every variant as a brand new word.
• Minimum fees rack up prices. Fixing even a single sentence on a landing page can trigger a project minimum that can cost more than the words themselves are worth.
• Project management overhead adds up. Worldly’s own rate guide notes that agencies often add a 10 to 20 percent fee on top of translation costs to cover coordination.

None of this makes per-word pricing dishonest. It’s a great model for documents that get translated once and stay translated, but the minute you apply that to something that, by definition, is always changing, the per-word pricing model begins to leave much to be desired.

The visit-based alternative

So how should you reframe before finalizing a budget for a website translation project? You need to think about what you want. You’re creating an ongoing experience for visitors who land on your page, and pricing by the word measures the wrong unit for that job.

Bablic’s pricing tracks monthly pageviews on your origin site (the site your visitors land on, before any translation layers), not a Words Served allotment or a one-time per-word invoice. 

The result? You’re not re-billed sentence by sentence every time a page changes. Translations are stored in translation memory and reused automatically, so a product description you already translated won’t generate a new invoice line if it appears elsewhere on the site.

Setup is a single line of JavaScript, not a document handoff or a build-pipeline integration. This matters because most teams pricing a website translation project don’t know their site’s total word count going in.

Instead, pageview-based metrics sidestep the guessing game and allow you to scope controls to limit or hide what gets translated. This way, you’re not paying to translate your admin footer or a staging subdomain. Additionally, a glossary layer allows you to lock brand names and set fixed phrasing. Meanwhile, Bablic’s in-context editor will let a Spanish-speaking colleague spot-check the live translated page instead of a translator working blind from a spreadsheet.

If you’re weighing this against a document-style quote, How Bablic Works and Bablic’s Current Plans lay out the mechanics in more detail than any per-word rate card will.

How to budget your project

If you’re deciding which model fits your project, the split is simpler than it looks:

• Translating a fixed document? A handbook, a legal contract, a one-time report. Per-word or per-page (roughly 250 words per page) pricing is the right tool. You know the word count up front, the content won’t change after delivery, and a quote against a static file is easy to compare across vendors.
• Translating a living website? Product pages, blog content, a marketing site that gets edited weekly. A subscription or usage-based model maps cost to the value you’re getting (visitors served in their own language), instead of penalizing you every time you add a page or fix a typo.

So, if a new invoice every time you edit a sentence bugs you, per-word isn’t the right model for your project. For a deeper look at what website-specific translation and localization involves beyond raw word counts, see our guide to website localization services. And if part of your calculation is whether free machine translation is good enough on its own, read whether Google Translate is reliable for typical business content before committing to a paid tier.

Translation cost per word is a real number, useful for pricing a document. It’s the wrong question for a website, though. The honest budgeting conversation there is cost per month for a site that stays translated, not cost per word for a site that’s translated once and starts drifting out of date the next day.