You ran a SvelteKit build and now you just want one person to see it — not to wire an adapter to a host and babysit a deploy. Swap in adapter-static, set prerender = true, and build; SvelteKit writes a folder of plain HTML, CSS, and hashed JS. Zip that folder, drop it in, and you get a private, unguessable link that runs the whole app in the browser — no pipeline, no dashboard, and no account for whoever opens it. Send it for a fast look or a client review while the build is still pre-launch.
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.
Set your adapter to adapter-static in svelte.config.js, turn on prerender, and run the build. SvelteKit renders your routes into a folder of static files (commonly build/), assets hashed and linked. Zip that folder and drop it in — miinideck unpacks it and serves the app behind one private link, routes and assets intact.
Send the link. It's unguessable and no-indexed, so a pre-release Svelte app never surfaces in search and only the people you hand the URL to can open it. It loads live on any device, with nothing to install.
Add a password or an expiry for the review window. Rebuild and replace the ZIP as you iterate — the link stays the same, so reviewers always land on your latest export instead of chasing a new URL each round.
Install adapter-static, set it in svelte.config.js, and add export const prerender = true to your root layout. Run the build and SvelteKit renders your routes into a folder of plain HTML, CSS, and JS (usually build/). Zip that folder and drop it in — it runs in the browser with no Node server behind it. This covers any SvelteKit app whose pages can be prerendered.
Then part of it needs a real server, and a static export won't run that part. miinideck serves the static, front-end slice — the prerendered pages and client-side code. For the server side (SSR, form actions, a database, API endpoints), deploy on a platform built for it like Vercel or Netlify, then point your front end at that backend. If your app is fully prerenderable, the static export is all you need here.
Yes, for a prerendered build. Open the entry page and Svelte's client-side navigation handles route changes inside the app. Deep links to dynamic routes are the exception: an adapter-static fallback page (like 200.html) is not served here, so a path with no matching file returns a not-found rather than loading the app. Share the entry page and let navigation happen inside the app, or switch to hash-based routing if the exact URL has to survive a reload. Assets resolve because the whole build is served together.
Yes. Every link is unguessable and no-indexed, so a pre-launch build stays off search and only people you send it to can reach it. Add a password — free on every plan — so even someone holding the link needs the passphrase to open it.
Yes. Turn on Review and anyone with the link can pin a comment to the exact element they mean — no account needed — and you resolve each one as you go. Review is free to use on every plan; exporting the whole thread as a prompt for Claude or Codex is a Studio feature.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.