Factorial StudioGameZone

For developers

How to Publish a Unity WebGL Game on Web Portals: The 2026 Checklist

By the Factorial Studio team ยท ยท 8 min read

How to Publish a Unity WebGL Game on Web Portals: The 2026 Checklist

Getting a Unity game onto browser portals is less about Unity and more about the dozen small things portals check before they say yes. This is the list we work through for every game we publish on GameZone and elsewhere. None of it is exotic, and all of it is the difference between a build that is accepted on the first try and one that comes back three times.

Build settings

  • Compression: Brotli gives the smallest files. Turn on Decompression Fallback unless you know the host sends Content-Encoding headers, because many do not. Our loading-screen troubleshooting guide explains why.
  • Run In Background: on. Portals load games in iframes that do not always have focus, and a game that pauses without focus looks broken to a reviewer.
  • Template: a template whose canvas fills the window. Portals size the frame for you; a fixed 960ร—600 canvas ends up letterboxed in a small box.
  • Code stripping and exceptions: use a release build with stripping on and exception support limited to explicit throws. It makes the build noticeably smaller.

Keep the first download small

Every portal measures how many players leave before your game appears. Aim for a first download in the tens of megabytes, not hundreds. Load later levels with Addressables or asset bundles, use compressed textures, and stream music rather than shipping it as uncompressed audio. Check each portal's file-size limits before you start; our own host accepts files up to 100 MB each.

Screen shapes and orientation

Your game will run in a wide desktop frame, a tall phone screen and everything between. Anchor your UI to screen edges rather than fixed positions, test at 16:9, 4:3 and 9:16, and decide whether the game is landscape or portrait so the portal can size its stage for it. A button that is clickable at one aspect ratio and pushed off-screen at another is one of the most common reasons for rejection.

Input

  • Support both mouse and touch. Unity's Input System handles both, but test taps on a real phone.
  • Do not depend on keys browsers reserve for themselves, such as F5, Ctrl+W or the Escape key in fullscreen.
  • Arrow keys and the space bar scroll the page around an iframe. Make sure your game takes keyboard focus once the player clicks it.

Sound and saves

Browsers block audio until the player interacts with the page, so start music after the first click rather than on load. For saves, Unity's PlayerPrefs on WebGL are stored in the browser's IndexedDB for that site, which persists between visits; just remember that a save made on one portal does not carry over to another.

Ads and portal SDKs

Most portals ask you to call their SDK at natural breaks: when gameplay starts and stops, and when a rewarded ad is offered. Keep those calls behind one small interface in your code, so the same build can be adapted to each portal by swapping one implementation rather than touching gameplay.

Store art and the game page

  • A cover image at least 1200 pixels wide in 16:9 or 16:10, with the game's name readable at thumbnail size.
  • A square icon of at least 512ร—512.
  • A description written for players: what you do, why it is fun, and the controls, in your own words for each portal rather than the same text pasted everywhere.
  • A short gameplay video if the portal accepts one. It converts browsers into players better than any screenshot.

Test like a reviewer

Load the build in an iframe on a different domain, on a phone, with a cold browser cache, and play past the first level. If it survives that, it will survive review. When you are ready, you can submit your game to GameZone. Publishing is free and non-exclusive, we can host the WebGL build for you, and you get a developer portfolio page that lists all your games.