Product and UI text, kept in context
Website & software localization
A localized product that feels native to a Norwegian or English user, without breaking your layout.
What it is / who it's for
Website and software localization translates the strings your product actually ships — UI labels, buttons, error messages, help text, product pages — in the file formats your team already uses, with the space constraints of a real interface kept in mind. Short strings without context are the single biggest way this goes wrong; we ask for context (screenshots, a staging link, a string key) wherever we can get it.
Who for
- · Product and dev teams shipping a UI into Norwegian or English
- · Marketing teams localizing a website
- · E-commerce businesses expanding across the language boundary
Document types
- · UI strings and interface copy
- · Website pages and product listings
- · Help centre and support content
- · App store listings
- · Error messages and notifications
File formats we work with: JSON, XLIFF, PO, CSV and plain spreadsheet exports — tell us yours when you order.
What's included
Included
- · Translation of your strings in their native file format
- · Independent revision for tone and consistency
- · Context requested and used wherever supplied (screenshots, staging link, string keys)
- · Delivery in the same file format, ready to re-import
Not included
- · Development work to re-import or deploy the file
- · Ongoing string updates beyond the batch ordered (see the escape hatch for recurring work)
kr 1 150
kr 920 ex. MVA
Ongoing localization, or a live product with strings shipping every sprint? Get a quote →
Context used wherever you supply it · independently revised for tone and fit · 14-day free correction window.
Process
- 01 Order & send your string file
- 02 Translator with product/UI experience assigned
- 03 Translated in context, then independently revised for tone and fit
- 04 Delivered in your file format, ready to re-import
Why this needs a specialist
- UI strings arrive stripped of context by nature — a translator working blind guesses at meaning, and guesses are how software ships with a wrong translation in the settings menu.
- We ask for a screenshot, a staging link or a string key wherever you can give us one, and translate accordingly.
- This is the one service on the site built to be ongoing — ordering a first batch at the published price doesn't lock you into a one-off; recurring work moves to a quote so we can price it as a standing relationship, not repeat one-off orders.
Turnaround & pricing detail
| Standard | Express | |
|---|---|---|
| ≤250 words | 24 hours | 8 hours (+50%) |
| ≤500 words | 48 hours | 24 hours (+50%) |
| ≤1 000 words | 3 working days | 48 hours (+50%) |
| ≤2 000 words | 5 working days | 3 working days (+50%) |
Localization is timed for context-gathering as much as translation — a batch with good context (screenshots, a staging link) moves faster than strings delivered blind.
Frequently asked questions
Can you actually work with our file formats?
Yes — JSON, XLIFF, PO, CSV and plain spreadsheet exports are all handled directly, delivered back in the same format ready to re-import. Tell us your format when you order; if it's something else, ask first.
How do you keep strings in context without seeing the product?
We ask for whatever context you can share — a screenshot, a staging link, a string key with surrounding strings. The more context we get, the fewer follow-up questions during the independent revision pass.
We ship new strings every sprint — is this only for a one-off batch?
The buy block prices a first batch. For ongoing work, use the quote route so we can set up a standing arrangement with consistent pricing and terminology, rather than pricing every sprint's strings as a fresh order.
Will the translated file just drop back into our codebase?
We deliver it in the same file format you sent, structured the same way, ready to re-import. We don't handle the deployment itself.
Strings ready to send?