Website & software localization — lokaliseerimine
Strings, tone, and interface constraints handled with UI awareness, not run through as ordinary prose.
from €0.14/per word
What's included
- — Translation and localization of UI strings, marketing copy, and in-product text
- — Tone and market-nuance adaptation, not literal translation
- — In-context review inside your actual interface where possible
- — Independent second read checking both language and fit
File formats handled
- — JSON
- — PO / POT
- — XLIFF
- — CSV
- — UI-string exports
- — Plain text / Markdown
Who it's for
Founder / product lead
Launching a product or website in Estonian for the first time.
→ Copy that reads as native, not machine-adjacent.
Product / localization manager
Managing an ongoing pipeline of strings as the product ships new features.
→ A consistent voice and terminology across every release, not a one-off pass.
Marketing lead
A campaign or landing page needs to land in Estonian without losing its tone.
→ Copy that keeps the brand’s voice, adapted, not diluted.
Process
From your file format back into your build, without losing context.
- 01
Extraction
strings are pulled from your file format (JSON, PO, XLIFF, CSV, or a raw export) with context notes preserved.
- 02
In-context translation
each string is translated with an eye on where it appears and how much room it has, not in isolation.
- 03
In-UI QA
wherever possible, we review strings inside the actual interface, checking that nothing overflows, truncates, or reads oddly against its neighbours.
- 04
Reintegration
translated strings are delivered back in your original file format, ready to drop into the build.
Pricing & packages
What moves the price
- — Word/string count
- — File-format complexity
- — Language pair
- — Turnaround
Microsite
Up to 2,000 words · 5–7 business days
€295.00
- — Extraction & reintegration
- — In-context translation
- — In-UI QA
- — Independent second read
Turnaround
Language pair
€295.00
Full site
Up to 8,000 words · 10–15 business days
€1,120.00
- — Extraction & reintegration
- — In-context translation
- — In-UI QA
- — Independent second read
Turnaround
Language pair
€1,120.00
Delivery: your original file format, plus a plain-text QA note on anything flagged. Returns: Refund & Cancellation Policy. Questions? support@amigotranslate.com — we reply within one business day.
Why Amigo for Website & software localization
File-format literacy.
We work directly in JSON, PO, XLIFF, CSV, and UI-string exports, so nothing gets lost translating out of and back into your build pipeline.
UI-aware, not just word-aware.
String length, tone, and where text sits in your interface are treated as part of the translation brief, not an afterthought.
Turnaround & delivery
- Standard
- 5–7 business days (microsite) · 10–15 business days (full site)
- Express / Priority
- Available for microsite-sized projects; larger projects scheduled individually
- Delivery
- Same file format as received, plus a plain-text QA note on any flagged strings
- Correction window
- 7 days, free, for genuine errors
Frequently asked questions
Will this just be machine-adjacent translation that makes our product feel foreign?
No — every string is translated with its interface context in mind, and reviewed inside the actual UI wherever possible, specifically to avoid the flat, translated-not-native feel.
What file formats do you work with?
JSON, PO/POT, XLIFF, CSV, and most UI-string export formats. Send us a sample file and we’ll confirm compatibility before you order.
Can you handle character-limited UI strings?
Yes — string length constraints are part of the brief; we flag any string where the Estonian or English translation genuinely can’t fit and suggest an alternative.
Do you localize ongoing releases, or just one-off projects?
Both — a one-off microsite or full-site project, or an ongoing pipeline as you ship new strings. Recurring work is scoped individually; ask us.
Do you review strings inside our actual product?
Wherever you can give us access — a staging environment, a design file, or screenshots — we check strings in context before delivery.