コンテンツにスキップ

FAQ

このコンテンツはまだ日本語訳がありません。

Eazip is an API service that converts multiple remote files into a single ZIP file. It’s perfect for:

  • Archiving web content
  • Batch downloading files
  • Creating backups
  • Data collection pipelines
  1. Send a files array to our API
  2. We download all files in parallel
  3. Files are packaged into a ZIP
  4. You get a download link

Eazip can download any publicly accessible URL. Common use cases include:

  • Documents (PDF, DOCX, etc.)
  • Images (PNG, JPG, SVG, etc.)
  • Data files (JSON, CSV, XML, etc.)
  • Any other downloadable content

Yes! The free tier includes:

  • Up to 100 files per job
  • Max 2 GB per ZIP archive
  • 20 GB/month of stream downloads
  • 100 GB-day/month of stored archives
  • 24-hour file retention
  • No overage

Paid plans combine a monthly subscription with included stream and stored quotas:

  • Starter: $9/month, 500 GB stream and 3,000 GB-days stored
  • Pro: $29/month, 3 TB stream and 20,000 GB-days stored
  • Scale: $99/month, 20 TB stream and 75,000 GB-days stored

Paid plans can optionally allow overage. Overage is billed at $0.004/stream GB and $0.002/stored GB-day.

What is the difference between stream and stored billing?

Section titled “What is the difference between stream and stored billing?”

Stream mode creates the ZIP during download, so usage is based on delivered ZIP bytes. Stored mode creates and stores the ZIP, so usage is based on ZIP size multiplied by retention time.

Stored downloads are included after the archive is created. Stream downloads count toward stream quota because the ZIP is generated and delivered for that request.

Free plans and paid plans with overage disabled are hard-capped: new over-quota stored jobs and stream downloads are rejected. Paid plans can turn overage on to continue accepting new jobs and downloads beyond included quota.

Turning overage off applies immediately to new work. Existing stored ZIPs are not shortened or deleted automatically, so any already-committed stored overage remains billable until the archive expires or is deleted.

What’s the maximum number of files per job?

Section titled “What’s the maximum number of files per job?”
  • Free: 100 files
  • Starter: 1,000 files
  • Pro: 5,000 files
  • Scale: 20,000 files

Need more? Contact us for enterprise plans.

By default, ZIP files are stored for 24 hours. Paid plans can use longer retention: Starter up to 7 days, Pro up to 60 days, and Scale up to 90 days.

What happens if a file URL fails to download?

Section titled “What happens if a file URL fails to download?”

By default (fail_on_url_error: true), the job fails immediately when any file URL cannot be fetched. If you set fail_on_url_error to false, the job continues with the remaining files and failed URLs are reported in the job status with error details.

Each ZIP archive has a plan limit. Free supports up to 2 GB per archive, Starter up to 10 GB, Pro up to 50 GB, and Scale up to 100 GB. Stream mode uses the same per-archive limit, but 10 GB is recommended for best reliability; use stored mode for larger or customer-facing downloads.

Yes. Pass max_zip_size_bytes when creating a job to auto-split the output. Eazip bin-packs your files into N ZIPs, each capped at the size you specify (min 100 MB, max 500 GB), and returns a zips[] array — one entry per ZIP file with its own download URL.

You can choose between two strategies via split_strategy:

  • preserve-order (default): keeps the input order across bins. Useful for chronological photo dumps or chapter-ordered exports.
  • ffd (First-Fit-Decreasing): minimises bin count by sorting files by size first.

If a single file is larger than max_zip_size_bytes, Eazip places it in a dedicated bin that exceeds the cap by default. Pass allow_oversize_zips: false to fail the job instead. See the Jobs API reference for the full payload shape.

Yes. Each entry in the files array can include an optional filename. If omitted, Eazip derives the filename from the source URL and response metadata. For the ZIP filename itself (one per output bin), see Filename templates.

Currently, only publicly accessible URLs are supported. Authenticated URL support is on our roadmap.

  • All transfers use HTTPS
  • Download URLs are signed and expire
  • Files are automatically deleted after retention period
  • We don’t access or analyze your file contents

Data is stored on Cloudflare’s global network, ensuring fast access worldwide and compliance with data protection regulations.

There is no documented self-serve delete endpoint today. ZIP files are automatically deleted after the retention period expires.

  • Documentation: You’re reading it!
  • Email: [email protected]
  • Pro and Scale users: Priority support with faster response times

Please email [email protected] with:

  • What you expected to happen
  • What actually happened
  • Steps to reproduce
  • Any error messages

We do not currently publish a formal SLA in the public docs or terms.