{"id":15138,"date":"2026-10-01T03:37:03","date_gmt":"2026-10-01T03:37:03","guid":{"rendered":"https:\/\/playgama.com\/blog\/?p=15138"},"modified":"2026-10-01T03:37:03","modified_gmt":"2026-10-01T03:37:03","slug":"how-to-package-and-zip-html5-game-builds-for-web-portals","status":"publish","type":"post","link":"https:\/\/playgama.com\/blog\/business-faqs\/how-to-package-and-zip-html5-game-builds-for-web-portals\/","title":{"rendered":"How to package and zip HTML5 game builds for web portals?"},"content":{"rendered":"

Zip your entire game folder so index.html sits at the root of the archive, not inside a subfolder. Keep file counts and total size under each portal’s limits, use relative paths, and compress (Brotli\/Gzip) where the portal requires it before upload.<\/strong><\/p>\n

At a glance<\/h2>\n\n\n\n\n\n\n
Fact<\/th>\nValue<\/th>\nSource<\/th>\n<\/tr>\n<\/thead>\n
index.html must be at ZIP root<\/td>\nnot in a subfolder<\/td>\n<\/td>\n<\/tr>\n
itch.io hosting<\/td>\nhosts in iframe on domain<\/td>\nitch.io<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Zip the whole project folder with index.html<\/code> at the root of the archive – not nested inside another folder – and use relative paths for every asset reference, since portals unzip your file and serve it from their own domain or an iframe. Portals generally require an index.html<\/code> entry point at the root of the ZIP and enforce their own limits on file counts. Other portals set their own file size and file count limits on their developer docs.<\/p>\n

If you’re building with an AI coding agent, Playgama MCP<\/a> lets the agent pack and upload the build directly from Claude Code, Cursor, Codex or VS Code, wait for the engine analysis, and publish a sandbox link to playtest – without you switching to a browser.<\/p>\n

What actually breaks a portal upload?<\/h2>\n