Web game portals enforce strict technical standards covering initial load speed, compressed package file size, frame rate stability on low-end hardware, audio autoplay compliance, and proper SDK integration. Reviewers test builds on modest devices to confirm smooth performance, verifying that games load quickly without blocking the browser thread or misbehaving in iframes.
At a glance
| Fact | Value | Source |
|---|---|---|
| Core checks across web portals | File size, load speed, stability | developer.crazygames.com |
Portals check three things before they approve a browser game: how fast it loads, how few files and bytes it ships, and how stably it runs on ordinary hardware. Keep total file size and asset counts low so loading stays fast, and test on modest hardware rather than relying solely on a high-end development machine. Portals review builds for smooth web performance alongside required SDK integrations. If you build your game with an AI coding agent in tools like Cursor or VS Code, Playgama MCP lets the agent upload builds, configure game details, and publish an unmoderated sandbox link to test performance before submitting for catalog review.
What actually trips developers up
- Load time: Compress textures and audio, and lazy-load anything not needed on the first screen to keep initial load times short.
- Audio autoplay: browsers suspend the AudioContext until the user interacts with the page; resume it on the first click or tap, per Chrome’s autoplay policy.
- Graphics scaling: Adjust device pixel ratio and engine export settings to keep frame rates acceptable across devices rather than assuming default resolution is fine.
- File hygiene: fewer, larger bundled files load faster than thousands of loose assets; check both size and count limits before you zip a build.
Because these numbers and rules change, verify the current requirements on the portal’s own developer documentation before submitting, and re-check after any major engine or SDK update.
Sources
- CrazyGames technical requirements
- CrazyGames resources
- Working with Poki
- Web Audio, Autoplay Policy and Games
- Playgama for developers
Related questions
Does a browser game need to work offline to pass portal review?
Not stated by these sources as a requirement; the checks that are documented focus on load time, file size, file count and stable performance on low-end hardware.
Why does my audio not play automatically on a portal iframe?
Browsers suspend the AudioContext until the user interacts with the page; call resume() on the AudioContext after a click or tap, per Chrome’s autoplay policy.
Do file size limits differ between portals?
Yes – each portal publishes its own technical requirements page; Check the current developer documentation for any portal before submitting a build.
Last updated: 30 September 2026