Skip to content

Pipeline3 min read

Preparing Low Poly GLB Files for Godot, Unity, and Three.js

One self-contained GLB checklist for Y-up orientation, meter scale, ground-center pivots, vertex attributes, and material parity across Godot 4, Unity, and the web.

Preparing Low Poly GLB Files for Godot, Unity, and Three.js

Why props look fine in one viewer and break in another

A .glb file rarely fails completely across engines—instead, it fails quietly. A barrel imports fine in Three.js yet faces sideways when spawned along a forward vector in Unity, or looks 100× too big in Godot because someone exported centimeters from an authoring tool. Standardizing every asset once before adding it to your project repository eliminates per-scene band-aids.

Cross-engine coordinate alignment diagram showing Y-up and 1 meter scale across Godot, Unity, and Three.js
Cross-engine coordinate alignment diagram showing Y-up and 1 meter scale across Godot, Unity, and Three.js

Engine comparison table: Godot 4, Unity, and Three.js

Even though all three engines converge on 1 unit = 1 meter and Y-up, their forward axes and importer pipelines differ slightly. Design your base GLB around the shared glTF 2.0 conventions below:

PropertyglTF 2.0 / Three.jsGodot 4 (Native)Unity (glTFast / Import)
Up Axis+Y+Y+Y
Unit Scale1 unit = 1 meter1 unit = 1 meter1 unit = 1 meter
Facing / Front+Z forward-Z forward+Z forward
Embedded MaterialsMetallic-Roughness PBRAuto-converts to StandardMaterial3DMaps to URP/HDRP Lit via glTFast
Best Pivot RuleGround-center (Y = 0) for propsGround-center (Y = 0) for terrain snapGround-center (Y = 0) for prefab scatter

Keep directional props consistent inside your own library. If you use +Z or -Z as the front face of signs, carts, and doors, apply that rule uniformly so placement scripts never need special-case rotation tables.

Standardize scale, rotation, and pivot in one pass

Instead of booting a heavyweight desktop DCC suite just to nudge a pivot or flip a rotated export, open the .glb locally in Origin & Transform:

  1. Pick the right pivot preset: Use bottom for ground-anchored props (trees, fences, barrels, buildings), center for floating pickups or spinning objects, and top for ceiling-mounted lanterns or hanging signs.
  2. Fix quarter-turn rotations: Apply exact ±90° turns on X, Y, or Z to correct Z-up exports or align every directional prop to the same forward axis.
  3. Bake cleanly: Export a fresh self-contained .glb with normalized geometry coordinates rather than relying on parent transform hacks.
Wooden barrel prop grounded at Y=0 with clean bottom-center pivot
Wooden barrel prop grounded at Y=0 with clean bottom-center pivot
Directional wooden signpost prop aligned consistently along the forward axis
Directional wooden signpost prop aligned consistently along the forward axis

Check geometry health before committing to version control

Before checking a prop into Git or dropping it into a shared asset folder, open it in the GLB Inspector (supports files up to 30 MiB and 250,000 triangles completely client-side) and confirm five green lights:

  • Dimensions in meters: Sanity-check width, height, and depth against real life (a barrel around ~0.9 m tall, a pine tree ~3 m tall, a doorway taller than 2.1 m).
  • Normals present: Missing vertex normals trigger smooth-shading glitches or pitch-black faces under dynamic lights.
  • UVs verified when textured: Ensure UV coordinates exist whenever a prop carries embedded baseColor or detail textures.
  • Zero external file paths: A true self-contained .glb packs images inside the binary container so it never breaks with missing .bin or textures/ folders on teammates machines.
  • Reasonable triangle & byte footprint: Trim bloated meshes with Polygon Reducer and generate mid/far levels via the LOD Generator before duplicating prefabs across levels.

Want to make sure all of those standardized props also look like they belong in the same world? Continue to Keeping Mixed Low Poly Props Consistent in One Game Scene.

Recommended GLB tools

Mehr zum Lesen