> For the complete documentation index, see [llms.txt](https://docs.corraldata.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corraldata.com/kb/explore-your-data/export-raw-data.md).

# Export Raw Data

Every widget's standard **Export CSV** covers most needs, but it's capped at 3,000 rows. When you need the full result set behind a widget — up to 1,000,000 rows — use **Export Raw CSV** instead.

***

### How it works

Export Raw runs asynchronously: instead of downloading immediately, CorralData generates the file in the background and notifies you when it's ready. This is what makes it possible to pull far more data than a normal export — the query isn't held open in your browser while it runs.

{% hint style="info" %}
If a widget's result set is larger than the standard export can handle, CorralData will route that export through Export Raw automatically.
{% endhint %}

***

### Exporting

{% stepper %}
{% step %}

#### **Open the widget menu**

Click the **⋮** menu in the top corner of any widget.
{% endstep %}

{% step %}

#### **Select Export Raw CSV**

The export starts running in the background — you can keep working while it generates.
{% endstep %}

{% step %}

#### **Check your notifications**

You'll get a notification when the file is ready to download.

{% hint style="info" %}
If you don't see the notification right away, try refreshing the page — it may already be waiting for you in the notification panel.
{% endhint %}
{% endstep %}
{% endstepper %}

***

### Where this fits

* Use the regular **Export CSV** for anything under 3,000 rows — it's instant, with no need to wait for a notification.
* See View a Widget Query if what you actually need is the SQL behind a widget, not the exported data itself.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.corraldata.com/kb/explore-your-data/export-raw-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
