Host a web project in seconds
Put a build output, prototype or side project online at its own address — for showing work in progress without setting up infrastructure.
Drop your build folder here
Any other file works too — up to 25.0 MB, or 100.0 MB for a whole site
Free to use, live at your-name.99helpers.site in about ten seconds.
Why this is harder than it should be
Not every project deserves infrastructure. A prototype you want feedback on, a side project you're not sure about, a build you need to show someone before the meeting — all of these need a URL and none of them need a deploy pipeline. Run your build, upload the output folder, share the link.
Setting up hosting outlasts the prototype
Repository, CI configuration, environment variables and a deploy target — often more work than the prototype itself, and most prototypes don't survive the week.
localhost isn't shareable
Tunnelling tools work while your machine is on and you're paying attention. That's fine for a demo and useless for asynchronous feedback.
Screenshots lose the point
If the thing you built is interactive, a screenshot shows none of what makes it worth looking at.
How it works
- 1
Build it locally
Run your usual build and find the output — dist, build, out or public, depending on your tooling. That folder is a finished static site.
- 2
Upload the output folder
Drop the whole folder in. The structure is preserved, so your assets, chunks and routes resolve exactly as they do locally.
- 3
Share and iterate
Publish updates to the same address as the project moves, so the link you gave people stays current.
Worth knowing
- Single-page apps that rely on client-side routing need care: deep links only work if the framework produces real HTML files per route, or you add a 404.html that loads the app.
- Anything requiring a backend won't work — this is static hosting, so APIs need to live elsewhere.
- Check your build doesn't reference absolute paths that assume a domain root, if you're publishing under a name you'll change later.
- Source maps expose your original code — decide deliberately whether to include them.
- Environment values baked into a client build are public. Never ship secrets in one.
Questions
- Can I host a React or Vue app?
- Yes, once it's built. Upload the production build output — the static HTML, JavaScript and CSS your bundler produces. The framework's development server isn't involved.
- Will client-side routing work?
- Direct navigation works. Deep links depend on your setup: if the build produces a real HTML file per route it works fine, otherwise add a 404.html that loads your app so unmatched paths still boot it.
- Can it talk to my API?
- Your frontend can call any API the browser can reach, subject to that API's CORS policy. What can't run here is the API itself — there's no server-side execution.
- Is it suitable for a production app?
- For a static frontend, it's fast and served from the edge. But there's no custom domain yet and no server-side capability, so it suits prototypes, demos and side projects better than a production product.
Try it with what you have right now
Drop it in at the top of this page and see the link for yourself. You only make an account once it's ready to go live.
Hosting guides by file type
Other things people host
Everything gets its own address on 99helpers.site — see everything you can host or free file hosting for any file type.