August 25, 2026 · 5 min read

Hosted Build vs. External URL: Which Should You Submit?

Two different ways to get an HTML5 game onto a portal — uploading a ZIP for them to host, or pointing at a URL you control. The tradeoffs aren't obvious until something breaks.

Most portals that accept HTML5 games give you two options: upload a ZIP build that they host directly, or submit a playable URL that they load in an iframe (or redirect to). Neither is universally better — the right choice depends on how often you plan to touch the game after launch.

Hosted ZIP: what you get

The portal serves the files from its own infrastructure, on its own domain. That usually means faster load times (same CDN as the rest of the site, no cross-origin request to a third party) and no dependency on your own hosting staying online. The tradeoff is friction on updates — a new build usually means a re-upload and, on portals with review gates, another review pass.

External URL: what you get

You keep full control. Push a fix to your own server and every portal embedding that URL gets the update instantly, no resubmission. This is the better option if you expect to patch bugs or balance the game after launch. The tradeoff: your own hosting becomes a dependency — if your server goes down or your HTTPS certificate expires, the game breaks on every portal simultaneously, not just yours.

Things that bite people on the URL route

HTTPS is non-negotiable — a portal embedding an http:// URL inside its own https:// page gets blocked by the browser (mixed content).
Changing what a live URL serves without notice can trigger re-review on portals that watch for content drift after approval — treat it as a real deploy, not a silent swap.
CORS and X-Frame-Options headers on your server need to actually allow being embedded — a server locked down to block iframing everywhere will block the portal too.
Uptime is now part of your game's reputation across every portal at once, not just your own site.

A reasonable default

If you're actively iterating on a game post-launch, the URL route saves real time over months of re-uploads. If the game is finished and you don't plan to touch it again, a hosted build removes your own infrastructure as a point of failure entirely. PlayKovo accepts both — see submission rules for the specifics of each path.