> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/import-and-export-data/export-data.md).

# Export data

Use export to move table data from Ninox into other tools for reporting, sharing, or further processing.\
You can export data as **CSV** for spreadsheets or as **JSON** for structured processing and integrations. Ninox downloads exported files directly to your local device.

#### CSV settings

For **CSV** exports, you can control how Ninox formats the file.

* Use **Include header** to add the field names to the first row.
* Use **Include separator definition in header** to add the separator definition at the top of the file.

Then review these options:

* **Delimiter** defines how columns are separated, such as comma, semicolon, pipe, or tabulator. Choose the separator your spreadsheet app or import tool expects.
* **Date format** defines how Ninox writes date values, such as **Locale**, **ISO 8601**, **GMT**, or **UNIX timestamp**. Choose a format your next tool can read without conversion.
* **Number format** defines how decimal values are written, such as **Locale**, `1234.56`, or `1234,56`. Match this setting to the decimal format your target tool expects.
* **Quote character** defines which quotation marks wrap text values. This helps when values contain separators or special characters.
* **Encoding** defines the character set, such as **UTF-8 (Unicode)**. Choose the encoding that keeps special characters readable in the target app.
* **Include BOM** adds a byte order mark to the file header. This can help some spreadsheet apps detect the file encoding correctly.

Choose the settings that match the tool that will open the file next.

### Export data as CSV

Choose **CSV** when you want to work with the data in a spreadsheet app or send it as a flat file.

{% stepper %}
{% step %}
**Open the export dialog**

Open the table in the **app screen**.\
In the toolbar, click **Import/export**.\
Then click **Export data**.
{% endstep %}

{% step %}
**Choose CSV**

In the export dialog, select **CSV**.
{% endstep %}

{% step %}
**Review the CSV settings**

Check whether you want to include the header row.\
If needed, turn on **Include separator definition in header**.

Then review these options:

* **Delimiter**
* **Date format**
* **Number format**
* **Quote character**
* **Encoding**
* **Include BOM**
  {% endstep %}

{% step %}
**Download the file**

Click **Download as CSV**.

Ninox downloads a CSV file of the table directly to your local device with the settings you selected.
{% endstep %}
{% endstepper %}

### Export data as JSON

Choose **JSON** when you want a structured export for integrations, scripts, or further processing.

{% stepper %}
{% step %}
**Open the export dialog**

Open the table in the **app screen**.\
In the toolbar, click **Import/export**.\
Then click **Export data**.
{% endstep %}

{% step %}
**Choose JSON**

In the export dialog, select **JSON**.
{% endstep %}

{% step %}
**Download the file**

Click **Download as JSON**.

Ninox downloads a JSON file of the table directly to your local device for structured reuse in other tools.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ninox.com/builder-hub/design-your-app/import-and-export-data/export-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.