Websites & apps

Website & software localization
delivered ready to publish

The hard part of a multilingual website is rarely the translating. It is the files, the formats, the strings that break, and keeping five languages in step every time something changes. We take all of that off your desk.

  • Websites, apps and web platforms
  • Strings, CMS exports and store listings
  • Ready to publish, not ready to reformat
  • Updates kept in step across languages
  • One named contact for the whole thing
Get my quote
Same-day answer

Get your quote

Send us a URL, an export or just a description, and we will reply with a fixed price.

Your documents

    What we localize

    • Websites

      From a five-page company site to a full CMS export. Content, navigation, metadata and the strings hiding in templates.

    • Software & apps

      Interface strings in JSON, .po, .strings or XLIFF, translated with their context and length limits respected — so nothing overflows a button.

    • Stores & marketplaces

      App store listings, product descriptions and category pages, written to sell in the target language rather than merely exist in it.

    • The words around the product

      Onboarding emails, help articles, error messages — the copy users actually meet, kept in the same voice as the interface.

    How a localization project runs

    1. 1

      Send us what you have

      A URL, a repository export, a pile of files, or just a description. We work out the real word count and the format plan from that.

    2. 2

      Receive your quote

      A fixed price and a delivery date, with repeated strings and previously translated content already discounted.

    3. 3

      We translate in context

      Interface strings are translated as interface, marketing pages as marketing. Length limits, placeholders and variables survive intact.

    4. 4

      You publish, we stay in step

      Files come back in the format they left in. When you add a feature or a page, send the new strings — only the new content is translated and charged.

    The maintenance problem nobody quotes for

    Launching a website in three languages is a project. Keeping it in three languages is the actual job — every new page, product and feature has to make the same journey again, and this is where most multilingual sites quietly rot: the English moves on and the other languages fall behind, one small update at a time.

    This is what our setup is built for. Your translations live in a translation memory, your product names and phrasing in a termbase, so each update costs only what actually changed and comes out consistent with everything already published. Placeholders, variables and formatting are checked before delivery, because a broken {variable} in production is our problem to prevent, not yours to find.

    And you deal with one named person throughout — not a ticket queue, and not a different project manager per language.

    Happy to be of service,

    Founder

    Localization languages

    Below are the languages we are asked for most often for websites and software. For any other language, just contact our team.

    • German
    • English
    • Spanish
    • French
    • Italian
    • Norwegian
    • Arabic
    • Chinese
    • Japanese
    • Romanian
    • Portuguese
    • Polish
    • Swedish
    • Finnish
    • Thai
    • Russian
    • Greek
    • Ukrainian
    • …and many others
    EnglishPortugueseSwedishGermanPolishGreekSpanishDutchTurkishFrenchRomanianJapaneseArabicUkrainianMandarinItalianRussianNorwegian

    Frequently asked questions

    Tap any question to see the answer!
    Which formats can you handle?
    Almost certainly yours: JSON, .po, .strings, XLIFF, XML, CSV, InDesign, subtitle formats and most CMS exports. Send us a sample file and we will confirm before you commit.
    Will placeholders and variables survive?
    Yes. Placeholders, variables and markup are protected during translation and checked before delivery — a translation that breaks the build is not a translation, it is a bug.
    Can you work directly in our CMS?
    Often, yes — and where an export-import round trip is safer, we will say so and handle the files. Tell us what you run and we will propose the least painful workflow.
    How do updates work after launch?
    Send the new or changed content, in whatever form it exists. Your translation memory means only the difference is translated and charged, and the new material comes out consistent with everything already live.
    Do you localize or just translate?
    Localize — dates, currencies, examples, idioms and tone are adapted to the market, not just the words. Where something in your product genuinely will not land in a market, we tell you rather than translating around it silently.
    What does it cost?
    By volume, format and language pair, with repetition discounted — interfaces repeat a lot, so this matters. Send us the files or the URL and you will have a fixed price, with no obligation.