Technical doc & features
✅ Supported Frameworks and Files
Everything you need to know about compatible frameworks and file formats.
🧱 Frameworks & i18n Libraries
Prismy is stack-agnostic—it works with any frontend or backend framework,
as long as your translation files live in your codebase. No vendor lock-in, no
black boxes.
JavaScript & TypeScript
JavaScript & TypeScript
Prismy works seamlessly with frameworks like React, Next.js, Vue, Svelte, Angular, Remix, Astro, and SolidJS.Commonly used i18n libraries supported include:
i18nextreact-i18nextnext-intlreact-intlLinguiJSPolyglot.jsvue-i18nvuex-i18nSvelte-i18ni18n-js(React Native, Expo)
.json, .ts, or .tsx translation files however you like—Prismy adapts to your structure.PHP
PHP
Prismy supports PHP frameworks like Laravel, Symfony, and CakePHP, including tools such as:
Laravel LangSymfony Translation.php,.json,.poand.mocatalogs
Python
Python
Prismy is compatible with Python-based apps including Django, Flask, and FastAPI.Supported libraries and tools:
gettext(.po/.mo)Flask-Babeldjango-rosettaBabelfor string extractionPolibfor.pomanipulation
Other Languages & Platforms
Other Languages & Platforms
Prismy is flexible enough to work with many other ecosystems:
- Java/Kotlin – using
.propertiesor Android XML - Swift / Objective-C – using
.stringsfiles - Ruby – YAML-based translations and
i18n-tasks - Go –
go-i18n, TOML/YAML files - .NET / C# –
.resxresource files
📁 Supported File Formats
If your translations are stored in a format not listed here, or if you have
unique format requirements, let us know—we’re happy
to explore custom support.
.json
.json
Common format for modern frontend frameworks. We support both flat and nested
JSON files.
.tsx / .ts / .js
.tsx / .ts / .js
Prismy can extract and manage inline strings and translation keys from your
source code.
.po / .mo
.po / .mo
Standard
gettext formats, used in many Python and PHP projects. We support
both editable .po and compiled .mo versions..arb
.arb
Commonly used in Flutter apps. We support
.arb files for Dart-based
workflows..xml
.xml
Structured formats used in Android, localization tools, and legacy systems. We parse
<string> tags and key-value entries..yaml / .yml
.yaml / .yml
Frequently used in Rails, static site generators, and CI/CD
configurations. Supports deeply nested structures and aliases.
.resx
.resx
Resource files for .NET and C# projects. Fully compatible with Visual
Studio-style workflows.
.ini
.ini
Used in older systems or gaming engines for flat key-value translations.
.strings
.strings
Used for localizing iOS and macOS apps, supported out of the box.
.properties
.properties
Java-centric localization files with key=value pairs, common in enterprise and
Android setups.
.toml
.toml
Occasionally used in Go projects or DevOps environments. Supported on
request.
.csv
.csv
Useful for spreadsheets, LSP exports, or manual reviews. Handy for
non-technical contributors.
.md
.md
Markdown file translation is supported for documentation, blogs, or knowledge
bases.