Source
Integrations, file formats & developer tools — found from sitemap — Locize
Checked for Locize on 1 Nov 2026
- Page
- https://www.locize.com/docs/integration/file-formats
- Checked
- 1 Nov 2026, 10:05 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:611650cdbe9707e4b3913b1c8ead70e83d1436ad39b54b7950d7134c1e6c2db5
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
File formats supported Report an error
“Locize supports a variety of translation file formats for import and export, making it easy to integrate with your existing localization workflow.”
-
Format structure preservation Report an error
“Locize generally only handles translation content (keys and values) and does not preserve the original file structure.”
-
No format conversion Report an error
“The originally used i18n format will always be respected; there is no conversion during import/export.”
-
Export language specific Report an error
“Language/namespace specific format: Select the appropriate language and namespace in the filter to export a file for a dedicated language.”
-
Export all zip Report an error
“"All" format or zip: Deselect language and namespace in the filter to export a "all" format or zip file for the whole project.”
-
Format json nested Report an error
“JSON nested Will import/export in JSON format, nesting keys separated by .:”
-
Format json flatten Report an error
“JSON flatten Will import/export in JSON format, flat (ignoring . separation):”
-
Format CSV xlsx Report an error
“CSV and XLSX Exports reference and target language in one file. Supported for imports and useful for sending translations to freelancers.”
-
Format yaml Report an error
“YAML Alternative format to JSON.”
-
Format xliff Report an error
“XLIFF 1.2 Standard translation exchange format. Xcode's localization export (.xcloc bundles) uses XLIFF 1.2.”
-
Xliff cli formats Report an error
“With the CLI, use the formats xliff21 / xliff22 (or xlf21 / xlf22).”
-
Format android Report an error
“Android resource string Format used on Android.”
-
Format strings Report an error
“Strings resources Format used for example for OS X and iOS.”
-
Format gettext po Report an error
“Gettext po files Gettext standard format.”
-
Gettext po i18next mode Report an error
“gettext (i18next) (CLI --format po_i18next or gettext_i18next, the editor's "gettext (i18next)"): the msgctxt becomes i18next's context suffix”
-
Gettext fuzzy Report an error
“#, fuzzy. Fuzzy entries arrive marked as needing review (target languages); values marked as needing review go out as #, fuzzy”
-
Format tmx Report an error
“TMX Used mostly as translation memory file.”
-
Format resx Report an error
“resx Files (.net) Localization files used in .net framework”
-
Format fluent Report an error
“Fluent Mozilla's translation format”
-
Format laravel Report an error
“Laravel PHP Laravel's translation format”
-
Format properties Report an error
“.properties (Java) .properties files”
-
Format xcstrings Report an error
“.xcstrings Apple string catalog files”
-
All format bulk metadata Report an error
“The "all" format (exported with no language or namespace selected in the filter) also contains the columns namespace, tags, context and maxCharacters”
-
CSV ignore marker Report an error
“You might see a “###ignore###” text in your exported "all" format file. This marks keys missing in the reference language or plural forms not present for a specific language.”
-
Xliff import constraint Report an error
“On import, ensure you have only one <file> tag in the XLIFF file, and the original attribute matches your namespace name.”
-
Custom formats via email Report an error
“If you need a format that isn’t listed here, send us an email; we’re always working to extend our supported formats!”
-
CSV import reuse Report an error
“For optimal import, reuse previously exported files including added translations.”
-
Company name Report an error
“© 2026 inweso Ltd liab. Co. All Rights Reserved.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The App Developer Integrations, file formats & developer tools
- The App Developer Data export, portability & self-hosting
- The Data Protection Officer Integrations, file formats & developer tools
- The Data Protection Officer Data export, portability & self-hosting
- The In-House Document Translator Machine translation & AI quality
- The In-House Document Translator Integrations, file formats & developer tools
- The In-House Document Translator Data export, portability & self-hosting
- The E-Commerce Marketer Integrations, file formats & developer tools
- The E-Commerce Marketer Data export, portability & self-hosting
- The Localization Manager Integrations, file formats & developer tools
- The Localization Manager Data export, portability & self-hosting
- The Skeptic Integrations, file formats & developer tools
- The Skeptic Data export, portability & self-hosting