Creator Resources

Build faster. Ship better browser games.

Guides, templates, prompts, and checklists for creating upload-ready 3JS games.

Browse resources Upload your game

Start here

Featured resources

Focused guidance for the most common release blockers.

Upload

Checklist

Upload Checklist

Make sure your ZIP, thumbnail, metadata, and preview are ready before publishing.

ZIPmetadatathumbnail

Read checklist

1Upload the distributable build, not the source project.
2Place index.html at the ZIP root and use relative asset paths.
3Add an accurate title, description, category, tags, and 16:9 thumbnail.
4Preview the sandboxed build before you publish.

Upload

Guide

ZIP Structure Guide

Learn what your game ZIP must contain, including index.html and safe file paths.

index.htmlpathsassets

View guide

1ZIP the contents of your production build folder, not the folder itself.
2Keep index.html directly at the archive root.
3Bundle every local asset and reference it with a relative path.
4Exclude secrets, project tooling, source maps, and server-side code.

Performance

Checklist

Performance Checklist

Keep load time, textures, audio, and runtime performance under control.

texturesaudioruntime

Optimize game

1Compress textures, models, and audio before packaging.
2Defer optional assets and keep the first playable load small.
3Avoid per-frame allocations and cap expensive effects.
4Test the production build on a mid-range phone and laptop.

Mobile

Guide

Mobile Controls Guide

Design touch-friendly controls and declare mobile support honestly.

touchcontrolsresponsive

Read guide

1Use visible controls with comfortable touch targets.
2Prevent accidental page scrolling while gameplay is active.
3Handle resize, orientation, pause, and fullscreen transitions.
4Only declare mobile support after testing on a real touch device.

Prompts

Prompt

Codex Game Prompt Starter

A starter prompt for generating small, upload-ready browser games.

Codexstarterscope

View prompt

1Build a small static browser game with a single clear play loop.
2Keep index.html at the build root and bundle runtime assets locally.
3Support keyboard and mouse; add touch only when it can be tested.
4Return production build steps plus a short compatibility test plan.

Safety

Guide

Safety Basics

Understand upload scanning, sandboxed playback, and what not to include in game builds.

sandboxscannersecrets

Read safety basics

1Never include credentials, tokens, personal data, or remote administration code.
2Review every scanner error and warning before publishing.
3Keep external network requests intentional and documented.
4Remember that automated scanning reduces risk but cannot guarantee safety.

Find your lane

Browse by type

Counts come directly from this curated Alpha registry.

Practical notes

Detailed guides and checklists

6 resources shown

Release Checklist

Templates

A final pre-publish checklist for testing, metadata, screenshots, and controls.

1Test a fresh production build with the browser console open.
2Verify the title, description, category, tags, and thumbnail.
3Check keyboard, mouse, audio, pause, and restart behavior.
4Run the 3JS preview and fix every blocking compatibility issue.

Browser Compatibility Checklist

Tools

Test keyboard, mouse, touch, audio unlock, fullscreen, and iframe behavior.

1Test current Chrome, Firefox, and Safari when available.
2Unlock audio from a user gesture and recover cleanly after pause.
3Confirm keyboard focus, pointer input, and fullscreen transitions.
4Run inside the 3JS preview because sandboxed iframe behavior can differ.

Thumbnail Brief

Templates

A compact creative brief for readable 16:9 game artwork without misleading players.

1Show the actual visual tone or play space of the game.
2Keep the focal subject readable at small card size.
3Use strong contrast and avoid tiny text.
4Export JPG, PNG, or WebP without fake awards or review badges.

Asset Audit Prompt

Prompts

A review prompt for finding oversized, unused, remote, or missing game assets.

1Audit this production build for unused and missing assets.
2List large textures, models, audio, and video with optimization suggestions.
3Flag remote runtime dependencies and absolute paths.
4Do not alter gameplay; return a prioritized packaging checklist.

Touch Test Plan

Mobile

A short repeatable test for orientation, gestures, focus, and comfortable controls.

1Play once in portrait and once in landscape.
2Check every control near screen edges and browser navigation gestures.
3Rotate and resize during play, pause, and restart.
4Record the devices tested before declaring mobile support.

Production Build Review

Tools

Use browser tools to catch console errors, missing files, and slow first loads.

1Serve the build locally instead of opening index.html directly.
2Reload with the Network and Console panels open.
3Confirm every required request succeeds without source-project paths.
4Test a cold load with cache disabled, then package only the build output.