ZIP Package Checklist
Prepare an HTML5 game ZIP for RetiPie with index.html at the root, bundled assets, allowed file types, and clean paths.
Use this checklist before uploading a multi-file game bundle to RetiPie Slice.
Required structure
Your ZIP must contain an index.html file at the root, or inside one shared root folder that RetiPie can strip during extraction.
game.zip
index.html
main.js
style.css
assets/
player.pngThis also works:
game.zip
my-game/
index.html
main.js
assets/
player.pngBefore upload
- Bundle images, audio, fonts, data files, and scripts inside the ZIP.
- Use relative asset paths so files resolve after extraction.
- Remove build folders that are not needed at runtime.
- Avoid third-party ad SDKs, analytics scripts, pixels, or tag managers.
- Keep the file names your game references. RetiPie stores them as they are; names containing
.., a backslash, or a control character are rejected. - Leave out executables, other interpreters' scripts, app packages, and nested archives. See File types.
- For engine exports, follow the Unity or Godot guide.
macOS metadata
Finder can add __MACOSX metadata folders. RetiPie filters these during extraction, but removing them before upload keeps the archive easier to inspect.
Validation
RetiPie checks blocked file types, executable content, file names and path length, extracted size and decompression ratio, maximum file count, and ad or tracking patterns before a release becomes active.
Game Requirements
File types, size limits, and runtime rules for HTML5 games on RetiPie, from the index.html entry point to bundling every asset with your upload.
Mobile Readiness Checklist
Check controls, first-screen clarity, loading state, orientation, and runtime behavior before submitting an indie browser game to RetiPie.