Website & Software Localization your team can ship without rework
Localized UI and CMS content, delivered in a format your team can ship without rebuilding it first.
A localization project usually fails somewhere other than the language: a broken placeholder, a string that doesn't fit the button, a file format your team has to rebuild by hand before it's usable. That handoff costs more time than the translation itself.
We localize websites, web apps, and software UI strings between German and English (and other pairs on request), from €0.18/word, working directly in the file formats your team already uses — JSON, XLIFF, .po, CSV string tables, or a CMS export — and returning them in the same format, with placeholders and variables protected throughout.
This page treats file formats and deliverables as the first-class topic, because for this buyer, the handoff is the risk.
from €0.18/word
Process for this service
01
Format check
We confirm the file format and how placeholders/variables are marked, before translation starts.
02
Assignment
A linguist experienced in UI/software localization is assigned.
03
Translation
Strings are translated in context where possible; length constraints are flagged, not silently overrun.
04
Independent revision
A second linguist checks strings for consistency and placeholder integrity.
05
Delivery
Returned in your original file format, ready to merge or import directly.
What's included / scope
We accept
JSON · XLIFF · .po/.pot · CSV/TSV string tables · CMS exports (WordPress, Shopify, custom) · Figma text layers (via export) · plain-text string lists.
We return
The same file format, structure and encoding you sent — placeholders, variables and HTML tags protected and untouched, string length flagged where the translation runs noticeably longer than the source.
Industries served
Turnaround & delivery
3–5 business days standard, scaling with string count
Digital delivery in your original file format; no hard-copy delivery for this service
Pricing for this service
From €0.18/word, Professional tier standard. DTP/format-rebuild add-on available at €45/hour if a non-standard format needs manual reconstruction.
Price estimator
MT with full human post-editing. (€0.09/word)
Human specialist translation, self-revised. (€0.16/word)
Specialist translation, independently revised, sworn certification where required. (€0.22/word)
Your job is below our minimum order — the total shown is the minimum for this language pair.
Estimate, not a binding quote — final price is confirmed against your actual file.
See full estimate →When you need this
A German storefront launch needs every product page, checkout string and error message localized without breaking a single {{variable}} placeholder.
A SaaS product's UI strings need translating from a JSON export and returned in the same structure, ready to merge back into the codebase.
A marketing site's CMS content needs localizing in place, string by string, without a developer having to touch the export file first.
Placeholders survive translation — checked, not assumed
Every string is checked at the independent-revision stage specifically for placeholder and variable integrity, not just linguistic accuracy — the most common way a localization project breaks isn't a wrong word, it's a broken {{token}}.
Related services
FAQ
What file formats do you support?
JSON, XLIFF, .po/.pot, CSV/TSV string tables, common CMS exports, and plain-text string lists.
How do you protect placeholders and variables?
They're marked and locked before translation starts, and checked again at the independent-revision stage.
What if the German text is longer than the English source and breaks our UI?
We flag strings that run noticeably longer than the source so your team can review them before launch.
Can you localize directly in our CMS?
We work from CMS exports and return the same structure for import; direct in-CMS access can be arranged for larger, ongoing projects.