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

# Export Formats

> Choose the right output format for your workflow.

LinguLink supports five export formats:

* **JSON** for application runtime consumption
* **CSV** for spreadsheet-first workflows
* **XLIFF** for translation tooling and localization vendors
* **XML** for legacy or platform-specific pipelines
* **YAML** for config-driven i18n setups

Pass the format via the `format` query parameter on the export endpoint
(`json`, `csv`, `xliff`, `xml`, `yaml`). `json` is the default.

Responses use the matching content type — `application/json`, `text/csv`,
`application/xml` (XLIFF and XML), or `text/yaml` — so scripts can pipe the
body straight to a file with the right extension.

## Choosing a Format

* Use **JSON** for i18n runtime libraries and deploy pipelines
* Use **CSV** when translators or PMs iterate in spreadsheets
* Use **XLIFF** when handing off to a translation agency or CAT tool
* Use **XML** / **YAML** to match an existing runtime's expected file shape

## Export Quality Checks

* Validate locale coverage
* Validate placeholder consistency
* Confirm environment-specific overrides

## Example JSON Output

```json theme={null}
{
  "auth": {
    "login": {
      "title": "Sign in",
      "submit_button": "Continue"
    }
  }
}
```

Pick the format based on your downstream system and automation needs.

## Next Steps

* Bring data in via [Import Translations](/api/import-translations)
* Wire automation from [Integration Examples](/api/integration-examples)