Questions we get before
almost every project.

We accept JSON, XLIFF (1.2 and 2.0), PO/POT, Android strings.xml, iOS .strings, CSV, Excel, Word, HTML, Markdown, SRT, VTT, SCC, and most CMS content exports. Contact us before ordering if your format is not listed.

Yes. Placeholder handling is a core part of our software localization QA process. We check that variables ({name}, %s, {{count}}, etc.) are present in translated strings exactly as in the source. Broken placeholders cause software errors and we verify against them as standard.

Yes. We return files in the same format you provide. You send us a JSON localization file, you get a translated JSON file in the correct structure. You send an XLIFF, you receive a translated XLIFF. No format conversion required from your end.

Word count is the total words in the source document(s). For multi-language projects, the word count applies per language pair. A 1,000-word document translated into French, German, and Spanish counts as 3,000 translated words total.

Translation memory archives previously translated content at the string level. When a string in a future project is identical or nearly identical to a previously translated string, it is reused rather than retranslated. Over time this reduces cost and delivery time for clients with repeated or overlapping content -- common in software updates.

Starter: 5 business days. Growth: 4 business days. Scale: 3-day priority. Express 48-hour delivery is available as a paid add-on through the package builder.

Our app store localization service translates and keyword-adapts titles, subtitles, descriptions, and keyword fields for App Store and Google Play. We do not perform independent market research from scratch, but we do work from your existing keyword sets and adapt them for natural-language search in the target market.

Payment is processed through Stripe Checkout at checkout.stripe.com. We accept all major credit and debit cards. All services are delivered digitally after payment and source file submission.