Field guides
Guides for browser-game assets
Practical developer guides on GLB optimization, glTF vs GLB, image-to-3D cleanup, Three.js loading, colliders and MCP asset workflows.
Choose what you are working on
AI 3D model generator for static game props
Turn a single reference image, text prompt, or existing GLB into a static 3D game prop with metre scale, two GLB tiers, box collision and a Three.js demo.
Read more ↗Free downloadsFree 3D game assets with playable examples
Download nine self-authored CC0 3D game scenes (buildings, walkable terrain and static props), each with two measured GLB tiers, collision data and a Three.js demo.
Read more ↗Practical guideHow to optimize a GLB model for a browser game
A practical GLB optimization checklist for WebGL and Three.js: separate download bytes from GPU VRAM, set triangle and texture budgets, and verify exported meshes.
Read more ↗Practical guideHow to load GLB game assets in Three.js
Load static GLB models in Three.js with GLTFLoader, verify Y-up metre scale and grounding, attach explicit collision data, and dispose WebGL resources cleanly.
Read more ↗Practical guideChoosing colliders for 3D game assets
Choose the right 3D collider for browser games: conservative boxes for props, compound wall boxes for open doorways, and shared heightfields for walkable terrain.
Read more ↗Practical guideImage to 3D for browser games: reference prep and fixing raw AI meshes
Prepare clean single-prop reference images and fix real image-to-3D mesh defects for WebGL games: baked background clutter, 8K textures, missing normals, scale drift and open geometry.
Read more ↗Practical guideglTF vs GLB for web and Three.js games: delivery, VRAM and asset checks
Compare multi-file .gltf and binary .glb for Three.js browser games: single-file HTTP delivery, why download size differs from GPU VRAM, material draw calls, and GLB header checks.
Read more ↗Practical guide3D game asset workflow with coding agents and MCP
Build Three.js browser games with coding agents using deterministic scene.json and report.json contracts, local CC0 packs, and SceneCrate’s scoped paid-account MCP endpoint.
Read more ↗