Skip to content

Guides4 min read

How to Reduce GLB File Size Without Ruining the Silhouette

Measure whether geometry buffers or embedded PNG textures are bloating your GLB, backed by real byte measurements from 500-triangle flat meshes and 24,864-triangle textured props.

How to Reduce GLB File Size Without Ruining the Silhouette

What actually takes up bytes inside a GLB

A self-contained .glb is a single binary container holding a JSON scene header, one binary buffer (BIN) for vertex positions, indices, normals, and UVs, plus any embedded texture images. Because everything ships in one file, optimizing blindly—such as decimating a mesh whose weight actually comes from an oversized 2048 × 2048 PNG—barely moves the needle.

Anatomy diagram showing the GLB Header, JSON Chunk, BIN Geometry Buffer, and Embedded Images
Anatomy diagram showing the GLB Header, JSON Chunk, BIN Geometry Buffer, and Embedded Images
GLB ComponentWhat Lives InsideDominates File Size When…Primary Lever
JSON ChunkScene hierarchy, nodes, material definitionsAlmost never (typically a few KiB)Merge redundant empty nodes
BIN Geometry BufferVertex POSITION, NORMAL, TEXCOORD_0, indicesUntextured or high-poly scans (> 10k tris)Simplify mesh in Polygon Reducer or encode with GLB Compressor
Embedded ImagesBaseColor, normal, and roughness PNG/JPEG/WebP blobsProps include 1024px–4096px texturesResize & convert textures to WebP in GLB Compressor

See the official Khronos GLB specification for chunk alignment rules.

Benchmark 1: flat-color geometry reduction on River stone

When a prop has zero embedded textures, 100% of its weight sits in the JSON and BIN vertex buffers. You can verify the exact byte savings right inside the browser:

  1. Open the Polygon Reducer and load the built-in River stone sample (or download the free River stone GLB directly).
  2. Switch targeting mode to Triangles, enter 250, and run Preview reduction.
  3. Toggle the wireframe preview and inspect both the silhouette and exported byte count, then verify the download in the GLB Inspector.
River stone original wireframe at 500 triangles (36,944 bytes)
River stone original wireframe at 500 triangles (36,944 bytes)
River stone reduced wireframe at 250 triangles (5,664 bytes, 85% smaller)
River stone reduced wireframe at 250 triangles (5,664 bytes, 85% smaller)

On this clean flat-color prop, cutting triangles in half reduced the file size from 36,944 bytes (500 tris) to 5,664 bytes (250 tris)—an 85% drop in file size. Not only are there fewer faces to serialize, the simplified mesh also shares indexed vertices cleanly across adjacent triangles instead of storing bloated duplicate attributes.

Why reduction sometimes stops above your target

Try running the same River stone with an aggressive target of 50 triangles. In our test, the simplifier hit its geometric shape-error limit at 100 triangles—50 triangles above budget—while still shrinking the download from 36.1 KiB down to 2.9 KiB.

Never force an automated reducer past its topology floor blindly. Open the wireframe comparison first: if key silhouette ridges collapse or thin borders invert, pick a moderate triangle target or keep the original file for hero close-ups.

Benchmark 2: textured meshes and embedded images

Dense AI-generated or sculpted meshes often combine high polygon counts and embedded color textures. Take our textured Oak barrel benchmark sample:

Textured Oak barrel original mesh at 24,864 triangles (630,144 bytes)
Textured Oak barrel original mesh at 24,864 triangles (630,144 bytes)
Textured Oak barrel simplified to 1,500 triangles while preserving UVs and wood bands
Textured Oak barrel simplified to 1,500 triangles while preserving UVs and wood bands

Decimating oak-barrel.glb from 24,864 triangles (630,144 bytes) down to 1,500 triangles cleanly removes 94% of the polygon load while preserving the silhouette and iron band UVs. However, once geometry is already compact (500–1,500 tris), any remaining megabytes almost always belong to embedded textures:

  • Check Embedded Textures in the GLB Inspector. If it is >= 1 and your GLB still exceeds 1–2 MiB after polygon reduction, geometry is no longer the bottleneck.
  • Open the file in the GLB Compressor to cap oversized 2048 × 2048 or 4096 × 4096 textures at 1024 px or 512 px, re-encode embedded maps to WebP, prune duplicate accessors, and apply EXT_meshopt_compression in one browser pass.

Meshopt compression + WebP textures without decimation

If your triangle count is already dialed in and you cannot afford silhouette changes, open the GLB Compressor instead of simplifying polygons:

  • Meshopt geometry encoding (EXT_meshopt_compression) shrinks vertex and index buffers dramatically on static meshes—reducing our 500-triangle River stone from 36,944 bytes to 6,536 bytes (82.3% smaller) with zero lost faces.
  • Vertex welding & pruning removes unused accessors and duplicate materials without changing appearance.
  • Texture downscaling & WebP encoding brings bloated 2048 px PNG maps down to 1024 px or 512 px right in the browser before shipping to WebGL, Three.js, or Godot 4.

A repeatable check before shipping

Recommended GLB tools

Related guides & reading