Host what Cursor built, without setting up a deploy
The agent finished, the folder's on your disk, and the last mile is a deployment pipeline you didn't want. Drop the folder in instead.
Drop your Cursor 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 the last step is the slow one
Cursor is very good at going from a prompt to a working folder on your machine. What it leaves you with is a local project and the assumption that you know where it's going next. For a real application that's fine — you have a pipeline. For a landing page, a demo, a prototype you want a colleague to look at in the next ten minutes, standing up a deployment is out of all proportion to the task.
What Cursor gives you
- A project folder on your own disk, built by the agent
- Static sites, landing pages and prototypes ready to build
- Whatever framework you asked for, with a real build output
localhost isn't shareable
The dev server proves it works to you. Sending someone a screen recording of your own browser is not the same as sending them the thing.
Deploy setup outweighs the task
Repository, provider, build settings, environment variables — a lot of ceremony for a page that might live for a week.
Prototypes clutter real infrastructure
Throwaway experiments end up in the same account as production, and nobody ever cleans them up.
Putting Cursor output online
- 1
Build it
Run the project's build — npm run build for most setups — and find the output folder, usually dist or build.
- 2
Drop the folder in
Drag the output folder into the box above. It needs an index.html at its root, which every standard build produces.
- 3
Name it and share
Pick an address and publish. The link works immediately, from any machine, with nothing installed.
Worth knowing
- Publish the build output rather than the source — node_modules alone will blow past the size limit.
- Set the base path to / before building so assets resolve from the site root.
- Plain HTML with no build step? Drop the folder as-is; there's nothing to compile.
- Add a 404.html matching your index for client-side routing, so deep links work.
- Use one address per prototype and delete them when you're done — it takes a click.
Questions
- Do I need a repository?
- No. There's no Git integration to configure and nothing to connect — you drop a folder and it's online.
- Can I host a Next.js app Cursor built?
- Only if it's statically exported. A Next app using server components or API routes needs a Node server, which static hosting can't provide.
- What about an API key in the code?
- Anything in a static file is readable by anyone who opens the page. Treat published front-end code as public and keep secrets on a server.
- How do I update it?
- Build again and publish to the same address. Previous versions are kept, so you can roll back if a build goes wrong.
- Is it really free?
- Yes. You make an account when you publish, and hosting itself costs nothing.
Try it with what Cursor just made you
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 artifacts from other tools
Hosting guides by file type
Everything gets its own address on 99helpers.site — see AI artifact hosting for every tool or free file hosting for any file type.