meshfx // DECIMATE
How to reduce the polycount of a 3D model
You reduce a model's polycount with decimation, which collapses edges until the mesh reaches a target triangle count, while you protect UV seams, borders and sharp edges so the shape and texture survive. Decimate in steps, compare the outline at your camera's distance, and bake (precompute) a normal map from the original if flat areas lose detail.
pyrofx effects work today, and new accounts start with $5 of usage.
meshfx measures faults, checks repairs and makes LODs for a triangle budget. meshfx runs on the hosted API: try it in the Playground.
- Count triangles, not quads
- Cut flat and hidden areas first
- Keep the original for baking (precomputing)
01 // BY HAND
Decimate without wrecking the model
- Save a copy of the original, since you will compare against it and bake (precompute) from it.
- Merge duplicate vertices first, so decimation does not tear the mesh open along hidden seams.
- Add a decimate (collapse) operation and set a ratio or target count, starting at 50 percent.
- Turn on the options that keep UVs, borders and sharp edges if your editor has them, and protect the face or outline with a vertex group or weight.
- Look at the model at the distance players see it, with the texture on, and keep cutting while it still reads the same.
- Recalculate normals and set hard edges or a smoothing angle so the shading stays clean.
- [Bake (precompute) a normal map](/mesh/bake (precompute)-high-to-low-poly/) from the original if the cut lost small surface detail.
02 // WHERE TRIANGLES GO
Spend triangles on the outline
Players read a model by its silhouette and by the parts the camera sees most. Flat panels, the underside and areas covered by other parts can lose most of their triangles without anyone noticing, while the curve of a wheel or a head shows every missing edge. Cut the hidden and flat areas hard first and the outline last.
Count in triangles, the unit engines draw. A quad is two triangles, so a 10,000-quad model is 20,000 triangles in the engine.
03 // SHADING
Fix the shading after decimation
Decimation leaves long, thin triangles that shade with streaks when normals are smoothed across them. Mark edges sharper than about 30 to 45 degrees as hard, or use a smoothing angle, then triangulate before you bake (precompute) and bake (precompute) the normal map onto the decimated mesh, not onto an earlier version.
04 // meshfx
meshfx for reduce polycount
meshfx reduces toward a triangle budget and makes LODs by count, ratio, explicit budgets or error. Each level reports measured distance, outline and faults. Godot 4 is the supported output target. Hosted meshfx runs are available in the Playground.
How do I reduce polycount without making a 3D model look worse?
Decimate in steps with UV seams and sharp edges protected, cut flat and hidden areas harder than the outline and compile a normal map from the original.
What is the safest way to reduce polygon count?
Decimate a copy rather than the original in small steps you can compare. Keeping the original also lets you compile its detail onto the reduced mesh.
How do I use decimation without creating bad shading artifacts?
Set hard edges or a smoothing angle after decimating, triangulate before compiling and compile the normal map onto the final mesh to prevent shading streaks.
Does decimation preserve UVs and textures?
It can if you turn on the option that keeps UV seams and the texture still fits. Hard cuts stretch textures, so check seams after reducing.
Should I reduce vertices, edges or triangles first?
Target triangles because engines draw them and budgets count them. Merge duplicate vertices first and triangle reduction removes edges and vertices along with them.
How do I fix a model with messy topology after decimation?
Recalculate normals, fix shading with hard edges and dissolve leftover slivers by hand. If the model must animate or be edited, retopologize it instead.
Explore meshfx outputs
Inspect compiled meshfx outputs and their reports. Hosted meshfx runs are available in the Playground.