Upload Without Command Line

Start here if you just want to upload a ZIP

You do not need the Buncha Games CLI or SDK to submit a browser game during the Developer Alpha. The normal beginner path is the private Developer Dashboard.

Use this guide if you are not comfortable with command-line tools, tokens, JSON manifests, or coding agents.

Before you have an invite

Request a developer invite from /developers/request-invite.
Invite requests are reviewed manually during Alpha. Timing can vary, and a request is not a guarantee of acceptance.
Prepare a browser-playable export of your game, not the source project.
Write a short game description and collect a thumbnail, hero image, and up to five carousel media assets.
List any external domains your game calls, such as multiplayer, leaderboard, analytics, storage, or API hosts.

What static browser export means

A static browser export is a folder that can be served by a normal web server and opened in a browser. It has an index.html file plus the JavaScript, CSS, WASM, data, and asset files your game needs.

Buncha Games hosts that exported folder. Your uploaded ZIP should not need a Node server, Unity editor project, Godot project, database, private API key, or local development tool to start.

What ZIP root means

The ZIP root is the first level you see when opening the ZIP. Buncha Games expects index.html at that first level.

If you open the ZIP and see a folder first, then index.html inside that folder, re-zip the contents of the export folder instead of the folder itself.

Good:
my-game.zip
  index.html
  assets/
  game.js

Bad:
my-game.zip
  my-game/
    index.html
    assets/
    game.js

Dashboard walkthrough

Sign in with your Buncha Games account after your invite is approved.
Open the Developer Dashboard and activate developer access if prompted.
Create a new game draft.
Fill in title, short description, controls, categories, and content expectations.
Open Manage Game Builds and upload your exported ZIP.
Fix validation errors if Buncha Games reports any.
Open the Sandbox preview and confirm the game loads, plays, and shows clear controls.
Add listing media from Edit Game Info: thumbnail, hero image, and screenshots.
Request external-domain review for any required network calls.
Submit for review only when the Sandbox build, listing, media, and domain disclosures are ready.

Local static server

Some engines, especially Unity WebGL and Godot Web, may not run correctly by double-clicking index.html. A local static server previews the exported folder the way a website would serve it.

If your engine has a preview command, use that. If not, a coding agent can help you run a simple local static server without changing the game.

When to use the CLI instead

Use /developers/docs/cli when you want a coding agent to create or update listings, upload media, check JSON status, or submit repeatable changes without browser file pickers.
Use /developers/docs/agent-quickstart when you want one copy-paste prompt for an agent.
Use dashboard upload first if you are working manually and only have one build to submit.

All docs Request invite