The real cost of localizing a web app — from free DIY to $50k+ enterprise. Broken down by team size, approach, and what most people underestimate.
"How much does localization cost?" is the first question every founder asks, and the answer is frustrating: it depends. But it shouldn't depend on vibes. Here's a concrete breakdown of what localization actually costs for web applications in 2026, segmented by approach and team size.
Every localization project has three cost components, and most teams only think about one of them:
Before you can translate anything, you need to find the user-facing strings in your codebase and wrap them in a translation function. Rough estimates for a typical Next.js app:
| App size | Components | Estimated strings | Developer time | Cost at $75/hr |
|---|---|---|---|---|
| Small (landing page) | 20-50 | 50-200 | 4-8 hours | $300-600 |
| Medium (SaaS app) | 100-300 | 500-2,000 | 2-5 days | $1,200-3,000 |
| Large (complex platform) | 500+ | 5,000+ | 2-4 weeks | $6,000-12,000 |
This is the cost nobody talks about. It's manual, tedious work — reading every component, deciding which strings are user-facing, wrapping them in translation functions, and creating the initial translation files. It's also the cost Polyglot targets: AST-based scanning reports candidates, and wrapping plans you review do the rewriting for supported patterns. You still review the changes, and unsupported cases stay manual.
The cost of converting your source strings into target languages. This varies dramatically by method:
| Method | Cost per word | 1,000 strings (~5,000 words) × 5 languages | Quality |
|---|---|---|---|
| Professional translator | $0.08-0.20/word | $2,000-5,000 | Highest |
| LLM/AI translation (raw API cost) | ~$0.001-0.005/word | $25-125 | Good for UI strings; review needed |
| Traditional MT (Google/DeepL) | ~$0.0001/word (about $20 per million characters) | ~$3, or $0 within a free tier | Medium |
| Community/volunteer | Free | $0 | Variable |
These are rough ranges. LLM costs depend on the model, and flat-priced tools like Polyglot bundle translation into a plan instead of billing per word. For UI strings (buttons, labels, headings, error messages), AI translation plus human review is a practical default at a small fraction of professional rates. Professional translators are still the right choice for marketing copy, legal text, and brand-sensitive content.
The ongoing monthly cost of your localization platform (prices checked September 22, 2026):
| Tool | Monthly cost (3-person team) | Annual |
|---|---|---|
| Polyglot Team (Pro covers one developer at $49) | $149 ($119 billed annually) | $1,788 ($1,428 billed annually) |
| Crowdin | $59-179 | $708-2,148 |
| Tolgee Cloud | from ~€58 (billed annually) | from ~€696 |
| SimpleLocalize | €12-35 | €144-420 |
| Lokalise | $149+ | $1,788+ |
| Phrase Strings | $525 (billed annually) | $6,300 |
| DIY (JSON + git) | $0 | $0 |
Setup: react-i18next + manual extraction + Google Translate free tier + JSON files in git
| Component | Cost |
|---|---|
| Extraction labor | $1,200-3,000 (one-time) |
| Translation | ~$0 (free MT tier) |
| Tooling | $0 |
| Year 1 total | $1,200-3,000 |
| Ongoing annual | $0 + developer time |
Trade-offs: Lowest cost, highest ongoing developer time. Translation quality is acceptable for common languages, but plan for extra review in languages like Chinese, Japanese, Korean, Arabic, and Hebrew. No detection — new strings are easy to miss.
Setup: Polyglot for detection and translation + any runtime library (one developer on Pro)
| Component | Cost |
|---|---|
| Extraction labor | Reduced — review time for each wrapping plan; unsupported cases stay manual |
| Translation | Included in Pro plan (10,000 lifetime strings, 5 languages) |
| Tooling | $588/year ($468 billed annually) |
| Year 1 total | $588 + review time |
| Ongoing annual | $588 |
Trade-offs: Scanning and plan-based wrapping take on much of the extraction work. Generated translations are reviewed in Polyglot's dashboard, and reviewer seats are free. There's no vendor marketplace or agency workflow. Add developers and you'll need Team ($149/month, or $119 billed annually).
Setup: Crowdin or Lokalise + manual extraction + built-in AI/MT
| Component | Cost |
|---|---|
| Extraction labor | $1,200-3,000 (one-time) |
| Translation | Depends on the plan's AI/MT allowance and any usage beyond it |
| Tooling | $708-1,788/year (Crowdin Pro to Lokalise Explorer) |
| Year 1 total | $1,900-4,800 + translation usage |
| Ongoing annual | $708-1,788 + translation usage |
Trade-offs: Dashboard for non-technical translators. Vendor management if you use agencies. But extraction is still manual, and entry tooling costs more.
Setup: Any TMS + professional translators for all content
| Component | Cost |
|---|---|
| Extraction labor | $1,200-3,000 (one-time) |
| Translation | $2,000-5,000 for 5 languages (one-time, ~5,000 words) |
| Tooling | $708-1,788/year |
| Year 1 total (5 languages) | $3,900-9,800 |
| Ongoing annual | $1,100-2,800 (tooling plus new strings) |
Trade-offs: Highest quality. Required for legal, medical, and regulated content. Overkill for "Save changes" and "No results found."
For most startups and small teams, the optimal strategy is:
This gives you a Year 1 cost of $588 (Polyglot) + $500-2,000 (professional translation for marketing content) = $1,100-2,600 total, plus review time. Your UI strings get scanning, glossary and translation memory, and the copy that carries the most risk gets a professional.
Maintenance cost. Localization isn't a one-time project. Every new feature introduces new strings. Without a check in CI, untranslated strings can slip through on every release. Budget for ongoing i18n work, not just the initial translation pass.
The number of strings. Teams often underestimate how many translatable strings are in their codebase. A "simple" SaaS app can easily have several hundred to over a thousand user-facing strings. Run polyglot scan (free) to get a candidate count before budgeting.
CJK and RTL costs. Chinese, Japanese, Korean, and Arabic/Hebrew translations often cost more (professional) or need more review (AI) than European languages. Budget extra for these language pairs.
Start in your terminal
Install the CLI, run a scan, and see exactly what you're missing. Free, no account required.