Website & App Localization
Your product's content, translated and adapted to a new market — delivered in the file formats you actually use.
01
What's included
- Translation and localization by a linguist working into their native language
- Adaptation of tone, examples, and formatting for the target market
- In-context quality check
- String-file handling and in-context linguistic QA on the Engineering tier
We work directly in JSON, PO, XLIFF, and .strings files — send us what your product actually uses.
Who it's for
- Product, marketing, or engineering teams shipping a website, app, or software product into a new market
- Teams who need content that works inside strings, formats, and UI constraints — not just translated words
- Technical buyers who need file-format and engineering fit, not just language
02
How it works for this service
- 01
Send us your content
string files, a document export, or a description of your project.
- 02
We scope it
file formats, word count, and whether you need engineering support.
- 03
Content is localized,
and on the Engineering tier, string files are handled directly and checked in context.
- 04
Delivered ready to drop back into your product.
This is the version specific to Website & App Localization. See the full process, our two-linguist QA model, turnaround table and revision policy on How It Works.
03
Pricing
Content localization
$0.16/word
Your website, app, or product content translated and adapted for a new market — tone, formatting, and cultural fit, not just words.
- Translation and localization by a native-language linguist
- Adaptation of tone, examples, and formatting for the target market
- In-context quality check
Turnaround: Scoped per project
Best for: Teams who can supply content in a plain-text or document format and handle the file integration themselves.
Get my quoteLocalization + Engineering
Recommended$0.16/word + $95/hour
Everything in Content Localization, plus we handle your string files directly — JSON, PO, XLIFF, .strings — so nothing breaks on the way back into your product.
- Everything in Content Localization
- String-file handling in your format
- In-context linguistic QA inside your actual UI where possible
- Independent second-linguist review
Turnaround: Scoped per project
Best for: Product and engineering teams who want the localized strings delivered ready to drop back in.
Get my quoteAdd-ons
- Glossary/termbase creationfrom $120
Keeps product terms, UI labels, and brand language consistent as content grows.
- Second-linguist review (Content localization orders)+$0.03/word
- Expedited handling+50%
What changes your price: word count · content-only vs. + engineering · number of string-file formats involved · turnaround agreed at scoping.
04
Our confidentiality policy
“An NDA on request, access limited to the assigned linguist and one reviewer, and deletion of your files whenever you ask.”
05
Frequently asked questions
What file formats do you work with?
JSON, PO, XLIFF, .strings, and plain text or document files. Send us what you have — if it's a format we haven't listed, ask; we can usually handle it.
Do you handle the engineering side, or just the translation?
Both, depending on the tier. Content Localization delivers translated, localized text; Localization + Engineering also handles your string files directly, so what comes back drops straight into your product without extra work on your end.
How do you keep terminology consistent across a large product?
A glossary or termbase, built for your project, is available as an add-on — it keeps product terms, UI labels, and brand language consistent even as the content grows.
Can you localize content in context, not just as a spreadsheet of strings?
Yes — in-context quality checks are part of the Localization + Engineering tier, so we review strings the way a user will actually see them, not just as isolated lines of text.