There are two different problems hiding under "I need a one-page site", and most tools only solve the first. Making the page is one problem; putting it somewhere is the other. If you're still searching, you've already solved the first — the page exists as an HTML file you wrote, exported from a design tool, or got out of an AI — and what's left is somewhere to put it. That's a hosting job, and it shouldn't cost you a new account, a canvas, or a rebuild. Drop the file and get a link in seconds. Your page renders exactly as built — your fonts, your layout, your code — at an unguessable URL that stays off search until you decide otherwise.
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.
Bring the file you already have — a single self-contained HTML page, or a ZIP of the whole thing (HTML, CSS, JS, images). However you made it, drop it in. There's no repo to initialise, no build command, and no canvas to learn; miinideck serves your markup as-is.
Get a private, unguessable link in seconds. It carries a no-index tag, so the page won't surface in search and only people you send the link to can open it — a clean way to put a one-pager in front of someone before, or instead of, going fully public.
Change the page by editing the file you already own — in your editor or by re-prompting the AI that made it — then drop the new version. The link stays the same, so anyone holding it lands on the current page. No builder project to keep in sync, nothing to rebuild block by block. Add a password or an expiry when the page is sensitive; on paid tiers the footer comes off so it reads as purely yours.
Match the tool to which half of the job you still have. If the page doesn't exist yet, you want a builder or an AI to make it. If it does exist as a file, everything a builder offers is work you've already done, and what you need is a host that takes the file as-is. The lightest version of that is drag the file, get a link: no repo to initialise, no build command, no DNS to point, no deploy to remember how to re-run six months later. Heavier static hosts do this too and are the right call once you have a build pipeline, several environments, or a team — this is the shape for one page and one person.
Yes — if you already have the page as a file. A builder is a tool for making the HTML when you have nothing; once the HTML exists — hand-written, exported from a design tool, or generated by an AI — there's nothing left for the builder to do. Drop the HTML file or a ZIP of the build, and it goes live behind a private link in seconds. No canvas, no blocks, no rebuild — your page renders exactly as you made it.
You can — but a builder wants you to recreate your page inside its editor, then it owns the project. If the page already exists as a file, that's hours spent arriving back where you started, and every later edit has to happen in the builder rather than in your own code. Here the file stays the source of truth: you edit it where you made it, drop the new version, and the link updates. The trade-off is that miinideck serves a front end — it doesn't give you a builder's form handlers or CMS, so for those you'd reach for a real backend.
Be honest with yourself about what the form needs. miinideck serves your page's front end exactly as built, so the form shows and any client-side script runs. But the moment a submission has to be stored, emailed, or written to a database, that needs a real backend — and for that, Vercel or Netlify are the right tools, with serverless functions behind your form. A common pattern: develop and run the live form there, and use miinideck to put a private one-pager in front of specific people before it's public.
Publishing puts your page on the open web at a findable address for anyone to reach. A private link serves the same page at an unguessable, no-indexed URL — visible only to the people you send it to. It's the right fit when you want to show a one-pager to a client, a few testers, or a stakeholder without it being discoverable. When the page is truly ready for the world, you publish it wherever it's meant to live.
Without signing in you can drop up to 3 MB and the link self-destructs after 7 days — enough to put a one-pager in front of someone fast. A free account raises that to 10 MB with one always-on link, and paid tiers go to 25 MB (Solo) or 50 MB (Studio), remove the footer, never expire your links, and add detailed analytics; a custom domain comes with Studio.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.