Extract files from a huge remote ZIP via HTTP byte-range reads — without downloading the whole archive.
Access
Gated demo. Access codes are managed in the admin panel.
Reconnecting to your job…
1 — Source archive
Extraction speed depends on how fast the source server answers byte-range requests. A slow or non-CDN host is the bottleneck, not rangezip.
2 — Destination
Files are written to the demo bucket and auto-deleted after the TTL.
You'll see a live countdown once extraction completes.
Use a scoped, write-only key for just this bucket/prefix — not a root key.
Your credentials are sent over HTTPS, held only in memory for the run, never stored or logged.
Write speed depends on your S3/R2 provider's throughput and region — that sets the pace for keeping the files, not rangezip.
3 — Extract
Progress pending
1
Reading index
sequential · 1×
→
2
Extracting
parallel
→
✓
Done
—peak concurrent extractions
0% · 0 / 0 · clears in —
—
range bytes vs archive
—
bytes fetched
—
archive size
—
bytes not fetched
—
range requests
—
peak concurrency
—
files extracted
—
bucket writes
—
index-read time
—
extraction time
—
total time
—
compute time (measured)
—
central dir reads (reused)
Per-file status
Extracted files
Files were written to your bucket — yours to keep. rangezip won't list or delete them.
