Get a public key

strategy: 'cloud' needs a publicKey. This page is the five minutes between "I want to try Cloud" and a key in your .env.

You need an Eazip account — sign up free (no card). The free tier is enough to run the export in this page end to end.

1. Create a Public App

A Public App is the policy your key carries: which sites may use it, which hosts it may fetch files from, and the per-session ceilings. Every publishable key issued for the app inherits that policy.

In the dashboard, open Public Apps → Create app, and give it a name your team will recognize (Acme Photos).

2. Add the websites that can use the key

Under Websites that can use this key, add the exact browser addresses where your app runs. The API compares each session-create request against the Origin header the browser sends.

Add every origin you'll develop and ship from, including local dev:

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

Use scheme + host + optional port. Do not add a path or query — https://app.acme.example/exports is not an origin. A trailing slash is normalized for you. A request from anywhere else is rejected, which is what makes the key safe to ship.

3. Add where the files come from

Under Where the files come from, add the hosts the API is allowed to fetch from. This is usually a different list from the websites above: your frontend address belongs in the first list, while your CDN, bucket, or asset host belongs here.

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

Enter bare hostnames — no scheme, port, or wildcard. Only this path is optional; use it when Eazip should fetch from one folder such as /exports rather than the whole host.

Both lists work the same way: edit each row directly, use Add another… to add an environment or file host, then save everything once at the bottom.

4. Keep the recommended defaults

Advanced settings starts collapsed because most apps do not need to change it. The defaults enable both delivery modes, allow 100 files per export, retain stored ZIPs for one day, and use your plan's size limit.

Open it only when you need a stricter delivery mode, file count, retention, or total-size ceiling. You can change these settings later; edits apply to new exports.

5. Create the app and copy the key

Click Create app & get key. The key looks like pk_ez_… and stays readable on the dashboard, so you don't have to store it anywhere secret:

'use client';

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

function Exporter({ urls }) {
  const zip = useEazip();

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

It ships in your JS bundle by design — see Public keys & origins for why that's safe and what the policy behind it enforces.

6. Run one export

Point a session at two files on an allowed source host and press the button. <EazipTray /> narrates the same five states as a local job, so a working cloud export looks like a working local one.

If it doesn't work, the fix is almost always on the dashboard rather than in SDK options:

For the failure taxonomy and how errors surface in the tray, see Partial results & errors.

Next

• Stream vs stored — delivery modes and expiry
• Zip GB-scale, 1,000+ URL jobs — a full worked example
• Plan limits and pricing live in the Eazip Cloud product area