Codex doesn't hand you a single file — it hands you a build: an index page, scripts, styles, maybe a few folders. Wiring that up to a deploy just to let one person look is more setup than the moment needs. Zip the folder and drop it in instead. You get one private link in seconds that serves the whole build with its files intact — browsable in any browser, open only to the people you send the link to, and kept out of search.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML file or ZIP bundle, or click to choose.
Single file or ZIP. 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.
Zip the folder Codex generated — index.html at the root, plus its scripts, styles, and asset folders — and drop the whole thing in. It unpacks and serves the files with their relative paths intact, so the multi-file build runs exactly as it does locally, behind one private link.
Send that single link to whoever needs to see it. They open the whole app in the browser — no account, no install, nothing to set up. The URL is unguessable and no-indexed, so an in-progress build never lands on the open web or in search.
Keep the same link as you iterate: re-run Codex, re-zip, replace the file from your dashboard, and the URL stays put — every reviewer always lands on your newest build instead of a stale copy.
Zip the whole folder — index.html at the root plus every script, stylesheet, and asset folder — and drop the zip in. miinideck unpacks it and serves the files with their relative paths intact, so the full multi-file build runs from one private link, with no deploy or hosting config to wire up.
Yes. As long as index.html sits at the root of the zip and your files reference each other by relative path the way they do locally, everything resolves — scripts load, styles apply, sub-pages open. The build behaves the same as it does on your machine, just behind a private link.
miinideck serves the front-end — the part of the build that runs in the browser. If your Codex app needs live server logic, a database, or auth, deploy that part on Vercel or Netlify, which are built for it, and use miinideck for the private share of the static build. For a front-end-only app, the zip is all you need.
Neither. The link is private, unguessable, and no-indexed by default, so the build reaches only the people you send the link to — not the open web or search results. You decide who gets it; you can add a password or an expiry when a build is sensitive.
Yes. With Review on — free on every plan — anyone with the link pins a note to the exact element, no account needed, and you resolve each one. On Studio you can export the whole thread as a prompt to paste straight back into Codex for the next pass.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.