Babylon.js Low Poly Models

GLB is the natural format for Babylon.js because the glTF loader can bring in meshes, PBR materials, textures, skeletons and animations through `SceneLoader.ImportMeshAsync` or `AppendAsync`. Keep the asset in meters and +Y up so it matches glTF conventions, apply transforms before export, and put the pivot at the placement point. A prop with its origin at ground center is much easier to clone, instance and align on a Babylon.js scene grid.

The browser budget is usually tighter than the desktop GPU budget. Aim for 200 to 800 triangles for repeated props, 1k to 5k for interactive hero props and 5k to 15k for stylized characters. Material count matters because every distinct material can become another draw call. A single atlas and one PBR material with flat base colors or baked gradients will outperform many tiny materials, especially on mobile Safari and mid-range Android devices.

Babylon.js supports thin instances and hardware instancing, which is a perfect fit for low poly rocks, trees, crates and city pieces. Build repeatable assets with shared geometry and materials so thousands of placements can draw cheaply. If models need collisions, use simplified invisible collision meshes or Babylon impostors instead of triangle-accurate collisions; a faceted visual mesh is rarely the right physics shape.

For delivery, use a GLB optimization pass before publishing. Meshopt or Draco compression can reduce geometry bytes, but test decode time in the actual Babylon.js loader. Resize textures to 512 or 1024px for props, reserve 2048px for close inspection, and keep the unoptimized source separate from the production GLB. A Babylon.js asset is ready when it loads fast, draws in few calls and still looks correct under the scene lighting.