Imports & exports
StringJet meets teams where their files already are. Import translations from ZIPs, single files, or folder selections; export Android XML, iOS strings or xcstrings, Flutter ARB, or web JSON ZIPs with per-locale checkboxes and optional platform filters — ideal for CI pipelines and repo workflows alongside OTA bundles.
Technical detail tables live in I18N_FORMAT_SUPPORT and Export formats (developer docs).
Import: stage, review, run
Drag and drop a ZIP, pick .arb, .json, .xml, .strings, or choose a folder (for example Android res or iOS *.lproj trees). The UI stages files so you can confirm size and names before import. Options include overwrite behavior and target language hints when folder structure alone is ambiguous — important when you select an .lproj folder directly.
Export kinds (ZIP)
The Download tab mirrors server-side generators:
- Android XML (ZIP) — resource XML bundles for Android projects.
- iOS legacy .strings (ZIP) — classic strings tables.
- iOS xcstrings (ZIP) — Xcode string catalogs.
- Flutter ARB (ZIP) — ARB files for Flutter localization.
- Web JSON (ZIP) — JSON payloads for web stacks.
Platform & language filters
Narrow exports with an optional platform filter (or export for all platforms your project supports). Toggle languages individually so partial exports match what your branch needs. Preferences can persist for repeat downloads.
How this fits OTA
Imports and exports sync your repo-shaped assets with the same canonical keys you edit in the editor and ship via OTA to devices. Many teams use exports for Git and OTA for hotfixes — both reference one project.