There is no official polygon limit for WebGL browser games. The practical budget is set by download size limits on portals, mobile GPU memory, and draw call counts – not a fixed triangle number. Test on a mid-range mobile browser and cut geometry until it loads and runs smoothly there.
At a glance
| Fact | Value | Source |
|---|---|---|
| WebGL renders 3D via HTML canvas element | no poly cap in spec | developer.mozilla.org |
| Draco compresses meshes for faster web loading | smaller, faster 3D | github.com |
| Build size limits | keep downloads small | developer.mozilla.org |
There’s no official polygon-count spec for WebGL games – the API itself just draws triangles through the browser’s canvas element and doesn’t cap how many. The real budget is set by three things: total download size, mobile GPU/memory limits, and draw call count. As a working rule, keep hero characters in the low thousands of triangles and background props much lower, then test on an actual mid-range phone browser – that’s usually the tightest constraint, not desktop.
With Playgama MCP, an agent uploads builds, gets a QA Tool link, and publishes a sandbox link to test performance on real devices.
What actually limits polygon count in a browser
- File size: portals set hard caps – portals often enforce strict build size caps and warn games will struggle on low-RAM devices if they don’t run smoothly. Large builds lead to long loading times and higher player drop-off, especially on mobile.
- Compression: use glTF as the delivery format and run meshes through Draco compression to cut file size without hand-reducing every model.
- Draw calls, not just triangles: many small high-poly objects can hurt performance more than one bigger mesh, because each draw call has overhead.
- Engine export path: Unity WebGL, Godot’s HTML5 export, and JS frameworks like Phaser all render through the same browser canvas, so the ceiling is the device, not the engine.
Test early on the cheapest phone you can find, and re-check after every asset pass – AI-generated 3D models from tools like Meshy often need retopology or decimation before they’re browser-ready.
Sources
- WebGL API – MDN
- Technical – CrazyGames Documentation
- Developer Docs โ OnlineGameWorlds
- google/draco
- glTF – KhronosGroup
- Playgama for developers
Related questions
Does glTF reduce polygon count automatically?
No. glTF is a delivery format, not a mesh reducer. It minimizes file size and load processing, but you still need to decimate or retopologize high-poly models yourself.
Should I use different polygon budgets for mobile vs desktop browsers?
Yes. Mobile GPUs and memory are the tighter constraint, so test on a mid-range phone browser first and let that set your ceiling, not desktop performance.
Last updated: 30 September 2026