Run Multy R2 on your Cloudflare account

How the pieces fit

Requirements

• • Cloudflare account
• • R2 enabled (free tier is enough to start)
• • Workers enabled (free plan works)

Choose a path

Pick your deployment method — the guide will adapt to show only the steps you need.

1. Create an R2 bucket

1. 1

   Open R2 in the dashboard

   Go to the Cloudflare Dashboard. In the left sidebar open Storage & databases → R2 Object Storage (you can also create D1 from that same menu later).

   

2. 2

   Create a bucket

   Click Create bucket, pick a name (e.g. my-assets), create it. Repeat for each bucket you want Multy to manage.

2. Paste Multy's Worker bundle (recommended)

Fastest path for most users — dashboard only, no Node/pnpm required. The paste target is Multy's multi-bucket Worker (same runtime as a CLI deploy). You still must attach bindings and secrets in the dashboard — the JS file alone is not enough.

1. 1

   Get Multy's Worker bundle

   Get the prebuilt multi-bucket Worker from the rolling worker GitHub Release. Every push to main rebuilds and updates this asset.

   Open worker.js

   Opens the JS inline on GitHub (raw) — select all, copy, paste into the Worker editor.

   Raw: https://raw.githubusercontent.com/pantharshit007/multy-r2/release-worker-js/worker.js

   Download instead: https://github.com/pantharshit007/multy-r2/releases/download/worker/worker.js

   Optional local build: pnpm build:worker-bundle → dist-worker/index.js. Paste either file into the Worker editor.

   Local note: pnpm gen:bindings bakes friendly bucket labels from your wrangler.jsonc into the bundle. Runtime still resolves whatever R2 bindings you attach; only the display names in multi-bucket mode may show Multy's (or your local) bucket names.

2. 2

   Create a Worker (Hello World stub)

   Left sidebar: Compute → Workers & Pages → Create.

   

   Start with Hello World! — you will replace this stub with Multy's bundle next.

   

   Name the Worker (Cloudflare suggests a URL; you can edit it), then click Deploy.

   

3. 3

   Paste Multy's bundle in the editor

   Open the Worker (under Workers & Pages) → Edit code.
   Select all of the content, replace it with copied code from worker.js, then click Deploy (top right).

   

   After deploy, opening the Worker URL should show Multy R2 endpoint worker (not Hello World).

4. 4

   Add secrets (type must be Secret)

   Leave the editor and open Settings → Variables and secrets → + Add. Create both:

   • AUTH_KEY_SECRET — API key Multy sends as x-api-key
   • PRIVATE_LINK_SECRET — used for signed private links

   Use a strong, random value for each key. You can generate one with Avast's Password Generator (16+ characters recommended).

   Save your API key

   Copy and store the AUTH_KEY_SECRET value somewhere safe (e.g. a password manager or notepad) — you will need it later when connecting this UI to your Worker. Cloudflare will not let you view Secret values after saving.

   Use Secret, not Plaintext

   For both keys, set the Cloudflare type to Secret (encrypted). Do not leave them as Plaintext — Plaintext values are visible in the dashboard and in config exports.

   

5. 5

   Attach R2 bindings (and D1 if needed)

   Open Bindings (or Overview → Bindings → Add a binding) and connect each R2 bucket. For the default bucket path, use variable name R2_BUCKET or BUCKET_A. Add more bindings with any valid name for multi-bucket mode in the UI. Attach D1 as DB if you use control-plane routes.

   

   

6. 6

   Confirm the Worker is live

   Open the Worker URL again — you should still see Multy R2 endpoint worker. Save that URL;
   you will paste it into Multy next.

3. Connect Multy R2

1. 1

   Open the endpoint form

   On the home page, fill in the New Endpoint panel:

   • Workers Endpoint — your Worker URL (no trailing path)
   • API Key — same value as AUTH_KEY_SECRET
   • Custom Domain — optional; the R2 custom domain (or subdomain) connected to that bucket for public CDN URLs

   

2. 2

   Optional multi-bucket mode

   If the Worker exposes several R2 bindings, enable multi-bucket mode. The UI calls GET /api/r2/bindings with your API key and lets you pick a binding. Each binding can have its own R2 custom domain entered in Multy (one domain per bucket).

3. 3

   Save and open

   Save to localStorage, then open the endpoint card. Upload, list, delete, and copy public URLs all go through your Worker — credentials never leave the browser except as x-api-key to that host.

4. Custom domain (optional)

Public reads also work via the Worker at /cdn/<key> (default bucket) or /cdn/<binding>/<key> (multi-bucket). Writes stay on /api/r2.

How Multy ships the Worker JS bundle

Multy is TypeScript + Hono. There is no hand-written single file in the repo root — Wrangler produces the final multi-bucket bundle. That file is what end users paste.

pnpm build:worker-bundle
# → dist-worker/index.js
# CI renames to worker.js on the worker release