Get a public key

A frontend-created Cloud session needs a browser-safe public key. The dashboard creates one when you create a Public App.

1. Create a Public App

Sign in to Eazip, open Public Apps, and select Create app.

Use a name your team will recognize, such as Acme Photos.

2. Allow your application origins

Under Websites that can use this key, add each exact browser origin that will create Cloud sessions:

http://localhost:3000
https://staging.acme.example
https://app.acme.example

An origin is scheme + host + optional port. Do not include a path or query.

3. Allow your source hosts

Under Where the files come from, add the CDN, bucket, or asset hosts Eazip Cloud may fetch:

cdn.acme.example
acme-exports.s3.amazonaws.com

Enter hostnames rather than full URLs. These hosts are usually different from the frontend origins in the previous step.

4. Review the policy

The default advanced settings work for most first exports. Open them only when you need to restrict delivery modes, file counts, archive size, or retention. Current plan limits belong in the Cloud dashboard and pricing pages rather than application code.

5. Create the app and use the key

Select Create app & get key. The generated value starts with pk_ez_ and can be used in browser code:

'use client';

import { useEazip, EazipTray } from '@eazip/react';

export default function App({ urls }: { urls: string[] }) {
  const zip = useEazip();

  return (
    <>
      <button
        onClick={() =>
          zip.download({
            strategy: 'cloud',
            publicKey: process.env.NEXT_PUBLIC_EAZIP_KEY,
            files: urls,
          })
        }
      >
        Download as ZIP
      </button>

      <EazipTray />
    </>
  );
}

Verify the first job

Run one export with URLs from an allowed source host.

Next, read Public keys and origins for the security model or follow Create multi-GB ZIP archives with JavaScript.