Upload your site's files

You can put a site online by uploading its folder, or a .zip of it, in the console. We check the files in your browser first, so any problem shows up before anything is sent.

Upload a new site

1. In the console at https://console.cloudzyro.com, open Sites & Apps and click New site.

2. Choose your site’s address and click Continue.

3. Under Upload files, drop your site’s folder onto the page, or click Choose a folder or Choose a .zip file. On a phone or tablet, choose a .zip file.

4. Check the summary. It says what we found (for example, “We found a Vite app. We’ll build it and serve the files it makes.”), how many files there are and their size.

5. Optionally, fill in What changed? so you can recognise this version later.

6. Click Deploy site. Keep the page open until your files are uploaded. After that, you can follow the deploy or leave it to finish.

Upload a new version

Open your site, then click Upload a new version on the Overview tab. Upload the folder again with your changes and click Deploy new version. Before you deploy, the summary compares your files with the live version, for example “12 files changed, 3 added”, and lists any files you’ve removed.

Your current version stays online until the new one is ready.

What to upload

Upload the folder that has an index.html or a package.json at the top level:

• A static site with an index.html goes online as it is.
• A site with a build step (Vite, React, Astro) needs a build script in package.json. We build it and serve the files it makes.
• A Node app, including Next.js, needs a start script in package.json. We build it and run it on Node 22.

If you upload a folder that holds everything inside one subfolder, we use that subfolder automatically. If there’s no index.html at the top level but there’s one in a folder like dist or build, we offer a button to use that folder instead.

Limits on each plan

Plan	Size of a version	Files in a version
Launch	100 MB	20,000
Boost	1 GB	50,000

If your files are over the limit, we tell you which are the largest. Large images and videos load faster from storage like Supabase Storage or S3 than from your site’s files.

Files we leave out

Some files are never needed online, so we leave them out and tell you we did:

• Folders of dependencies, version control and caches, such as node_modules, .git, .next, .nuxt, .svelte-kit, .vercel, .netlify, .turbo, .cache, .astro, coverage, __pycache__, .venv, .idea and .vscode.
• Build output folders (dist, build, out) when your site has a package.json, because we build it ourselves.
• System files like .DS_Store, Thumbs.db and desktop.ini.
• .env files, such as .env and .env.local. Example files like .env.example are kept.

Secrets in your files

We never upload your .env file. If we find one, the summary says “We left out .env so your secrets stay private.” Click Add them now to paste each value: they’re saved privately as your site’s environment variables and can’t be shown again.

We also look through your files for keys left in your code, such as Stripe secret keys, GitHub tokens, AWS keys, private keys, Supabase service role keys or database passwords in connection strings. If we spot one, you’ll see a warning naming the file. Keys meant to be public, like a Supabase anon key, aren’t flagged.

Caution

On a static site, or a site with a build step, anyone who visits your site can download its files. If we warn about a key in one of them, remove the key and keep it somewhere private. For a Node app, keys are safer in environment variables than in your files.

Other ways to deploy

• Deploy with your AI tool: ask it to put the site online.
• Deploy from Git: every push to your branch goes online by itself.

While a site is connected to a repository, uploads are turned off for it. Disconnect the repository in the site’s Settings to upload again.