Last verified
Pick by the job you need done
Start with the missing capability, not the biggest platform name. Many browser games need a host plus one or more discovery channels.
Put a static build online
GitHub Pages or another static host
Host files and build an indie project page
itch.io
Get public reviews and community judgment
Newgrounds
Pursue portal ad revenue after engagement testing
CrazyGames
Pursue a curated publisher relationship
Poki
Syndicate across publisher sites
GameDistribution
Control infrastructure and commercial systems
Self-hosting
Add GitHub-backed discovery and player signals
Vibe Arcade
Platform options
Each recommendation names the useful job and the tradeoff that matters before you invest in integration or a contract.
GitHub Pages
Putting a static game online directly from a repository.
- Choose it when
- The build is static HTML, CSS, JavaScript, and assets, and you want a stable URL with an optional custom domain.
- Watch for
- Hosting creates no built-in player audience, marketplace, or game community. Server-side runtimes need another host.
itch.io
HTML5 hosting, a flexible indie project page, community tools, and donations.
- Choose it when
- You want to upload a ZIP or self-contained HTML file and avoid building your own publishing surface.
- Watch for
- A public page and Search or Browse indexing are separate. Publishing does not guarantee discovery placement.
Newgrounds
Community voting, reviews, medals, high scores, and direct public judgment.
- Choose it when
- You want a community-first portal and the game matches its content and submission rules.
- Watch for
- Low-rated work can be removed through community judgment. Current rules exclude fully prompt-generated games and require disclosure of permitted AI use.
CrazyGames
Testing a polished game with portal players and pursuing ad-supported distribution.
- Choose it when
- The game is ready for QA and a measured Basic Launch, with SDK integration justified if it reaches Full Launch.
- Watch for
- Basic Launch does not include monetization. Selection for Full Launch depends on real engagement signals and is not guaranteed.
Poki
A selective publisher relationship for a polished cross-device game.
- Choose it when
- The game is strong on desktop, mobile, and tablet, and you are ready for playtesting, SDK work, and a commercial agreement.
- Watch for
- This is not an open self-service upload. Access is curated, and deal terms can include exclusivity or a different non-exclusive commercial model.
GameDistribution
Syndicating a game across a network of publisher sites.
- Choose it when
- Broad third-party distribution and advertising revenue matter more than controlling every placement.
- Watch for
- SDK integration and QA are required. Read the current developer agreement before committing to continuing build and distribution obligations.
Self-hosting
Maximum control over domain, headers, backend, branding, analytics, and releases.
- Choose it when
- The game needs multiplayer services, custom authentication, commerce, or infrastructure that a static host cannot provide.
- Watch for
- You own availability, performance, security, privacy obligations, and promotion. A hosted URL alone creates no audience.
Vibe Arcade
Adding moderated discovery and player signals to a public GitHub-backed game.
- Choose it when
- You already have the repository and optional hosted build, and want a player-facing listing, likes, charts, return signals, and build reports.
- Watch for
- Vibe does not host files, run payments or ads, provide an SDK network, or guarantee traffic. Every listing is moderated.
Useful publishing combinations
GitHub Pages + Vibe Arcade
A simple public-repository stack: static hosting plus moderated discovery and player signals.
itch.io + Vibe Arcade
HTML5 hosting, project-page tools, and donations plus a separate play-first listing.
Self-hosting + Vibe Arcade
Technical and brand control plus an external acquisition and feedback surface.
Portal + independent home
Portal reach without making one distributor the only durable place where players can find the game.
Before publishing in more places
- 01Choose one canonical build you can update and monitor.
- 02Test desktop and touch controls on representative browsers before claiming support.
- 03Prepare a real gameplay image, a clear player pitch, controls, and an immediate goal.
- 04Read current SDK, revenue, licensing, and exclusivity terms before portal integration.
- 05Use consistent title and creator credit while tailoring each page to that platform's audience.
- 06Track which channel sends useful opens and returns, then deepen the channels that work.
Questions, answered
What is the best platform for a browser game?
Does Vibe publish or host my browser build?
Which hosting providers can I connect to Vibe?
Can I use GitHub Pages for a browser game?
Can I list the repository now and add hosting later?
What happens when I change hosts?
Will a portal accept and monetize my game?
Already have a hosted build?
Check the exact repository, image, controls, and moderation requirements before adding it to Vibe Arcade.