File Downloads Made Simple

No. There are no file size or row count limits. Datasets with millions of rows are automatically split into chunked files and delivered as a ZIP archive. For very large datasets, we also offer an incremental download option where you can pull data in pages without downloading the entire file at once.

Yes. Scheduled file delivery is available on all paid plans. You can configure recurring deliveries to be sent to an email address, uploaded to an SFTP server, pushed to an Amazon S3 bucket, or dropped into a Google Drive or Dropbox folder at any frequency you define.

Standard download links expire after 7 days. Enterprise customers can configure extended link validity up to 30 days. If a link expires before you download, you can regenerate it from your dashboard at any time — the underlying file is retained for 90 days.

Yes. Delta or incremental downloads are supported. When you request a delta file, you receive only records that were added, updated, or removed since your previous download. This significantly reduces file sizes for recurring jobs and makes it easy to keep your database in sync without full reloads.

All files above 10MB are automatically gzip-compressed. CSV files use UTF-8 encoding by default, with proper quoting and escaping for special characters, commas, and line breaks within fields. JSON files use standard UTF-8 with Unicode escaping. Encoding can be changed to Latin-1 or UTF-16 on request.

Yes. You can configure any scraping job to generate multiple output formats in parallel. For example, you might receive the same dataset as both a CSV for your analyst team and a JSON file for your development team from every job run, without running the extraction twice.

CSV (Comma-Separated Values) is a flat, tabular format where each row represents a record and columns are separated by commas. It is universally compatible with spreadsheet tools and databases but cannot represent nested data structures. JSON (JavaScript Object Notation) supports hierarchical, nested data and is the standard format for web APIs and modern applications. Choose CSV for simple tabular data and spreadsheet workflows, and JSON when your data has complex nested relationships.

A delta export contains only the records that changed since your last download — new records, updated fields, and deleted entries — rather than a complete copy of the entire dataset. This approach dramatically reduces file sizes for recurring exports and speeds up data warehouse synchronization. Delta exports are identified by change type (insert, update, delete) so your import pipeline can apply the correct operation to each record in your database.

UTF-8 is a character encoding standard that can represent virtually every character in every language, from Latin alphabets to Chinese characters, Japanese kana, Arabic script, and emoji. It matters for ecommerce data because product titles and descriptions frequently contain non-ASCII characters, accented letters, currency symbols, and multilingual content. Using the wrong encoding causes these characters to appear as garbled text, corrupting product data and breaking search functionality.

Data compression reduces file sizes by encoding repetitive patterns more efficiently. Gzip compression typically reduces CSV and JSON file sizes by 70-90%, meaning a 100MB file downloads as 10-30MB. This dramatically speeds up transfer times, reduces bandwidth costs, and lowers storage requirements. Most modern programming languages and tools can decompress gzip files automatically, making compression transparent to the end user while providing significant performance benefits.

ETL stands for Extract, Transform, Load — the process of pulling data from source systems, converting it into a usable format, and loading it into a destination like a data warehouse. File downloads serve as the 'Extract' step, providing clean structured data in standardized formats. Tools like Apache Airflow, dbt, and Fivetran can automatically ingest downloaded files, apply transformations, and load the results into analytics platforms — creating a fully automated data pipeline.

A full export contains every record in your dataset at the time of generation, regardless of whether individual records have changed. A snapshot export captures the state of all records at a specific point in time and is stored as a versioned file for historical reference. Full exports are used for initial data loads and periodic reconciliation, while snapshot exports create an audit trail that lets you reconstruct exactly what your data looked like on any given date for trend analysis or compliance purposes.