Add Studio to your business’s Cloudflare account
If your company’s domain is already managed in Cloudflare, Studio can go into that same account, next to your website. It gets its own free workers.dev address and, if you like, a new subdomain of your domain. Your website and its DNS records stay exactly as they are.
- Best for
- Businesses whose domain is already managed in Cloudflare.
- You need
- Maxisnap for Windows or Mac, signed in with the account that has Studio; a sign-in to your company’s Cloudflare account that can add Workers, or the person who looks after it; and an AI coding assistant on your computer, or a terminal with Node.js 20 or newer.
- Time
- About 20 minutes the first time.
- You get
- Studio on its own workers.dev address, plus a new subdomain such as snaps.yourcompany.com if you want one. Your website stays exactly as it is.
- Cost
- Studio is built to run on Cloudflare’s free plan. Cloudflare publishes R2’s current free allowance and prices.
What Studio adds, and what it leaves alone
Studio adds
- The Studio app itself (Cloudflare calls it a “Worker”)
- A storage space for your captures (an “R2 bucket”)
- A small database for your library and team (“D1”)
- Its address on workers.dev, plus one new subdomain if you pick one
- Your account’s workers.dev name, if it has none yet (one name for the whole account)
Studio leaves alone
- Your website and its files
- Your domains’ existing DNS records
- Any other Worker, storage or database
- Your billing and your other account settings
If a name is already in use, Studio picks another or asks you to; it does not replace something that is already there.
If someone else looks after your Cloudflare or your website, check with them first. Some companies have rules about who adds services to the company account, or put a sign-in page in front of every subdomain, which would block Maxisnap’s uploads.
Share the technical brief with the person who looks after your Cloudflare.
Check that storage is on
Studio stores your captures in Cloudflare R2. Sign in to your company’s Cloudflare account and check it once:
- In the Cloudflare dashboard, open Storage & databases → R2 → Overview.
- If Cloudflare offers to add R2, complete its checkout. If you are not the account’s billing owner, ask them to do this step.
Your Studio dashboard shows how much storage you use. Cloudflare's R2 documentation, read in October 2026, says R2 is free to get started with included free monthly usage, and that you are billed for your usage on a monthly basis.
Get Studio on your computer
- On Windows: in Maxisnap, open Settings → Account → Maxisnap Studio setup wizard, click “Get started”, then “Download dashboard”. Maxisnap saves the Studio ZIP to your Downloads folder and opens that folder.
- On a Mac: in Maxisnap, open Settings → Welcome & Help → Studio Setup Guide, click “Get Started”, then “Download Dashboard”. Maxisnap saves the Studio ZIP to your Downloads folder.
Extract the ZIP. On Windows, right-click it and choose “Extract All”. On a Mac, double-click it.
Want your logo and colours from the start? Double-click “Maxisnap Studio - Start Here.html”, design your branding and click “Lock in my branding”. Your assistant uses it. Or skip it and change the branding later in your dashboard under Branding.
Decide on the address
Studio always gets a workers.dev address, which works from the start. You can add a new subdomain of your domain as well, such as snaps.yourcompany.com, if the domain is active in this Cloudflare account.
Your address will look like this: snaps.yourcompany.workers.dev
You can add your own domain later without losing anything.
Hand it to your AI assistant
- Open your AI coding assistant: Claude Code, Codex, Cursor or another one that can run commands on your computer.
- Copy the ready-made instructions from the AI assistant guide, replace the line in angle brackets with your Studio folder, and paste them in.
- Tell it that your business already uses Cloudflare, and whether you want a subdomain. It reads the instructions file in your Studio folder and explains each step before it does it.
Create a Cloudflare key when your assistant asks
The deploy needs permission to work in your account. You give it with a Cloudflare API token, which works like a password for this one job.
- In Cloudflare, open My Profile → API Tokens, click “Create Token” and choose to create a custom token.
- Add these four permissions: Account Settings Read, Workers Scripts Edit, Workers R2 Storage Edit and D1 Edit.
- For a subdomain, add three more: Zone Read, DNS Read and Workers Routes Read.
- Under Account Resources, choose your company’s account. For a subdomain, under Zone Resources, include your domain.
- Click “Continue to summary”, then “Create Token”. Cloudflare shows the token only once, so copy it straight away.
- When your assistant asks for it, paste the token into the terminal yourself, not into the chat.
Open Cloudflare’s API Tokens page.
The technical brief says what each permission is used for. Once your Studio is running you can delete the token; updating or removing your Studio later needs a new one.
Check the plan, then create your Studio
Nothing is created until you say yes. Your assistant first runs the plan and shows it to you. “Will create” lists one Worker, one R2 bucket and one D1 database, plus your workers.dev name if it is new and your subdomain if you chose one. “Will not touch” lists your domains and DNS, your other Workers, buckets and databases.
- If the plan shows a problem, such as a name that is already in use, pick another name and run the plan again.
- When the plan looks right, tell your assistant to go ahead. If the deploy stops part-way, running the same command again continues without creating anything twice.
Save your Admin key
- When it is done, the deploy shows your Studio’s address and its Admin key, once. Keep the key somewhere safe, like your password manager. You sign in to your dashboard with it, and anyone who has it can use your Studio.
- It also writes a file called deployment.json in the cloudflare folder. Keep that file, because updating or removing your Studio later uses it.
Connect Maxisnap and try it
- Maxisnap for Windows: open Settings → Account → Maxisnap Studio setup wizard, click “Get started”, then “Next” until step 4, “Connect Maxisnap”. Paste your Studio’s address and key, click “Test connection”, then “Next”, then “Finish & Save” on the last page. The Admin key from setup works, and so does an upload code from People & access in your dashboard.
- Maxisnap for Mac: open Settings → Welcome & Help → Studio Setup Guide and choose “I already have a dashboard”. Paste your Studio’s address and key, click “Test Connection”, then “Next”, then “Finish & Save”.
Capture something and click “Upload” in the editor. On Windows, Ctrl+Alt+7 captures a region and uploads it straight away. The share link lands on your clipboard.
Maxisnap for Windows and Maxisnap for Mac send each upload to a Cloudflare Studio in one request, which it accepts up to 25 MB per file.
Next steps: add your team in the dashboard under People & access (everyone gets their own code and role), and change your logo or colours any time under Branding.
If something goes wrong
The subdomain is already in use
snaps.yourcompany.com is already in use (it has DNS records). Pick a name that isn’t used yet; Studio never changes existing DNS.
That name already points somewhere, so Studio leaves it alone. Pick a subdomain that nothing uses yet, such as studio or share.
A Worker route already covers the subdomain
The Worker route “*.yourcompany.com/*” on yourcompany.com already covers snaps.yourcompany.com, so Studio would not receive its traffic. Pick another name.
Another Worker in your account answers every subdomain that matches that route, so Studio would never see its own visitors. Pick a name outside the route, or ask the person who set up the route.
Studio cannot find your domain
That domain is not in this Cloudflare account.
The domain lives in another Cloudflare account, or the token cannot see it. Create the token in the account that holds your domain, with Zone Read, DNS Read and Workers Routes Read for that domain.
Your domain is marked “not active yet”
yourcompany.com is not active on Cloudflare yet, so snaps.yourcompany.com will not work until it is.
Cloudflare does not answer for the domain yet, usually because its nameservers still point at your old provider. Use the workers.dev address for now; you can add the subdomain later without losing anything.
The new subdomain does not open yet
Cloudflare can take a while to switch a new subdomain on. The workers.dev address works from the start, so use it until then.
Uploads fail on the subdomain, but the workers.dev address works
A Cloudflare security setting on that subdomain is stopping Maxisnap: Cloudflare Access (a sign-in page in front of the address), a WAF rule or Bot Fight Mode. Ask the person who looks after your Cloudflare to let the Studio subdomain through. The technical brief lists what to check.
The plan says it could not check the Worker routes
Studio could not check the Worker routes on yourcompany.com (the connection has no Workers Routes Read permission).
Add Workers Routes Read to the token. Without it, Studio cannot see whether another Worker already catches the new subdomain.
Storage is not turned on
R2 storage is not turned on for this Cloudflare account yet.
Turn R2 on in the Cloudflare dashboard, as in step 1, then ask your assistant to run the plan again.
The Studio name is already in use
A Worker named “snaps” already exists in this account. Pick another name; Studio never replaces someone else’s Worker.
Tell your assistant another name, such as snaps-yourcompany. If a storage or database name is taken, the deploy tool picks the next free one by itself.
Cloudflare refused a step
Cloudflare refused this step: the connection does not have permission for it. Reconnect Cloudflare and approve every permission Studio asks for.
The token is missing a permission. Create a new token with the permissions from step 5 and paste it into the terminal again when your assistant asks.
Setup stopped part-way
Ask your assistant to run the same deploy command again. It continues from where it stopped and does not create anything twice.
Your new address does not open yet
Studio did not come online in time (HTTP 404). Cloudflare can take a few minutes to publish a new address; try again shortly.
Everything is created; Cloudflare is still switching the address on. Wait a few minutes, then open the address again.
You lost your Admin key
Your assistant can set a new one. It runs this command from the cloudflare folder of your Studio download, with a Cloudflare token in the terminal. The command shows the new key once; then connect Maxisnap again with it.
node deploy/cli.mjs update --record deployment.json --yes --new-admin-key Large videos do not upload
Maxisnap for Windows and Maxisnap for Mac send each upload to a Cloudflare Studio in one request, which it accepts up to 25 MB per file.
Keep recordings under that size, or trim them before you upload.
Maxisnap says the key is not right
Copy the key again from where you saved it, without spaces before or after it. Check the address too: it is the one setup showed you, starting with https://.
Still need help?
Email us and a person will write back, usually within one business day. These details help us answer in one go:
- The setup option you chose and the step you are on.
- A screenshot of the screen, with any error message in full.
- Where your Studio is going: a new or existing Cloudflare account, or the name of your web hosting company.
- Your Maxisnap version: on Windows in Settings, then About; on a Mac under Maxisnap, then About Maxisnap.
Please don’t send your Admin key, a Cloudflare key or a password. We don’t need them to help you.