Make it in Blender. Play it in the browser.

Use Blender on the creator's computer

The Blender integration runs against your local Blender installation. Once connected to your AI client, it can help create models, assign materials and export assets. This is an authoring workflow: visitors do not need Blender installed to play the published browser game.

Export a self-contained GLB

The build0 upload workflow accepts validated GLB models with embedded buffers and textures. If a source asset is FBX or another authoring format, import or convert it locally before exporting GLB. Check scale, origin and materials in the exported result, rather than assuming a file will look the same in every renderer.

• Embed the textures needed by the model.
• Name animation clips clearly and keep loops intentional.
• Remove unseen geometry and unnecessary material variants.

Upload to the correct lot and bind the asset

Use the lot's authenticated upload tools, inspect the stored asset and reference its returned asset ID in the scene or experience. Include every required asset ID when saving the game version. An asset belonging to another private lot is not automatically available to your experience.

Budget for the device that will play the game

Large textures, dense geometry and many animated copies can make the first load slow. Use the current budgets from get_build_guide, share repeated models where appropriate and inspect the browser result. Improve materials and lighting deliberately before adding more geometry. Save, play and publish the finished version on the same lot.

Your next steps

1. Connect local Blender MCP to the AI client you use for building.
2. Create an original asset and export it as a self-contained GLB.
3. Upload it to your lot and inspect the validated asset information.
4. Bind its asset ID to the game, play the result and publish the version.

Common questions