Website & App Localisation
Content that reads native in your target market — not a word-for-word rendering of the source.
from 36.00€ / 250-word block · IVA incl.
Typical turnaround 4–7 business days, confirmed at order
Translated, or localised — the difference shows
Applies to: marketing landing pages, app onboarding flows, checkout copy, help-centre articles, app store listings.
- Literal: "Solicitar una demostración del producto." → Native: "Reserva tu demo."
- Literal: "Nosotros proporcionamos soporte al cliente las 24 horas." → Native: "Soporte 24 horas, siempre disponible."
- Literal: "Haga clic aquí para continuar el proceso de compra." → Native: "Sigue con tu compra."
Included
- Native-market phrasing, not literal translation — content that reads like it was written for that market
- String and character-limit awareness (buttons, labels, notifications)
- SEO-localised tier: keyword-adapted headings and metadata for the target market
- Integration & QA package: string extraction support, RTL/format edge-case checks, in-context layout QA
Not included
- Development or engineering work to implement strings back into your codebase — we hand back translated strings in the format you sent
How this service runs
We work from the strings/content you send (JSON, XLIFF, CSV, PO, or plain copy).
Content is localised to read native, not translated literally — restructured where the source phrasing wouldn't land.
(SEO-localised tier) Headings and metadata adapted for target-market search terms.
(Integration & QA package) Strings tested in context for length, format and layout.
Delivered in the same file format you sent, ready to implement.
Choose your tier
Delivery method and turnaround are confirmed at checkout.
Formats, delivery & turnaround
Formats
JSON, XLIFF, CSV, PO, plain text/Word for marketing copy
Delivery
Same format as received
Turnaround
4–7 business days typical, depending on string volume and whether Integration & QA is included
1 / 3
Frequently asked questions
Is this the same as regular translation?
No — regular translation renders the source faithfully; localisation adapts phrasing, tone and structure so the content performs for a specific market, not just reads correctly.
What formats do you accept?
JSON, XLIFF, CSV and PO for app/software strings; plain text or Word for marketing and help-centre content.
Do you handle character-limit-constrained strings, like app buttons?
Yes — this is exactly what the Integration & QA package is built to check, alongside RTL and layout edge cases.
What does the Integration & QA package actually check?
String length against your UI constraints, format/placeholder integrity (e.g. {username} variables), and a layout pass once strings are implemented, flagging anything that breaks or overflows.
Can you localise into multiple target markets from one source?
Yes — scope each target language as a separate line; we'll confirm one delivery date across the set if you need them together.