Download S3 or R2 Objects as a ZIP

The browser should receive short-lived object URLs, never S3, R2, or S3-compatible storage credentials.

Prepare a signed source list

Your backend endpoint should:

1. authenticate the application user;
2. authorize each requested object;
3. create a short-lived signed URL; and
4. return only { url, filename } entries.

The exact signing code depends on the storage provider and belongs on the server.

Fetch the list and create the ZIP

import { createZip } from '@eazip/core';

type SignedSource = {
  url: string;
  filename: string;
};

const response = await fetch('/api/exports/123/files', {
  credentials: 'include',
});

if (!response.ok) {
  throw new Error('Could not prepare export files');
}

const files = (await response.json()) as SignedSource[];
const result = await createZip({
  files,
  zipName: 'project-files.zip',
});

result.downloadAll();

For a Local job, the bucket or CDN must allow browser CORS and each signed URL must remain valid until its file has been fetched.

Use Cloud for larger object sets

Cloud fetches the same signed URLs outside the browser:

const result = await createZip({
  strategy: 'cloud',
  publicKey: 'pk_ez_...',
  files,
  zipName: 'project-files.zip',
});

Add the bucket or CDN hostname to the Public App's allowed source hosts. Make the signed URL lifetime long enough for Eazip Cloud to start and finish reading the source.

Continue with Backend-created sessions or Public keys and origins.