Skip to content
File Formats

One platform. 19 localization file formats.

Humlens translates your base JSON and converts it to every format your stack needs — from React i18next JSON to Flutter ARB to Android strings.xml to CAT-tool-ready XLIFF — on every deploy.

Deploy targets JSON YAML XLIFF ARB PO XML TS + 13 more formats 19 Formats 50+ Languages 1 Base (JSON) 1-click Deploy Translate once, deploy to every format XLF Converting ARB Packaged PO Deployed XML Queued

Every format gets the full workflow.

19 file formats, one base

Translations live in Humlens as structured JSON and convert automatically to any of 19 supported formats on deploy — JSON, YAML, XLIFF, ARB, strings.xml, and more.

AI translation with glossary rules

Every format gets the same context-aware AI translation, respecting glossary entries and tone rules.

Human review & approval gates

Reviewers approve, edit, or flag strings in any format before they reach the deploy stage.

Coverage tracking per language

Track translation coverage per language and key, regardless of which output format you deploy to.

Deploy to S3 or download as .zip

Push translated files straight to storage, or download every supported format in a single .zip package.

QA checks for placeholders

Automated checks catch broken placeholders and formatting issues before export, across every format.

One base format, every tech stack covered.

React & Next.js apps via JSON (react-i18next, next-intl)
Vue & Nuxt apps via JSON or YAML
Android apps via strings.xml
iOS & macOS apps via .strings, .stringsdict, .xcstrings
Flutter apps via Application Resource Bundle (.arb)
WordPress, Python & C apps via Gettext PO
Enterprise CAT tool handoff via XLIFF 1.2
Docs & content sites via Markdown, MDX, and HTML

Frequently asked questions.

Which localization file formats does Humlens support?
Humlens supports 19 localization file formats: JSON, YAML, TypeScript, JavaScript, Java Properties, Android XML (strings.xml), iOS Strings (.strings), iOS Stringsdict, iOS XCStrings, Flutter ARB (.arb), Gettext PO (.po), XLIFF (.xlf/.xliff), CSV, XML, HTML, Markdown (.md), MDX, PHP, and Fluent FTL — covering every major technology stack.
Can Humlens convert JSON to other localization formats?
Yes. Humlens uses JSON as its internal base format and converts translated content to any supported format on every deploy. A single project can deploy to JSON (for your web app), ARB (for your Flutter app), and strings.xml (for your Android app) simultaneously.
What localization format should I use for a React app?
React apps typically use JSON locale files with libraries like react-i18next, i18next, next-intl, or react-intl. JSON is Humlens's native format, so React projects integrate with zero conversion — import your JSON files, translate, and export deployment-ready JSON back.
What format does Flutter use for localization?
Flutter uses the ARB (Application Resource Bundle) format — JSON files with the .arb extension, consumed by the flutter_localizations and intl packages. Humlens imports and exports ARB files natively, preserving the @@locale metadata and all message entries.
What is the best format for Android localization?
Android uses strings.xml (Android XML) as its native resource format. Humlens exports translated content as strings.xml files in the correct format for each target locale, ready to place in your Android project's res/values-{locale}/ directories.
Does Humlens support XLIFF for CAT tool integration?
Yes. Humlens imports and exports XLIFF 1.2 files, making it compatible with professional CAT tools like SDL Trados, memoQ, Phrase (Memsource), and Smartling. You can run the AI translation in Humlens and export XLIFF for agency review, or import agency-translated XLIFF back into Humlens.

Explore more of the platform.

See all features

Translate once. Deploy to every format.

Free plan available. No credit card required.