Skip to content
Text Localization

Localize JSON, YAML, PO, XLIFF, and 15+ formats — with AI.

Humlens translates your software strings with context-aware AI, routes them through human review, enforces glossary rules, and deploys locale files directly to your CDN or S3 bucket.

en.json { "nav.home": ES "nav.pricing": FR "cta.start": JA "footer.rights": DE } Coverage 92% ES Translated FR In review JA Approved DE Queued

Everything in one localization platform.

Upload or sync any format

Push locale files via the UI, API, or CI pipeline. Humlens detects your format automatically — JSON, YAML, PO, XLIFF, ARB, and more.

AI translation with glossary rules

Context-aware AI generates translations for every key, respecting glossary entries and tone rules across the whole project.

Human review & approval gates

Reviewers approve, edit, or flag strings inline. Approval gates prevent unreviewed content from shipping.

Coverage dashboard

Track translation coverage per language and per key, so you always know what is missing before a release.

Deploy to S3 / CDN

Export locale files in your target format, or auto-push to S3 / CDN so your app fetches the latest files at runtime.

QA checks & version history

Automated checks catch broken placeholders and formatting issues, backed by full version history and an audit trail.

Built for every software localization workflow.

AI translation with glossary & tone rules applied automatically
Coverage dashboard per language and translation key
Human review stages with approval gates before deploy
Inline key comments for translator context
Export to JSON, YAML, PO, XLIFF, ARB, and more
One-click deploy to S3 or your CDN
Version history and a full audit trail
Bulk import from Crowdin, Lokalise, or Phrase

Frequently asked questions.

What is text localization?
Text localization (also called software localization or i18n) is the process of adapting UI strings, documentation, and marketing copy for different languages and markets. It goes beyond word-for-word translation to handle pluralization, date formats, number formats, and cultural nuance so the product feels native to each audience.
What is the difference between i18n and l10n?
i18n (internationalization) is the process of designing your software so it can support multiple languages — for example, externalizing strings into locale files. l10n (localization) is the process of actually translating and adapting that content for a specific market. Humlens handles the l10n side: you bring your i18n-ready files, Humlens translates and manages them.
What file formats does Humlens support for text localization?
Humlens supports JSON, YAML, TypeScript, Java Properties, Gettext PO, XLIFF, Android XML (strings.xml), iOS Strings (.strings), iOS Stringsdict, iOS XCStrings, Flutter ARB, CSV, HTML, Markdown, MDX, JavaScript, Fluent FTL, and PHP — covering virtually every technology stack.
How do I localize a React app with Humlens?
Most React i18n setups (react-i18next, i18next, next-intl, react-intl) use JSON locale files. Export your JSON files, import them into Humlens, translate with AI, approve in review, and export deployment-ready JSON files back to your project — or push them directly to your CDN.
What is a translation management system (TMS)?
A translation management system (TMS) is a platform that organizes, automates, and manages the end-to-end process of translating software content. It typically includes import/export of locale files, AI or human translation, review workflows, glossaries, QA checks, and deployment. Humlens is a TMS with native support for 19 localization file formats.
Does Humlens support glossaries and brand terms?
Yes. You can define a glossary of brand terms, product names, competitor names to avoid, and style rules. The AI respects glossary entries during translation and the QA step flags any violation before deployment.

Explore more of the platform.

See all features

Start localizing your strings today.

Free plan available. No credit card required.