> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prismy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# ✅ Supported Frameworks and Files

> Everything you need to know about compatible frameworks and file formats.

# 🧱 Frameworks & i18n Libraries

<Note>
  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.
</Note>

<AccordionGroup>
  <Accordion title="JavaScript & TypeScript">
    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.
  </Accordion>

  <Accordion title="PHP">
    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.
  </Accordion>

  <Accordion title="Python">
    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.
  </Accordion>

  <Accordion title="Other Languages & Platforms">
    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.
  </Accordion>
</AccordionGroup>

***

# 📁 Supported File Formats

<Note>
  If your translations are stored in a format not listed here, or if you have
  unique format requirements, [let us know](mailto:cyril@prismy.io)—we’re happy
  to explore custom support.
</Note>

<AccordionGroup>
  {" "}

  <Accordion title=".json">
    Common format for modern frontend frameworks. We support both flat and nested
    JSON files.
  </Accordion>

  {" "}

  <Accordion title=".tsx / .ts / .js">
    Prismy can extract and manage inline strings and translation keys from your
    source code.
  </Accordion>

  {" "}

  <Accordion title=".po / .mo">
    Standard `gettext` formats, used in many Python and PHP projects. We support
    both editable `.po` and compiled `.mo` versions.
  </Accordion>

  {" "}

  <Accordion title=".arb">
    Commonly used in **Flutter** apps. We support `.arb` files for Dart-based
    workflows.
  </Accordion>

  <Accordion title=".xml">
    Structured formats used in **Android**, localization tools, and legacy systems. We parse `<string>` tags and key-value entries.
  </Accordion>

  {" "}

  <Accordion title=".yaml / .yml">
    Frequently used in **Rails**, static site generators, and CI/CD
    configurations. Supports deeply nested structures and aliases.
  </Accordion>

  {" "}

  <Accordion title=".resx">
    Resource files for **.NET** and **C#** projects. Fully compatible with Visual
    Studio-style workflows.
  </Accordion>

  {" "}

  <Accordion title=".ini">
    Used in older systems or gaming engines for flat key-value translations.
  </Accordion>

  {" "}

  <Accordion title=".strings">
    Used for localizing **iOS** and **macOS** apps, supported out of the box.
  </Accordion>

  {" "}

  <Accordion title=".properties">
    Java-centric localization files with key=value pairs, common in enterprise and
    Android setups.
  </Accordion>

  {" "}

  <Accordion title=".toml">
    Occasionally used in **Go** projects or DevOps environments. Supported on
    request.
  </Accordion>

  {" "}

  <Accordion title=".csv">
    Useful for spreadsheets, LSP exports, or manual reviews. Handy for
    non-technical contributors.
  </Accordion>

  {" "}

  <Accordion title=".md">
    Markdown file translation is supported for documentation, blogs, or knowledge
    bases.
  </Accordion>
</AccordionGroup>