Enlarged screenshot

How To Upload A ZIP Project To Cloud From Claude / ChatGPT

Takes a ZIP of any website, publishes it to your own cloud storage, and gives you back the live URLs. The ZIP goes straight from the chat to your cloud — nothing is kept on YACSS.

Before you start:
  • YACSS connected to Claude or ChatGPT (see the ChatGPT or Claude MCP connection tutorials).
  • At least one cloud account connected in YACSS, under Clouds Connectivity.
  • Your website as a ZIP file, up to 500MB. This is your own HTML project, not a YACSS build.
1

Pick The Client

If you manage sites for several clients, start here so you only see that client's clouds and don't publish to the wrong account.

List all my Yacss clients.
List of YACSS clients returned
2

See That Client's Cloud Accounts

Now ask for the clouds belonging to that client. Each one comes back with the provider, the account name, and the bucket already set on it, if any.

List my cloud accounts for the client Acme Roofing.

From here on, just refer to a cloud by its provider and account name, for example "the aws account Acme AWS." Claude matches that to the right account for you.

Cloud accounts for a client listed by provider and account name
3

Check The Bucket Exists

A ZIP can only be published into a bucket that already exists on that cloud. If the table above shows no bucket, or you want a different one, check what's actually there.

Can u check 'acme-roofing' bucket on my aws account Acme CF.

You'll get the real bucket names on that account. Two outcomes:

  • The bucket you want is in the list. Good, use that name when you publish.
  • It isn't there. Create it — see the next section.
Bucket check showing the bucket does not exist yet
4

Create The Bucket If It's Missing

Ask for it by name on that account. If a bucket with that name already exists and is yours, this simply confirms it rather than failing.

Create the bucket acme-roofing-site on my aws account Acme CF.

Two things worth knowing:

  • Vercel, Netlify and Render don't use buckets — they deploy from a GitHub repo. For those, the "bucket" is the repository in owner/repo form, for example acmedev/acme-roofing. Ask for the buckets on that account to see your repos.
  • Bunny needs two things, a storage zone and a pullzone. Creating the bucket makes the storage zone only, so ask for a pullzone as well or the site won't be reachable.
Bucket created and ready to use
5

Attach Your ZIP And Send It

Now that you know where the site is going, send the file. Attach the ZIP to the chat the same way you'd attach any file, then ask Claude to send it to YACSS. Claude requests a private, short-lived upload link and puts your file on it directly.

Here's my site as a ZIP. Send it to acme-roofing-site-1 in aws ready to publish.

Claude will confirm the file is uploaded before going any further.

If Claude built the site for you in this same chat, there's no attachment needed. Just say:

Zip up the site you just built and send it to YACSS.
Why this step comes now: the upload link is short-lived on purpose. Sorting out the client, account and bucket first means the ZIP goes up right before it's needed, instead of sitting around waiting.
ZIP file attached and sent to YACSS, publishing started
6

Get Your Live URLs

You'll get one line per cloud with its live URL and one of three results:

  • Published — the files are up and the URL loads.
  • Not publicly readable — the files uploaded fine, but the URL doesn't open yet. Almost always the bucket isn't set to public on your cloud. Make it public-read, then open the URL again.
  • Failed — comes with a plain reason.
Show me the live URLs for that upload.
Live URLs and full page list returned after upload
Done! Your ZIP project is published and live.

If Something Goes Wrong

What you seeWhat to do
Claude says it can't send the fileAsk it to request a new upload slot and send the ZIP again.
"No file uploaded to that slot yet"The link expired or the file never arrived. Ask for a fresh slot and attach the ZIP again.
The upload link expired while you were choosing bucketsSort out the account and bucket first, then send the ZIP, as in the order above. Ask for a new slot and resend.
"Zip is too large"The limit is 500MB. Remove unused images or videos and zip it again.
The size shown isn't your fileThe wrong attachment was sent. Say which file you mean, and check the size before publishing.
"bucket is required"Tell it which bucket to use, for example bucket acme-roofing-site. It won't guess.
"The bucket does not exist"Create it on that account first, see the section above.
The site uploaded but the URL won't openThe bucket isn't public. Set it to public-read on your cloud, then reload the URL.
The homepage loads but images are missingThe ZIP's folder structure is off. Zip the site's files directly, not a folder containing them.
Monthly upload limit reachedEach cloud counts as one upload. Upgrade under My Subscription or wait for your allowance to renew.
Vercel, Netlify or Render gives a broken URLThe bucket must be the GitHub repo in owner/repo form, not a project name.
A Bunny site won't loadThe storage zone exists but there's no pullzone. Ask for a pullzone on that storage zone.
Upload stuck showing generatingRetry the upload. If it stalled it will now report an error instead of hanging.
Shopping Cart
Scroll to Top