Where can I publish something I vibe-coded?

"Vibe-coding" means describing what you want to an AI assistant and shaping the result through conversation instead of writing every line yourself. The building part keeps getting easier. The publishing part — getting a real URL someone else can open — is where people still get stuck. This guide maps the publishing options to the kind of thing you actually made.

What does a vibe-coded project actually produce?

Before picking a platform, look at what came out of the session. AI assistants tend to produce one of two shapes. The first is a single self-contained file: one HTML document with the CSS in a style tag and the JavaScript in a script tag. Claude artifacts, ChatGPT canvas output, and most "make me a game" prompts land here. The second is a multi-file project: a folder with separate components, a package.json, and maybe a backend — what you tend to get from Cursor, Bolt, v0, or Lovable when you build a full app. The right publishing tool depends entirely on which shape you have.

Where do I publish a single-file HTML project?

If your project is one HTML file — a game, an animation, a physics toy, a data visualization — you do not need a build pipeline or a hosting account. ArcadeLab is built for exactly this case: paste the file at arcadelab.ai/publish and you get a permanent URL like arcadelab.ai/play/your-project. No signup, no email, no credit card. If the file uses a library — Phaser, p5.js, Three.js, D3, GSAP, Tone, Pixi, or Matter — you list it in a short header comment and ArcadeLab injects it from a CDN, so you do not even need the script tag.

Other single-file options exist. CodePen is good for showing source code and quick edits, but it frames your work inside its own editor chrome. GitHub Pages works if you already keep a repo and do not mind the git workflow. The difference is friction: ArcadeLab optimizes for the shortest path from "the file is done" to "here is a link." See where to publish a single-file HTML game for a closer look at that case.

Where do I publish a multi-file app?

If you vibe-coded a full application — multiple routes, a build step, a database, authentication — you need a real host. Vercel and Netlify deploy from a git repo or a CLI and run the build for you. Replit hosts what you build inside its own editor. Cloudflare Pages and Render cover similar ground. These are the right tools when a project genuinely has moving parts. They cost more setup time, and that is the correct trade for an app that needs it.

The common mistake is reaching for one of these when the project is actually just one HTML file. A build pipeline for a static single-file game is overhead with no payoff.

How do I pick the right platform?

• One HTML file, no backend — ArcadeLab (paste, no signup)
• One HTML file, you want inline source editing — CodePen
• Static multi-file site — Netlify, Vercel, GitHub Pages, Cloudflare Pages
• Full app with a backend or database — Vercel, Netlify, Replit, Render
• You are still iterating inside an IDE — Replit (build and host together)

What about the file an AI assistant just handed me?

If your AI assistant produced a code block or an artifact, copy the entire thing — from the first character to the last. For a single-file project that is the whole HTML document. Paste it into the publishing tool that matches the shape above. If the assistant split the project across several files, either keep it in a folder for a git-based host or ask the assistant to "combine this into a single self-contained HTML file." Many games and visualizations flatten cleanly, and once they do, ArcadeLab handles them.

Built a single-file project? Publish it at arcadelab.ai/publish.