> For the complete documentation index, see [llms.txt](https://docs.datasaur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasaur.ai/data-studio-projects/export-project.md).

# Export Project

## Export projects

Both features are supported through API call. Click [here](/api/export-project.md) for more detailed explanation.

1. Go to the **File** menu.
2. Select **Export file** or **Export all files**.

<figure><img src="/files/hHX0TvbzELDpHoZ8B3U6" alt=""><figcaption></figcaption></figure>

* **Export** **file:** Export only the currently opened file. The output reflects the latest project state and does not include all project data.
* **Export all files:** Export all files in the project. For projects with multiple assignees, each labeled version is exported separately. The output is a `.zip` file containing three folders:
  * **DOCUMENT-Labeler-name:** Contains files labeled by each labeler.
  * **REVIEW:** Contains the final version, including auto-accepted labels and reviewer edits.
  * **ROOT:** Contains the original raw text without any labels or edits.

## Advanced settings

When exporting, you can configure additional settings to control what gets included in the export.

<figure><img src="/files/rtvIFRA9IsOMiicGkgBT" alt=""><figcaption></figcaption></figure>

### Export work from assignee

{% hint style="info" %}
This setting is only visible to Supervisor and Admin roles, and is only supported when using export all files in the Reviewer mode.
{% endhint %}

Choose whose work to include in the export:

* **All labelers** — Includes work from every labeler.
* **All reviewers** — Includes work from every reviewer.
* **Specific labeler** — Includes work from one or more selected labelers.

### **Fields to export**

{% hint style="info" %}
Fields to export is only available for the **Datasaur Schema** and **File Transformer**, and is currently only supported for **Span+Line** and **Row labeling** projects.
{% endhint %}

Select which fields to include in the export output:

* **Line numbers** — Identifier for each row.
* **Contents** — Original text content from the documents.
* **Span labels** — Label classes applied to spans.
* **Row/Line answers** — Question-answer pairs applied to individual rows/lines. Available only in row/line labeling projects.
* **Metadata** — Additional data fields associated with the content.
* **Comments** — Comments added to labels, relationships, or spans.
* **Label sets** — Collections of label classes used for labeling.
* **Row/Line questions** — Collections of questions used for row/line answering.

In File Transformers, these fields are available as secondary, nullable inputs. You can customize your export transformer based on the selected fields. See the attached file for an example File Transformer that outputs the document together with the export configuration. Feel free to try it out and modify it to suit your needs.

{% file src="/files/tpmshKCeNiJnTGe3wD4o" %}

<figure><img src="/files/2k9E6zZ8p5erKojHAN5i" alt=""><figcaption></figcaption></figure>

### Include unresolved labels / answers

{% hint style="info" %}
This is supported for **span**, **row**, and **document labeling** projects in both **Datasaur Schema** and **CSV** formats.
{% endhint %}

You can include unresolved labels or answers inside the export result.

#### Enable the option

When you select a supported export format, a checkbox will appear. If selected, unresolved labels or answers will be included in the export.

#### Export result

* **Comma-separated values (.csv)**
  * **New column: Label Status**

    This column indicates whether a line is conflicted or resolved.
  * **New column: Line**

    This column indicates the line number.
* **Datasaur Schema (.json)**
  * **New values:** <mark style="color:red;">`rowAnswers`</mark>, <mark style="color:red;">`documentAnswers`</mark>, <mark style="color:red;">`spanLabels`</mark>, <mark style="color:red;">`arrowLabels`</mark>

    The conflicted values will be added to <mark style="color:red;">`rowAnswers`</mark>, <mark style="color:red;">`documentAnswers`</mark>, <mark style="color:red;">`spanLabels`</mark>, or <mark style="color:red;">`arrowLabels`</mark>.

    You can differentiate between resolved and unresolved answer by looking at <mark style="color:red;">`labeledBy`</mark> attribute. Unresolved label should have **CONFLICT** as their <mark style="color:red;">`labeledBy`</mark> value.

The following section will give you some illustration on the result.

* **Span labeling**
  * **Datasaur Schema (.json)**

    Conflicted labels will be added to <mark style="color:red;">`spanLabels`</mark> or <mark style="color:red;">`arrowLabels`</mark>.
  * **Comma-separated values (.csv)**

    This format is similar to the Amazon Comprehend CSV export format, but with an additional column titled `Label Status`.
* **Row and document Labeling**
  * **Datasaur Schema (.json)**

    Unresolved answer will not be added to the answer set (<mark style="color:red;">`rowAnswerSets`</mark> for Row Labeling, while <mark style="color:red;">`documentAnswerSets`</mark> for Document Labeling)

    However, it will be added to <mark style="color:red;">`rowAnswers`</mark> for Row Labeling, while <mark style="color:red;">`documentAnswers`</mark> for Document Labeling, along with the resolved answers.
  * **Comma-separated values (.csv)**

    Adds `Label Status` and `Line` column.

    There may be cases where a single line contains both resolved and unresolved answers due to consensus. In such cases, the answers are split into two lines: one for resolved answers and one for unresolved answers.

## Export methods

When exporting a file, you can choose from several delivery options. All methods are also available via [API](https://datasaurai.gitbook.io/datasaur/api/apis-docs).

![](/files/fwoAFhIr2lu45YPvVBPD)

### **Download**

* The export result is uploaded to Datasaur's storage bucket, and you download it directly to your device via a generated link.
* Keep in mind that the time needed to generate the link will be directly proportional to the size of the project.

### **Email**

* Datasaur will generate a download link and send it to the email address used for your account.
* The link **expires in 6 hours**.

### **Webhook**

* The export result is sent as a payload in a webhook request.
* See the [Webhook](/api/export-project/custom-webhook.md) documentation for full details.
* The link **expires in 6 hours**.

### **External Object Storage**

* The export result is uploaded directly to your selected external storage bucket.
* You can also add a prefix to the file name. The prefix is appended directly without a separator. For example:
  * Prefix: `test`
  * File name: `name.json`
  * Result: `testname.json`

## Export multiple projects from the Projects page

You can export multiple projects with the **same project settings** in the **Projects** page.

1. Select all projects you want to export.

<figure><img src="/files/7YjyuCPtRtPDmDRUy679" alt=""><figcaption></figcaption></figure>

2. Click **Export** button. You can choose the export format and method. The output will be a `.zip` file.

<figure><img src="/files/bNG36OMJLce9KxjCbNke" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
We recommend exporting up to 10 projects at once for better performance.
{% endhint %}