Skip to content

GLB polygon reducer

Simplify your mesh and compare both versions before exporting. Files stay in this browser.

Budget unit
Percentage to keep

Viewport

Open a GLB to view its mesh.

More browser GLB tools

Browser GLB Workflow

How to reduce GLB polygon count without losing shape

Decimate static glTF 2.0 meshes toward a target triangle count or keep-percentage and verify silhouettes side by side.

  1. 01

    Open a static GLB

    Drop any self-contained GLB up to 30 MiB and 250,000 triangles. Mesh simplification runs inside a browser Web Worker with zero server uploads.

  2. 02

    Set target triangles or percentage

    Switch between a target triangle count or a percentage of original faces (5%–100%), then preview the decimated result.

  3. 03

    Compare & export

    Inspect the original and reduced meshes side by side with wireframe and shading toggles, check file-size savings, and download the GLB.

Decimation Best Practices

Hit your polygon budget cleanly

Smart meshoptimizer decimation preserves hard low-poly edges and UV seams while trimming redundant coplanar faces.

Target triangle budgets

Enter a target triangle cap (from 4 triangles up to the source count) when fitting props to strict mobile, Godot, or WebGL budgets.

Percentage scaling

Keep a percentage (5%–100%) when batch-tuning props of varying complexity to a consistent visual density.

Side-by-side wireframe

Toggle Wireframe and orbit both models together to spot collapsed corners, thin handles, or silhouette pinching before export.

UV & material preservation

Materials, embedded textures, and UV mappings are preserved across border-locked vertex collapses so textured low-poly assets stay intact.

Balancing triangle count and file size

Reducing geometry shrinks vertex buffers and speeds up GPU rasterization, while texture resolution often drives total MiB. Combine decimation with our GLB compressor and optimization guides for optimal performance.

Technical Specifications & Guardrails

File limits, runtime guarantees & scope

Supported specifications & hard limits

Input & output
Uncompressed static .glb → Simplified .glb
Maximum file size
30 MiB (31,457,280 bytes)
Supported triangle range
4 to 250,000 triangles (target 4–source or 5%–100%)
Simplifier engine
meshoptimizer WASM (weldPrimitive + simplifyPrimitive)
Topology guardrails
lockBorder: true · max shape error 0.025 (UV & seam safe)
Execution & privacy
100% local browser Web Worker · Free · No upload

What Polygon Reducer does NOT do

  • Does not force an exact triangle count at the expense of destroying silhouettes: border locking (lockBorder: true) and the 0.025 error threshold stop simplification early when collapsing more edges would tear open boundaries, UV seams, or material splits.
  • Does not support skeletal skins, weight-painted rigs, animations, or morph targets—decimate rigged characters inside Blender before export.
  • Does not import already Draco- or Meshopt-compressed GLBs or files with external buffers/textures; export an uncompressed static GLB first.
  • Does not resize or re-encode embedded textures—if a reduced mesh still has a large file size, pass the exported GLB to GLB Compressor next.
Real Measured Benchmarks

Actual decimation results on bundled CC0 GLB models

Measured directly with our production meshoptimizer WebAssembly worker (weld + lockBorder: true, error 0.025). Notice how single-material geometry decimates deeply while multi-material flat-shaded props protect hard color boundaries.

Model & material layoutOriginalTargetActual outputFile size changeBehavior note
River stone (1 material)500 tris · 36.1 KiB50% (250 tris)250 tris36.1 → 5.5 KiB (-84.7%)Clean target hit + vertex welding
River stone (1 material)500 tris · 36.1 KiB25% (125 tris)124 tris36.1 → 3.3 KiB (-90.8%)Within budget, silhouette intact
River stone (1 material)500 tris · 36.1 KiB10% (50 tris)100 tris36.1 → 2.9 KiB (-92.0%)Stops at shape limit (+50 over budget)
Castle exhibit (19 materials)456 tris · 42.7 KiB50% (228 tris)456 tris42.7 → 41.4 KiB (-3.0%)Material borders locked; use Compressor (-52.1%)
Forest pine (5 materials)92 tris · 9.5 KiB50% (46 tris)92 tris9.5 → 9.2 KiB (-3.4%)Already minimal silhouette; borders preserved

Because each material boundary acts as a locked border, multi-material flat-color assets naturally resist aggressive decimation. For those assets, keep the triangles and run GLB Compressor to cut file size by 30%–52%.

Engine Compatibility

Engine compatibility for exported reduced GLBs

Polygon Reducer writes standard uncompressed glTF 2.0 binary (.glb) files with welded indexed meshes, materials, and UVs intact.

Godot 4.x

Direct drag-and-drop (.glb)

Imports cleanly as MeshInstance3D with preserved materials and UVs. Re-enable Generate Shadow Mesh or collisions as needed.

Unity (glTFast)

Direct import (.glb)

Standard indexed triangle lists work out of the box with URP/HDRP materials and automatic tangent recalculation.

Unreal Engine 5

Direct glTF / Interchange import

Works cleanly as a Static Mesh without extra decoder plugins. Ideal for reducing dense AI-generated props before Nanite or mobile builds.

Three.js / WebGL

Direct GLTFLoader (no decoder needed)

Output uses core glTF 2.0 buffers so any WebGL viewer loads it immediately; follow with GLB Compressor if you also want Meshopt + WebP.

Häufige Fragen

Are my GLB files uploaded during polygon reduction?

No. Decimation runs 100% client-side in a Web Worker inside your browser using meshoptimizer WebAssembly. Files up to 30 MiB stay completely private on your device.

What are the file size and triangle limits for online GLB decimation?

Polygon Reducer accepts uncompressed static glTF 2.0 binary (.glb) files up to 30 MiB and 4 to 250,000 triangles or vertices. Pre-compressed Draco/Meshopt inputs, external URIs, skins, animations, and morph targets are rejected cleanly.

Why can a reduced mesh sometimes stay above my target triangle count?

To avoid tearing UV seams, open boundaries, or material splits, the simplifier runs with border locking (lockBorder: true) and a 0.025 shape-error limit. On multi-material props or very aggressive targets—like pushing the 500-triangle River stone to 50 triangles—it stops at the safe shape limit (100 triangles) and warns you before download.

Should I decimate a GLB in one pass or repeatedly re-upload reduced exports?

Always reduce from your original uncompressed GLB in a single pass. Running multiple sequential decimation passes compounds vertex error, pinches silhouettes, and degrades UV interpolation faster than setting one direct target.

Does polygon reduction keep my textures and materials without stretching UVs?

Yes. Embedded textures, PBR materials, and UV coordinates are preserved across vertex collapses, and locking mesh borders keeps UV island seams from tearing on textured props.

How should I decimate heavy AI-generated 3D models for games?

AI-generated props often arrive at 20,000–100,000 triangles. Start with a single pass to 3,000–6,000 triangles for hero props or 1,000–2,000 for background scatter, inspect thin silhouettes in Wireframe mode, and then run GLB Compressor to downscale 2K/4K textures to 1024 px WebP.

Why did reducing triangles barely change my GLB file size?

On textured models, embedded 2K or 4K PNG textures often account for 70%–90% of total bytes. Reducing triangles speeds up GPU vertex shading, while shrinking file size requires passing the reduced GLB through GLB Compressor to resize textures and apply Meshopt or WebP.

What is the minimum triangle count for reduction?

Models must have at least 4 triangles to be simplified, and percentage targets range from 5% to 100%.

Does it support rigged or animated GLBs?

No. The reducer is designed for static GLB meshes. Animated, skinned, or morph-target characters should be decimated in a DCC tool like Blender before export.