Put your Studio online.

You open a free Cloudflare account, and the deploy tool in the Studio download puts Studio in it: your AI assistant runs it for you (route 4), or you run it from a terminal (route 5). Your Studio gets an address like snaps.yourname.workers.dev. You can add your own domain later without losing anything.

1. Create your Cloudflare account Sign up at dash.cloudflare.com/sign-up with an email address you check every day, and confirm it before you go on. You can skip Cloudflare’s questions about adding a website.
2. Turn on storage Your captures are stored in Cloudflare R2. In the Cloudflare dashboard, open Storage & databases → R2 → Overview and complete Cloudflare’s checkout to add R2. Cloudflare may ask for a card or PayPal before it turns R2 on, even if you stay within its free allowance.
3. Hand the Studio download to your AI assistant Download Studio from Maxisnap (see the top of this page) and extract it, then paste the ready-made instructions into your assistant. It follows AGENTS.md in the Studio folder and asks you for a Cloudflare API token, which you create in Cloudflare under My Profile → API Tokens with the permissions it lists.
4. Pick your address Choose a Studio name with lowercase letters, numbers and dashes. If your account has no workers.dev name yet, you pick one now as well. It is shared by everything in that account and hard to change later, so your company name is a good choice.
5. Check the plan, then create your Studio The deploy first shows a plan: everything Studio will create, and everything in the account it will not touch. Nothing is created until you say yes.

Studio is added to your Cloudflare account next to your website, on its own free workers.dev address, plus a new subdomain you choose, such as snaps.yourcompany.com, if you want one. Your AI assistant (route 4) or the command-line deploy (route 5) does it with the deploy tool in the Studio download. It reads your account first, shows a plan of what Studio adds and what it leaves alone, and creates nothing until you say yes. R2 storage must be on in the account; if it isn’t, the plan says so.

If a name is already in use, Studio picks another or asks you to; it does not replace something that is already there. A subdomain must be on a domain in the same Cloudflare account, and for one the API token also needs Zone Read, DNS Read and Workers Routes Read. Cloudflare adds one DNS record for that name only. The workers.dev address works from the start; the new name can take a while to start working.

Studio for web hosting is the snaps folder in your Studio download. Upload that folder, or upload it as one file, snaps.zip, which you get when you lock in your branding (your own look or the Maxisnap look). Studio needs PHP 8.0 or newer on Apache or LiteSpeed with .htaccess rules enabled. When you’re done, your Studio lives at yourcompany.com/snaps.

Upload snaps.zip with your hosting’s File Manager

Open your Studio once to finish

Open https://yourcompany.com/snaps/ in your browser. The first visit runs a short setup: it checks your hosting and shows your Admin key. Copy that key before you click “Create my dashboard”, then connect Maxisnap with your Studio’s address and that key.

Paste ready-made instructions into Claude Code, Codex, Cursor or another coding assistant that can run commands on your computer. It reads AGENTS.md in your Studio folder, which explains both editions, the exact install steps, what must stay private and how to check the result. The instructions tell it to ask you before it changes anything.

Replace the line in angle brackets with the folder where you extracted the Studio download. For the Cloudflare edition your assistant asks you for a Cloudflare API token; AGENTS.md tells it which permissions the token needs and where you create it.

Set up Maxisnap Studio for me.

Maxisnap Studio is a self-hosted dashboard for the screenshots and screen recordings the Maxisnap desktop app uploads: a private library plus branded share links. It comes in two editions with the same features: a PHP app for ordinary web hosting, and a Cloudflare Worker that uses R2 and D1.

Everything is in this folder on my computer:
  <the folder where I extracted the Studio download>

Start by reading AGENTS.md in that folder. It explains both editions, the exact install steps, what must stay private, and how to check the result.
If I locked in my branding, it is in snaps.zip; AGENTS.md says what to do if it is missing.

Goal: Work out with me whether the PHP edition (my web hosting) or the Cloudflare Workers edition fits my setup, then install it.

Rules:
- Ask me before you upload, deploy, or change anything on a server or in an account, and tell me exactly what you will change.
- Never delete, overwrite or rename existing website files, DNS records, Workers, buckets or databases. Studio only adds new things.
- Keep keys and passwords out of files you create and out of chat transcripts where you can.
- When it works, give me the Studio address and the Admin key so I can connect the Maxisnap app (on Windows, Settings, Account, Maxisnap Studio setup wizard, step 4; on a Mac, Settings, Welcome & Help, Studio Setup Guide, “I already have a dashboard”).

When it works, your assistant gives you the Studio address and the Admin key. Connect Maxisnap with them.

Two editions of the same app, with the same URLs, upload API, dashboard and roles: a database-free PHP app for Apache, LiteSpeed or nginx hosts, and a Cloudflare Worker backed by R2 and D1. On nginx, reproduce the routing and deny rules from snaps/.htaccess; the Developer guide lists them.

Maxisnap-Studio-v<version>/
  Maxisnap Studio - Start Here.html   guided setup (branding + every route)
  snaps/                              PHP edition: upload this folder to a web host
  cloudflare/                         Cloudflare Workers edition (Worker + R2 + D1)
    deploy/cli.mjs                    deploys it through the Cloudflare API (Node 20+)
  docs/Developer guide.html           architecture, upload API, security, updates
  docs/Cloudflare setup - technical brief.html
  AGENTS.md                           instructions for AI coding assistants

Deploy the Cloudflare edition from a terminal

cd cloudflare
# Option 1: the bundled CLI (Node 20+; plan first, then --yes). PowerShell:
$env:CLOUDFLARE_API_TOKEN = "<token: Account Settings Read; Workers Scripts, R2 and D1 Edit;
                              for --zone/--hostname also Zone Read, DNS Read, Workers Routes Read>"
node deploy/cli.mjs whoami
node deploy/cli.mjs plan --account <account id> --name snaps
#   no workers.dev name on the account yet? The plan asks you to "Choose your free
#   workers.dev name": add --subdomain <your-company> to both commands (account-wide).
#   A subdomain of your domain as well: add --zone <zone id> --hostname snaps.example.com
node deploy/cli.mjs deploy --account <account id> --name snaps --yes
#   prints the Studio address and the Admin key once, and writes deployment.json here

# Option 2: plain Wrangler (create the bucket and database, set their ids in wrangler.jsonc)
npm install
npx wrangler r2 bucket create maxisnap-studio-media
npx wrangler d1 create maxisnap-studio
npx wrangler secret put ADMIN_KEY
npm run sync
npx wrangler deploy

Good to know

• The Maxisnap apps upload with an X-Dashboard-Key header to api/upload.php; the Workers edition accepts up to 25 MB in one such request. It also has a chunked upload API for larger files (api/upload/start, part and complete), described in the Developer guide.
• Share pages are /<slug>, media bytes /<slug>.<ext>; everything else is internal. Keep uploads/, data/ and branding/ private on PHP hosts.
• Updating PHP installs: replace only the files listed in snaps/How to update.txt. Updating the Workers edition: from a newer package’s cloudflare folder, with the old deployment.json copied in, run node deploy/cli.mjs update --record deployment.json --yes. The CLI writes that record in the folder it runs from. Captures, people and settings stay.
• The CLI reads the account first, shows a plan and refuses names that are already in use. If a deploy stops half-way, running the same command again continues without creating anything twice.

The full Developer guide (architecture, upload API, keys and roles, security model, troubleshooting) is docs/Developer guide.html in the Studio download.