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

# Exporting and export profiles

> Download translations as files for your project, with fixed profiles or a format of your own.

Everyone in the team can export. An export includes every translation that is not empty and has no placeholder error. For the same translations, an export always produces exactly the same files, so git diffs stay small.

## How to export

<Steps>
  <Step title="Open the export">
    On the project page or in the editor, click **Export** (*Exporteren*). If you have selected keys in the editor, Tolk exports only those.
  </Step>

  <Step title="Choose a profile or format">
    Choose an export profile, or **Other format…** (*Ander formaat…*) for a layout of your own.
  </Step>

  <Step title="Languages and missing translations">
    Choose the languages and what Tolk does with a missing translation: **Fall back to the fallback language** (*Terugvallen op de fallback-taal*), **Leave empty** (*Leeg laten*) or **Leave out** (*Weglaten*).
  </Step>

  <Step title="Download">
    Click **Download** (*Downloaden*). Multiple files come in a zip with your project's folder structure. A large export is built in the background; you see its progress.
  </Step>
</Steps>

## Default profiles

Every project gets profiles that match its type. They export all languages and fall back to the fallback language.

<Tabs>
  <Tab title="Laravel">
    | Profile | Format | Path |
    | - | - | - |
    | Laravel JSON | Laravel JSON | `lang/{locale}.json` |
    | PHP files | Laravel PHP | `lang/{locale}/{group}.php` |
    | JavaScript | JS script with `window.Tolk` | `public/lang/{locale}.js` |
  </Tab>

  <Tab title="WordPress">
    | Profile | Format | Path |
    | - | - | - |
    | PO | PO (gettext) | `languages/{wp_locale}.po` |
    | MO | MO (gettext) | `languages/{wp_locale}.mo` |
    | PHP (WordPress 6.5+) | WordPress PHP | `languages/{wp_locale}.l10n.php` |
    | POT | POT (template) | `languages/{domain}.pot` |

    For a plugin, the file name starts with the text domain, for example `languages/everyday-i18n-de_DE.po`.
  </Tab>

  <Tab title="Other">
    | Profile | Format | Path |
    | - | - | - |
    | JSON | JSON for JS, nested | `{locale}.json` |
    | XLIFF 1.2 | XLIFF 1.2 | `{locale}.xliff` |
    | Excel | XLSX | `translations-{locale}.xlsx` |
  </Tab>
</Tabs>

## A format and profiles of your own

With **Other format…** you choose:

* the **file format**: Laravel PHP or JSON, JSON for JS, JS module, PO, POT, MO, WordPress PHP, WordPress JS JSON (Jed), CSV, XLSX, XLIFF 1.2 or 2.0;
* the **path**, with the tokens `{locale}`, `{locale_posix}`, `{wp_locale}`, `{group}` and `{domain}`;
* the **shape** (flat or nested), the notation for **plurals** (with a pipe character or with a suffix `_one`, `_other`), and whether **placeholders** are kept or converted, for example `:name` to `{name}` for vue-i18n;
* extra options per format, such as one sheet per namespace or all languages in one file.

With **Save as profile** (*Bewaren als profiel*) you save the settings for everyone in the project. A custom profile is also available in the API and the Laravel package. A project has at most 20 custom profiles. You cannot delete default profiles.

<Tip>
  You can also fetch an export profile through the API, with an ETag so nothing is downloaded again when nothing has changed. See [Imports and exports through the API](/developers/imports-and-exports).
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.