Skip to main content

​
🧱 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.
Prismy works seamlessly with frameworks like React, Next.js, Vue, Svelte, Angular, Remix, Astro, and SolidJS.Commonly used i18n libraries supported include:
  • i18next
  • react-i18next
  • next-intl
  • react-intl
  • LinguiJS
  • Polyglot.js
  • vue-i18n
  • vuex-i18n
  • Svelte-i18n
  • i18n-js (React Native, Expo)
We also support projects using Electron and React Native.You can organize your .json, .ts, or .tsx translation files however you like—Prismy adapts to your structure.
Prismy supports PHP frameworks like Laravel, Symfony, and CakePHP, including tools such as:
  • Laravel Lang
  • Symfony Translation
  • .php, .json, .po and .mo catalogs
Ideal for both traditional MVC apps and headless PHP backends.
Prismy is compatible with Python-based apps including Django, Flask, and FastAPI.Supported libraries and tools:
  • gettext (.po / .mo)
  • Flask-Babel
  • django-rosetta
  • Babel for string extraction
  • Polib for .po manipulation
Both traditional and async Python projects are welcome.
Prismy is flexible enough to work with many other ecosystems:
  • Java/Kotlin – using .properties or Android XML
  • Swift / Objective-C – using .strings files
  • Ruby – YAML-based translations and i18n-tasks
  • Go – go-i18n, TOML/YAML files
  • .NET / C# – .resx resource files
Have a custom setup? We’re happy to support it.

​
📁 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.
Common format for modern frontend frameworks. We support both flat and nested JSON files.
Prismy can extract and manage inline strings and translation keys from your source code.
Standard gettext formats, used in many Python and PHP projects. We support both editable .po and compiled .mo versions.
Commonly used in Flutter apps. We support .arb files for Dart-based workflows.
Structured formats used in Android, localization tools, and legacy systems. We parse <string> tags and key-value entries.
Frequently used in Rails, static site generators, and CI/CD configurations. Supports deeply nested structures and aliases.
Resource files for .NET and C# projects. Fully compatible with Visual Studio-style workflows.
Used in older systems or gaming engines for flat key-value translations.
Used for localizing iOS and macOS apps, supported out of the box.
Java-centric localization files with key=value pairs, common in enterprise and Android setups.
Occasionally used in Go projects or DevOps environments. Supported on request.
Useful for spreadsheets, LSP exports, or manual reviews. Handy for non-technical contributors.
Markdown file translation is supported for documentation, blogs, or knowledge bases.