Stream or stored
Choose whether Eazip Cloud generates an archive on download or prepares and retains it ahead of time.
Cloud supports two delivery modes. The SDK defaults to stream; set mode only
when stored better matches the download lifecycle.
const zip = useEazip();
zip.download({
strategy: 'cloud',
publicKey,
files: urls,
mode: 'stored',
});const result = await createZip({
strategy: 'cloud',
publicKey,
files: urls,
mode: 'stored',
});
result.download();Which mode should I choose?
| Stream | Stored | |
|---|---|---|
| Archive generation | When a download starts | Before the download is offered |
| Repeat download | Regenerates the archive | Reuses the prepared archive |
| Source availability | Sources must remain reachable for each download | Sources are needed while the stored archive is built |
| Best for | One-time or immediate downloads | Repeat downloads or a stable prepared artifact |
Your Public App must allow the selected mode. The result still exposes the same ZIP outputs and download methods.
What expires?
The session and its download access have a configured lifetime. Once access expires, start a new export for fresh links.
Resume is for a still-valid, in-progress session; it does not renew expired
output. React's tray converts expired Cloud output into an expired task
state instead of leaving a dead download action.
How does usage differ?
Stream and stored consume different Cloud usage meters. Stream is based on delivered data; stored is based on archive size and retention.
Use the current dashboard and pricing page for plan-specific quotas and prices.
For keeping stored usage predictable, see Understand zero-egress ZIP exports.