How to Share a React App with a Client (No Vercel, No Git)

The Problem with Sharing React Apps

You’ve built a React prototype. The client wants to see it. Your options:

Option A: Share localhost via ngrok Unreliable. Requires your computer to be on. URL changes every session. Looks unprofessional.

Option B: Deploy to Vercel Requires a Git repository. Generates a new URL on every deploy. Client gets confused which link is current. Overkill for a preview.

Option C: Deploy to Netlify Same problems as Vercel. New URL on every deploy.

Option D: Send screenshots Not interactive. Client can’t actually use the app.

None of these are the right answer for sharing a React app with a client in a professional, repeatable way.

The right answer: build → zip → upload → permanent link. Done in 60 seconds.

---

The 60-Second Method

Step 1: Build your React app

# Create React App
npm run build
# Output: build/

# Vite
npm run build
# Output: dist/

# Next.js (add output: 'export' to next.config.js first)
npm run build
# Output: out/

Step 2: Zip the output folder

Mac: Right-click the build (or dist) folder → Compress Windows: Right-click → Send to → Compressed folder

Step 3: Upload to Clowd

1. Go to clowd.host
2. New delivery → Static Site
3. Upload your zip
4. Live in seconds

Step 4: Share the link

Hi [Client],

Your React prototype is live here: [Clowd link]

No login needed — just open the link. Leave comments directly on the
page if you have feedback. I'll update the same link as we iterate.

That’s it. When you have updates, upload a new zip to the same delivery. The URL never changes.

---

Why This Is Better Than Vercel for Client Previews

	Vercel	Clowd
Git required	✅	❌
New URL on every deploy	✅	❌
Permanent URL	❌ (production only)	✅
Client comments	❌	✅
Version history	❌	✅
Custom domain (free)	❌	✅
Setup time	10-30 min	60 seconds

Vercel is the right tool for production deployments with CI/CD. Clowd is the right tool for client previews where you need a permanent, updatable link.

---

Handling Common React Scenarios

React Router (client-side routing)

React apps with React Router need a server that redirects all routes to index.html. Clowd handles this automatically — all routes in your React app will work correctly.

Environment variables

Static React builds bake environment variables into the bundle at build time. Make sure your .env file has the correct values before building. Don’t include sensitive keys in a client preview build.

API calls

If your React app makes API calls, the API needs to be accessible from the client’s browser. For client previews, consider:

• Using mock data for the preview
• Pointing to a staging API
• Using a CORS-enabled API endpoint

Large builds

If your build folder is large (> 100 MB), consider:

• Running npm run build with production optimisations
• Removing source maps (GENERATE_SOURCEMAP=false npm run build for CRA)
• Compressing images before building

---

Practical Example: The Agency Developer

Tom is a developer at a digital agency. He builds React dashboards for clients.

The old workflow:

1. Push to GitHub
2. Connect Vercel
3. Configure environment variables
4. Wait for deployment
5. Send client the Vercel URL
6. Push a fix → new Vercel preview URL
7. Send client the new URL
8. Client asks “which link is the right one?”

The new workflow:

1. npm run build
2. Zip dist/
3. Upload to Clowd
4. Send client one link
5. Push a fix → upload new zip to same Clowd delivery
6. Ping client: “Updated — same link”

Total links sent to client: 1. Total “which link?” emails: 0.

---

Best Practices

• Test the build locally first — open index.html in a browser before uploading
• Use a descriptive delivery name — “ClientName — Dashboard — Preview” in your Clowd dashboard
• Enable client comments — keeps feedback out of email
• Set a custom domain — preview.youragency.com looks more professional
• Keep version history — label each upload (“v1 — Initial”, “v2 — After Feedback”)
• Don’t include source maps — reduces build size and doesn’t expose your source code

---

Question-Based Insights

Why does Vercel create a new URL on every deploy?

Vercel’s preview deployment system is designed for CI/CD workflows where every branch and commit gets its own URL for internal review. This is useful for development teams but creates confusion for client delivery — the client doesn’t know which URL is “current.” Clowd’s permanent URL solves this by design.

Can I share a React app with a client who isn’t technical?

Yes. A static React build runs in any browser — your client just opens the link. They don’t need to know what React is, install Node.js, or understand anything about how the app was built. It just works.

---

How Clowd Helps

• 60-second deployment — build, zip, upload, share
• Permanent URL — one link per project, updates in place
• No Git required — no repository, no CI/CD, no configuration
• Client comments — feedback tied to specific versions
• Version history — every build saved, rollback with one click
• Custom domains — free plan includes 1 custom domain

Share your React app with a client in 60 seconds →