> ## 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

<Columns cols={2}>
  <Card title="Use CSV for compatibility">
    CSV is widely supported and works well for databases, spreadsheets, and automation tools.
  </Card>

  <Card title="Use Excel for business users">
    Excel is convenient when teams need to inspect, filter, or share data manually.
  </Card>

  <Card title="Use JSON for developers">
    JSON preserves structured records and is easier to process in scripts and applications.
  </Card>

  <Card title="Use HTML or XML for specific systems">
    These formats are useful when another tool or workflow specifically requires them.
  </Card>
</Columns>

## Export workflow

<Steps>
  <Step title="Run the task">
    Complete a local or cloud extraction run.
  </Step>

  <Step title="Review the results">
    Check field names, record count, missing values, and duplicate rows.
  </Step>

  <Step title="Select an export format">
    Choose the file type that matches your target workflow.
  </Step>

  <Step title="Download or send the data">
    Export the file manually or use an automatic export destination if configured.
  </Step>
</Steps>

## 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.
</Note>

## Related pages

<Columns cols={2}>
  <Card title="Auto export & scheduling" href="/docs/platform/auto-export">
    Send task results downstream automatically.
  </Card>

  <Card title="Refine data" href="/docs/platform/refine-data">
    Clean field values before export.
  </Card>
</Columns>
