Start from the workflow your app needs: prompt-generated primitives, product viewers with real GLB/glTF assets, interactive scenes, or static deployment-ready 3D pages.
Aura3D documentation is organized around production tasks: create an app, describe a scene, register assets, choose templates, use the public API, and prepare a static deployment.
Create a Vite Aura3D app and give an AI coding assistant the public SDK patterns it needs.
Read guide DocumentationGenerate scenes from maintained kits for particles, physics, data, materials, cities, games, and products.
Read guide DocumentationRegister GLB and glTF files with the CLI, then import generated asset references in TypeScript.
Read guide DocumentationPick product-viewer, cinematic-scene, or mini-game starters based on what you want to ship.
Read guide DocumentationUse the public @aura3d/engine surface for scenes, models, lights, cameras, materials, and interactions.
Read guide DocumentationPrepare static output with asset validation, route checks, and production-safe paths.
Read guide