> For the complete documentation index, see [llms.txt](https://help.join.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.join.com/candidates-and-applications/application-export.md).

# Application export

In this article, you’ll learn how to export candidate lists and documents from the Applications tab or directly from specific job views.

You can export candidate details and documents directly from JOIN whenever needed. This could be useful for reporting, sharing, or backup purposes.

{% hint style="warning" icon="hand-back-point-right" %}
Application export is available on the Advanced and Enterprise plans. Upgrade your plan to use this feature. 

<a href="https://join.com/settings/company/billing?source=companySettings" class="button secondary small">View plans</a>
{% endhint %}

## Export formats

You can export candidate data in three formats:

* **CSV** – candidate list only
* **XLSX** – candidate list only
* **ZIP** – candidate list + candidate CVs and attachments

***

## Export applications

You can export candidates and their applications across all jobs from the `Candidates` tab:

1. Go to the `Candidates` tab.&#x20;
2. Navigate to the relevant sub-tab: `Active`, `Hired`, or `All` (all include the option to export).
3. Select the candidates using the checkboxes, or leave them unselected to export everyone in the chosen sub-tab. You can also use filters like `Job`, `Job Status`, `Stage`, etc. to narrow your results.
4. Click the `Export` button in the top-right corner.
5. Choose your desired format (CSV, XLSX, or ZIP) and confirm the export.
6. Once the file is generated, you’ll receive it at the email address linked to your JOIN account. You’ll also see a confirmation message:

> Your file is being generated. We will email you when it's ready for download.

{% hint style="success" %}
Each recruiter can run their own export independently. If a colleague already has one in progress, it won't stop you from starting yours.
{% endhint %}

***

## Export job-specific applications

You can export applications tied to a specific job using two methods:

#### Option 1: From 'Candidates' tab

Filter for the job in `Candidates` tab and follow the steps mentioned [above](#export-applications).

#### Option 2: From 'Applications' tab of a job

1. Go to the `Jobs` > `Active` tab. Click on the relevant job.
2. You will be directed to the `Applications` sub-tab.
3. You can select specific candidates here using checkboxes. If you don't make specific selections, then all the applications will get exported.
4. Click the overflow menu <i class="fa-square-ellipsis">:square-ellipsis:</i> in the top-right corner.
5. Hover over `Export application list`, then choose a format (CSV, XLSX, ZIP) and confirm the export.
6. Once the file is generated, you’ll receive it at the email address linked to your JOIN account. You’ll also see a confirmation message.

You can also select specific candidates here using checkboxes and export them from the toolbar at the bottom by clicking the <i class="fa-square-ellipsis">:square-ellipsis:</i> menu and selecting Export.

{% hint style="info" %}
Whichever entry point you export from, the file always contains application-level rows (one per application, not one per candidate). Exporting from the `Candidates` tab includes every application matching your filters; exporting from a job's `Applications` tab only includes applications to that job.
{% endhint %}


---

# 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://help.join.com/candidates-and-applications/application-export.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.