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

# Export formats

> Export Octoparse task data to common file formats such as CSV, Excel, JSON, HTML, and XML.

Octoparse stores extracted results as structured records. After a task runs, you can export those records to file formats that fit your downstream workflow.

Use file export when you need to review data manually, share a dataset, import records into another tool, or archive task results.

## Supported formats

| Format | Best for |
| - | - |
| CSV | Spreadsheet tools, databases, lightweight data pipelines |
| Excel | Manual review, business reporting, spreadsheet workflows |
| JSON | Developers, APIs, scripts, and structured downstream processing |
| HTML | Previewing or preserving table-style output |
| XML | Systems that require XML-based data exchange |

## Choose the right format

> [card] Use CSV for compatibility
>
> CSV is widely supported and works well for databases, spreadsheets, and automation tools.

> [card] Use Excel for business users
>
> Excel is convenient when teams need to inspect, filter, or share data manually.

> [card] Use JSON for developers
>
> JSON preserves structured records and is easier to process in scripts and applications.

> [card] Use HTML or XML for specific systems
>
> These formats are useful when another tool or workflow specifically requires them.

## Export workflow

**1. Run the task**

Complete a local or Cloud Extraction run.

**2. Review the results**

Check field names, record count, missing values, and duplicate rows.

**3. Select an export format**

Choose the file type that matches your target workflow.

**4. Download or send the data**

Export the file manually or use an automatic export destination if configured.

## Before exporting

Check these items before using the exported data:

* Field names are clear
* Important fields are not empty
* Pagination captured the expected number of records
* Duplicate rows are acceptable or removed
* Data cleaning rules are applied
* The selected file format matches the downstream system

> [!NOTE]
>
> If your workflow needs recurring delivery, use Auto Export or an integration destination instead of downloading files manually.

## Related pages

> [card] [Automate cloud data exports](https://www.octoparse.com/docs/en/cloud/automate-cloud-data-exports.md)
>
> Send task results downstream automatically.

> [card] [Refine data](https://www.octoparse.com/docs/en/desktop/refine-data.md)
>
> Clean field values before export.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.