Estimate translation cost and schedule
Default rates reflect 2025 English-source industry averages across service tiers. Adjust the rates or export the CSV table to compare against vendor quotes.
All-in total
$19,578
4 locales · 20,000 words
Translation program
$10,378
Translation + LQA + PM overhead
Engineering (one-time)
$9,200
i18n framework · Webfonts · Per-locale integration
Cost breakdown
- Translation$7,520(38%)
- LQA$1,504(8%)
- PM overhead$1,354(7%)
- Engineering$9,200(47%)
Parallel duration
6 days
All locales at once
Sequential duration
23 days
One translator across all
Per-locale breakdown
| Locale | Rate × | Translation | LQA | Subtotal | Days |
|---|---|---|---|---|---|
| es-ESSpanish | 1.0 | $1,600 | $320 | $1,920 | 5.7 |
| fr-FRFrench | $1,760 | $352 | $2,112 | 5.7 | |
| de-DEGerman | $1,920 | $384 | $2,304 | 5.7 | |
| ja-JPJapanese | $2,240 | $448 | $2,688 | 5.7 | |
| Translation subtotal | $7,520 | ||||
| LQA subtotal (1 round) | $1,504 | ||||
| PM overhead (15%) | $1,354 | ||||
| Translation program | $10,378 | ||||
Vendors usually charge a per-locale minimum of $50–100; this estimate applies $50.
1 · Source word count
Planning figures: small app ~5,000 · web product ~50,000 · enterprise app ~200,000+
2 · Translation tier
Shortens the schedule; costs coordination and consistency.
Typical 2025 figures: 15–20% in-house, 25–30% with a full-service vendor.
4 · Target locales (4)
Or load a preset
Rank what to add next in the launch planner (these locales count as shipped)
5 · Translation memory
Repetitions and fuzzy matches bill below the new-word rate.
6 · Engineering setup
One-time engineering work that per-word rates do not cover, priced from the locale set.
- i18n framework$6,000
- Webfonts (1 script)$1,200
- Per-locale integration (4)$2,000
One-time total$9,200
Estimation notes
- Count only new and modified source words for incremental releases. Translation memory (TM) matches discount repeated and fuzzy segments.
- Service tier affects total budget more than locale count. Use light MT post-editing for high-volume support documentation, and reserve TEP (translation, editing, proofreading) for core UI and regulated copy.
- Include at least one in-context LQA pass for UI releases, and add a second pass for regulated markets or marketing headlines.
- Parallel schedules assume all locales start simultaneously with separate linguists. Use the sequential estimate when a single internal reviewer signs off on multiple locales.
Related: Launch planner (prefills this estimator from a shortlist) · String audit (checks the returned files)