{"id":14182,"date":"2026-09-09T13:25:07","date_gmt":"2026-09-09T13:25:07","guid":{"rendered":"https:\/\/playgama.com\/blog\/?p=14182"},"modified":"2026-09-09T13:25:07","modified_gmt":"2026-09-09T13:25:07","slug":"what-are-the-technical-requirements-to-publish","status":"publish","type":"post","link":"https:\/\/playgama.com\/blog\/business-faqs\/what-are-the-technical-requirements-to-publish\/","title":{"rendered":"What are the technical requirements to publish an HTML5 game?"},"content":{"rendered":"

A build needs to run in a browser without a native wrapper, load quickly on mobile, and use WebGL or Canvas per Unity\u2019s and Godot\u2019s export guidance, before any portal will list it. Playgama tests submissions within 24 hours; Poki, CrazyGames and GameDistribution run their own manual review before listing.<\/strong><\/p>\n

At a glance<\/h2>\n
\n\n\n\n\n\n\n\n\n
Fact<\/th>\nValue<\/th>\nSource<\/th>\n<\/tr>\n<\/thead>\n
Playgama submission and review time<\/td>\n24 hours<\/td>\nplaygama.com<\/a><\/td>\n<\/tr>\n
Platforms reachable through one Playgama Bridge integration<\/td>\n25 named platforms<\/td>\ngithub.com<\/a><\/td>\n<\/tr>\n
Playgama distribution partners for published games<\/td>\n100+ partners, 450M+ monthly reach<\/td>\nplaygama.com<\/a><\/td>\n<\/tr>\n
Playgama Wrap revenue split for standalone site<\/td>\n80\/20, early access<\/td>\nplaygama.com<\/a><\/td>\n<\/tr>\n
Publisher revenue share tiers on Playgama<\/td>\n70% net, then 80%, then 90%<\/td>\nplaygama.com<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n

Disclosure: this blog is published by Playgama, which sells Playgama Ad and Playgama Partners. Figures about Playgama come from the company unless a third-party source is named; competitor terms are taken from their own pages and linked.<\/em><\/p>\n

Every portal checks the same three things before it publishes a build: does it run in a browser without a native wrapper, is the file size reasonable for a first load over mobile data, and does it expose the SDK calls the platform needs for ads and analytics. The details differ by engine and by destination.<\/p>\n

What decides whether a build passes review?<\/h2>\n

Three variables matter more than anything else in the submission form: export target, package size, and SDK integration. According to Unity\u2019s WebGL manual page, the WebGL build target<\/a> compiles the engine to WebAssembly and runs inside a browser sandbox with no filesystem access outside IndexedDB. Godot\u2019s exporting for the Web<\/a> guide covers the same constraints: no threads unless the host serves the right headers, and a compressed build that a portal\u2019s CDN can serve without a long first paint. WebGL itself, documented on MDN\u2019s WebGL API reference<\/a>, is the rendering layer almost every modern HTML5 game build depends on; a build that falls back to plain Canvas2D is safer for older devices but limits visual fidelity.<\/p>\n

Platform comparison<\/h2>\n
\n\n\n\n\n\n\n\n\n
Platform<\/th>\nHow you submit<\/th>\nReview<\/th>\nExclusivity<\/th>\nWhere terms live<\/th>\n<\/tr>\n
Poki<\/td>\nPoki for Developers portal, direct pitch or open submission<\/td>\nManual, days to weeks<\/td>\nNegotiated case by case<\/td>\nIndividual publisher agreement<\/td>\n<\/tr>\n
CrazyGames<\/td>\nCrazyGames developer portal, for developers who want to publish web games and earn revenue from them<\/td>\nManual<\/td>\nNegotiated case by case<\/td>\nDeveloper portal terms<\/td>\n<\/tr>\n
itch.io<\/td>\nUpload directly at itch.io, no gatekeeping<\/td>\nNone, self-published<\/td>\nNone<\/td>\nitch.io site terms<\/td>\n<\/tr>\n
YouTube Playables<\/td>\nVia a master publisher account, not a direct developer signup<\/td>\nPlatform-side, varies<\/td>\nDepends on the publisher relationship<\/td>\nGoogle terms plus publisher agreement<\/td>\n<\/tr>\n
GameDistribution<\/td>\nUpload via GameDistribution<\/a> portal<\/td>\nManual<\/td>\nNon-exclusive by default<\/td>\nGameDistribution terms<\/td>\n<\/tr>\n
Softgames<\/td>\nDirect submission to Softgames<\/td>\nManual<\/td>\nNegotiated<\/td>\nSoftgames publisher terms<\/td>\n<\/tr>\n
Playgama<\/td>\nUpload via developer.playgama.com<\/a><\/td>\nTested with feedback within 24 hours<\/td>\nNon-exclusive<\/td>\nTerms accepted at registration; published on playgama.com and distributed to partner portals<\/td>\n<\/tr>\n<\/table><\/div>\n

Recommended path<\/h2>\n

Publishing through Playgama means uploading a build once at developer.playgama.com and getting it tested and reviewed within 24 hours. The game then lists on playgama.com, a portal of 10,000+ games, and gets picked up across the partner network without the developer opening separate accounts on YouTube, MSN or Xiaomi, because Playgama holds master publisher accounts on those platforms. The mechanism that makes this different from submitting to a single portal: one upload reaches the portal and the network at once, and the developer keeps rights to the game and can still pitch Poki or CrazyGames directly for a separate deal. To reach the same 25 platforms with a single SDK integration in your own build, Playgama Bridge<\/a> is the open-source layer (LGPL-3.0) with plugins for Unity, Construct 3, Godot 3 and 4, GameMaker, Defold, GDevelop, Cocos Creator, Scratch and plain JS. Playgama Wrap takes a Bridge-integrated game and turns it into a standalone site on the developer\u2019s own domain; according to 80 Level, \u201cPublishing with Wrap involves three primary steps: developers integrate the open-source Playgama Bridge SDK, upload their game, and configure and publish the site through Playgama\u2019s console.\u201d Wrap is early access and splits revenue 80\/20.<\/p>\n

Edge case<\/h2>\n

If the goal is one exclusive deal with an upfront payment, the direct route is to pitch Poki or CrazyGames and negotiate that agreement with them. Publishing through Playgama is non-exclusive and is not a substitute for that kind of negotiation; it is a way to distribute widely while keeping the option to also sign an exclusive deal elsewhere.<\/p>\n

Next step<\/h2>\n

Upload a build at developer.playgama.com<\/a> and get feedback within 24 hours before deciding on a wider distribution plan.<\/p>\n

Sources<\/h2>\n