A Replit preview is tied to the repl and your account, and it sleeps when the repl goes idle. So the person you sent it to clicks a replit.dev URL, waits out a cold start while the repl wakes, and only then sees the page — if the repl is awake at all. When you just need someone to look at the front end, export the static build and drop it in. You get a private, unguessable link in seconds: no repl has to stay running, it opens with no account, and it stays off search.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML, ZIP, PDF, PNG or JPEG file, or click to choose.
One file, or a ZIP bundle. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
Build the static version of your Replit app — a single self-contained HTML file, or your build output (the dist or build folder) zipped — and drop it in. It runs in the browser with its scripts, styles, and assets intact, behind a private link in seconds. Nothing has to stay awake for it to load.
Send the unguessable link to a client, a teammate, or a reviewer. There's no cold start and no repl to wake, so it opens the instant they click — no Replit account, no replit.dev URL, no spin-up spinner. It's no-indexed, so a work-in-progress reaches your people, not search.
Keep iterating in Replit and re-export when you want to update the share — replace the file and the link stays the same, so whoever you sent it to always opens your latest build.
Export the static build of your app and drop it into miinideck. You get a private, unguessable link in seconds that runs in any browser on its own — no replit.dev URL, no repl that has to stay awake, and no Replit account needed on the viewer's end.
A Replit preview runs inside your repl, so the repl spins down when it's idle and the next visitor triggers a cold start — they wait while it boots before the page appears. A static export here has no repl behind it: it's served as plain files from your link, so it opens immediately every time, even months later.
miinideck serves the static front end — what runs in the browser. Replit runs a full server, so if your app needs that live backend, a database, or API routes, keep that part on a host built for servers like Vercel or Netlify, or keep the repl deployed. Use miinideck for the private share of the built, browser-ready page.
No. The link is private, unguessable, and no-indexed by default, so a draft only reaches the people you send it to and won't surface in search. You can add a password free on every plan.
Yes. Turn on Review and anyone with the link pins a note to the exact element — no account required — and you resolve each one. On Studio you can export the whole thread as a prompt to take back into Replit's AI or another tool.
Watch what the running app talks to. If every piece of data is baked into the page or fetched from an external API the browser reaches directly, it's static and the export works. If the app reads or writes a database inside the repl, runs Express or Flask routes, handles auth server-side, or reads Replit secrets at runtime, it has a backend — a static export will load but break on those actions. That slice needs a real server, and Vercel or Netlify are the honest call for it.
For a Vite, React, Astro, or plain-HTML project, run the build command in the Replit shell, open the output folder — usually dist or build — and download it as a zip. Those files need no Node, no database, and no running container; they render anywhere a browser can open them. Drop that zip in and the whole build serves from one private link.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.