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.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.
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
Use CSV for compatibility
CSV is widely supported and works well for databases, spreadsheets, and automation tools.
Use Excel for business users
Excel is convenient when teams need to inspect, filter, or share data manually.
Use JSON for developers
JSON preserves structured records and is easier to process in scripts and applications.
Use HTML or XML for specific systems
These formats are useful when another tool or workflow specifically requires them.
Export workflow
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
If your workflow needs recurring delivery, use Auto Export or an integration destination instead of downloading files manually.
Related pages
Auto export & scheduling
Send task results downstream automatically.
Refine data
Clean field values before export.