How to Share a Svelte Build with Clients

Sharing a Svelte build with clients should be a one-step process. In practice, most developers end up sending a new Vercel or Netlify preview URL every time they push a change — and clients end up with a browser full of tabs, none of which they are sure is current. Clowd gives you one permanent link per project that always points to the latest build.

This guide covers exactly how to do it with Clowd — no Git required, no CI/CD pipeline, no configuration files. Upload your build, get a permanent link, share it with anyone.

---

Why Most Hosting Tools Are Overkill for This

Vercel, Netlify, and GitHub Pages are excellent tools for production engineering workflows. But they come with a cost: you need a Git repository, a connected account, environment variable configuration, and a deployment pipeline just to put a site live. For sharing a Svelte build with clients for review, that overhead is unnecessary.

Vercel and Netlify generate a new URL on every deploy. If you share a preview link with a client or stakeholder, that link breaks the moment you push a new build. You end up resending links constantly and your audience has no idea which URL is current.

GitHub Pages requires a repository and Git knowledge. For non-technical users, designers, or anyone who just wants to put a site live quickly, this is a significant barrier. You should not need to understand branches and commits to host a static site.

Configuration files add friction. vercel.json, netlify.toml, _redirects — every platform has its own configuration format. For simple static sites, none of this should be necessary.

No file delivery alongside hosting. If you need to share a PDF, ZIP, or other asset alongside your hosted site, you need a separate tool. Clowd handles both from the same dashboard.

---

How Clowd Handles sharing a Svelte build with clients for review

Clowd takes a different approach. You upload your build folder as a ZIP — or paste HTML directly — and get a permanent link immediately. No Git, no configuration, no pipeline.

Permanent URL by default. Every site you host on Clowd gets a permanent link that never changes. When you upload a new build, the URL stays the same. Your audience always has the current version at the same address.

No login required to view. Anyone with the link can open your site instantly — no Clowd account required. This is essential for client previews, stakeholder reviews, and public-facing sites.

Supports any static framework. React, Next.js (static export), Svelte, SvelteKit, Astro, Vue, Nuxt, Vite, Gatsby, Remix (static), Angular, or plain HTML — if it builds to a static output, Clowd hosts it.

Three upload methods. Drop a ZIP of your build folder, upload individual HTML files, or paste HTML directly. Whatever your workflow, there is a path that fits.

Free custom domain. Map your own domain to any Clowd site — including on the free plan. Your site lives at yourname.com instead of a random hosting URL.

Version history. Every previous build is stored. Roll back to any prior version instantly — no redeployment needed.

---

Step-by-Step: Hosting Svelte on Clowd

Step 1: Build your Svelte project. Run your build command to generate the static output. For most frameworks this produces a dist/, build/, or out/ folder containing your HTML, CSS, and JS files.

Step 2: ZIP the output folder. Compress your build output into a single ZIP file. On macOS: right-click the folder and select “Compress”. On Windows: right-click and select “Send to > Compressed folder”.

Step 3: Upload to Clowd. Sign in to clowd.host, create a new site, and drop your ZIP file. Clowd extracts it and serves it immediately. You get a permanent link within seconds.

Step 4: Share the link. Copy the permanent link and share it with whoever needs it — clients, stakeholders, reviewers, or the public. They open it in any browser, no account required.

Step 5: Update without changing the link. When you have a new build, upload the new ZIP to the same Clowd site. The URL stays the same. Everyone who has the link automatically sees the updated version.

Step 6: Add your custom domain (optional). In your Clowd dashboard, go to domain settings and add your custom domain. Point your DNS to Clowd and your site is live at your own URL — free on the free plan.

---

What You Can Host on Clowd

Clowd supports any static site output. Here is what that covers in practice:

React apps built with Create React App, Vite, or custom webpack configs. Run npm run build and upload the build/ folder.

Next.js static exports using next export or output: export in next.config.js. Upload the out/ folder.

Svelte and SvelteKit with the static adapter. Run npm run build and upload the build/ folder.

Astro sites with output: static. Run npm run build and upload the dist/ folder.

Vue and Nuxt with static generation. Run npm run generate and upload the dist/ folder.

Vite projects of any kind. Run npm run build and upload the dist/ folder.

Gatsby sites. Run gatsby build and upload the public/ folder.

Plain HTML. Upload a single HTML file, a folder of HTML files, or paste HTML directly into the editor.

Angular apps with ng build --configuration production. Upload the dist/project-name/ folder.

---

Clowd vs Other Hosting Options

Feature	Clowd	Vercel	Netlify	GitHub Pages
Permanent URL across deploys	Yes	No	No	Yes
No Git required	Yes	No	No	No
No login to view	Yes	Yes	Yes	Yes
Custom domain free	Yes	Yes	Yes	Yes
File delivery alongside hosting	Yes	No	No	No
Version history with rollback	Yes	Yes	Yes	Via Git
Upload ZIP directly	Yes	No	Yes	No
Paste HTML directly	Yes	No	No	No
Analytics built in	Yes	Paid	Paid	No

---

Common Mistakes When Hosting Static Sites

Uploading the source folder instead of the build output. Always upload the compiled output — dist/, build/, out/, or public/ — not your src/ folder. The build output contains the optimised HTML, CSS, and JS that browsers can render directly.

Forgetting to configure your router for client-side routing. If your React or Vue app uses client-side routing, make sure your build is configured to serve index.html for all routes. Clowd handles this automatically for single-page apps.

Using a new deployment for every update instead of updating in place. With Clowd, you upload to the same site and the URL stays the same. Do not create a new site for every build — update the existing one.

Not adding a custom domain. A random hosting URL looks unprofessional when sharing with clients or publishing publicly. Clowd gives you a free custom domain — use it.

Sharing preview links that expire. Vercel and Netlify preview URLs are tied to specific deployments and can become stale. With Clowd, the link is always the current version.

---

---

Frequently Asked Questions

How do I share a Svelte build with clients without a new URL every time?

Upload your Svelte build to Clowd. You get a permanent link. Every time you have a new build, upload it to the same Clowd site — the URL stays the same and clients always see the latest version.

Do clients need to install anything to view a Svelte build?

No. Anyone with the Clowd link opens your Svelte site in any browser — no account, no app, no friction.

Can I share multiple builds of the same Svelte project?

Yes. Create one Clowd site per project. Each site has its own permanent link. Update each one independently as your builds evolve.

Is there a file size limit for Svelte build uploads?

Clowd supports uploads up to 120 GB, so even large Svelte builds with many assets are no problem.

Can I roll back to a previous Svelte build?

Yes. Clowd stores every version of every site. Roll back to any prior build instantly from your dashboard — no redeployment required.

---

Get Started

Sharing your Svelte build with clients is straightforward with Clowd.

1. Build your Svelte project and ZIP the output folder
2. Upload to Clowd — free, no credit card
3. Copy the permanent link and share it
4. Update anytime — the link stays the same

Host your Svelte site on Clowd for free