How to make a Vibecade game
Any game that runs in a web browser can go on Vibecade, whether you built it with an AI assistant, an engine or by hand. Here's what to upload and what works.
1. Pick your upload
- One-file game (common for games made with ChatGPT, Claude and similar tools): upload the
.htmlfile as it is. Any name works; we store it asindex.html. - Game with several files (images, sounds, scripts): zip the folder.
index.htmlmust be at the top of the zip, or inside a single folder at the top. Use relative paths like./img/ship.png, not/img/ship.png.
2. Limits
| Game file | .zip or .html, up to 100 MB |
|---|---|
| Files in a zip | up to 2,000, 300 MB total once unzipped |
| Cover image (required) | PNG, JPEG, WebP or GIF, up to 5 MB. 16:9 looks best (e.g. 1280×720) |
| Preview clip (optional) | GIF, WebP, MP4 or WebM, up to 15 MB. A short loop of gameplay works best |
| Tags | 1–5 of: Action, Puzzle, Arcade, Multiplayer, Platformer, Racing, Strategy, Shooter, Casual, RPG, Horror, Sports, Simulation, Retro, Idle |
3. What's not allowed
- Programs and installers (.exe, .dmg, .apk, .jar and similar), even renamed.
- Server-side code (.php, .py, .rb, .asp and similar) and shell scripts. Vibecade only serves static files.
- Crypto-miners, trackers, malware or obfuscated code meant to hide what a game does.
- Anything you don't have the rights to: other people's games, art, music or fonts.
Uploads go live right away after an automatic safety check. A game that calls more than 8 different outside websites, or looks obfuscated, waits for a quick review instead.
4. How games run on Vibecade
To keep players safe, every game runs in a locked-down sandbox on a separate website from Vibecade. Most browser games work without changes:
Works
- Canvas, WebGL, WebAssembly, Web Audio
- Keyboard, mouse, touch and gamepads
- Pointer lock and fullscreen (via the player's button)
- Loading your own files with fetch() and ES modules
- Web Workers created from a Blob URL
- Libraries from CDNs such as jsDelivr, cdnjs and unpkg
localStoragesaves: kept for the session, and synced to the player's account for Vibecade Plus members (up to 512 KB per game)
Doesn't work
- Cookies and IndexedDB. Unity and Godot keep save files in IndexedDB, so those saves won't persist. Test your game after uploading, since some engine versions may not handle this gracefully
- Popups, new tabs and links that leave the page
- Forms that submit to a server
- Web Workers loaded from a file (
new Worker("worker.js")). Create them from a Blob URL instead - Multithreading that needs SharedArrayBuffer
Vibecade adds one small script to your index.html to make localStorage work. To opt out, add <meta name="vibecade-sdk" content="off"> before uploading.
5. Engine export settings
Common setups. Tell us if your engine needs something else.
Plain HTML / JavaScript
Upload your .html file directly, or zip the folder with index.html at the top.
Phaser, PixiJS, Three.js, Kaboom
Build (e.g. npm run build) and zip the output folder (often dist/ or build/).
Construct 3
Export → Web (HTML5), then zip the exported folder.
GDevelop
Export → Web (upload to any host) → zip the folder it creates.
Godot 4
Export → Web with Thread Support turned OFF (Godot 4.3+), then zip the export folder. Name the HTML file index.html.
The threaded export needs browser features the sandbox doesn't allow.
Unity (WebGL)
Player Settings → Publishing Settings: set Compression Format to Disabled (or enable Decompression Fallback). Zip the build folder.
Brotli/gzip builds need special server headers.
GameMaker
Use the HTML5 target and zip the output folder.
RPG Maker MV / MZ
Deployment → Web browsers, then zip the output folder.
LÖVE (love.js)
Build with love.js compatibility mode (-c), then zip the output folder.
C / C++ (Emscripten)
Build to HTML/WASM without pthreads, then zip the output.
Pygame (pygbag)
Not supported yet.
pygbag packages games as a .apk file, which Vibecade blocks for security.
6. If something goes wrong
- The game shows a blank screen.
- Usually a path starting with
/(use./), a file that wasn't included in the zip, or a feature from the “Doesn't work” list. Open the game in your browser's developer tools to see the error. - “index.html must be at the top level of the zip.”
- Zip the folder containing index.html, or select the files inside it and zip those.
- “File type not allowed.”
- The error names the file. Remove it (it isn't needed in a browser) and zip again.
- My game is waiting for review.
- The safety check flagged something, often many outside websites. An admin will look shortly. You'll see the reason on your account page.
- How do I update my game?
- Account → your game → New version. Players get the new version right away, and reviews and plays are kept.