Host a web app in seconds
Put a client-side app online at its own address — a tool, a calculator, a game, anything that runs entirely in the browser.
Drop your app build 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
A surprising number of genuinely useful apps need no server at all. A unit converter, a mortgage calculator, a colour picker, a game, a data visualiser reading from a file you ship alongside it — all of it can run entirely in the browser. Those apps need hosting, and almost every option is priced and shaped for something far more complicated.
Paying for a server that does nothing
An app that runs in the browser doesn't need compute, yet the obvious hosting options all assume it does and price accordingly.
Deployment complexity you don't need
Containers, environment configuration and CI for a bundle of static files is machinery in search of a problem.
Nowhere to put a small tool
The useful little utilities people build for themselves usually stay on their own machine, because publishing one feels disproportionate to what it is.
How it works
- 1
Build for production
Whatever your tooling produces — a bundle from Vite, a compiled WebAssembly module and its loader, or a hand-written page — the output is what gets uploaded.
- 2
Upload the whole output folder
Everything together, so relative paths, chunks and assets resolve. Files are served with the correct content types, including application/wasm for WebAssembly.
- 3
Publish and share
The app is live at its address and served from the edge, so it loads quickly wherever someone opens it.
Worth knowing
- WebAssembly modules are served as application/wasm, which is what instantiateStreaming requires — a common failure point on other static hosts.
- Data your app needs can be uploaded alongside it as JSON or CSV, and fetched from a relative path with no CORS issues.
- Browser storage works normally, so an app can remember state per visitor.
- There's no backend, so anything needing a database, authentication or server-side processing has to live elsewhere.
- Anything in your bundle is public — never include API keys or secrets in a client build.
Questions
- What kind of apps work here?
- Anything that runs entirely in the browser: calculators, converters, games, visualisers, editors, WebAssembly applications. Anything needing a server, a database or authentication does not.
- Does WebAssembly work?
- Yes, and modules are served with the correct application/wasm content type, so streaming instantiation works rather than falling back to the slower path. Upload the .wasm alongside your HTML and JavaScript.
- Can my app store data?
- In the visitor's browser, yes — localStorage and IndexedDB work normally. Data shared between users would need a backend, which this doesn't provide.
- Can it call an external API?
- Yes, subject to that API's CORS policy — the same constraint as on any other host. Just don't put the API key in your client code, since it's public.
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.