LEARN // meshfx

Retopology vs decimation: what is the difference

Decimation removes triangles from your mesh until it hits a budget, keeping the existing layout and mostly its UVs, but it leaves long, uneven triangles. Retopology builds a new, clean layout of faces over the same shape, which deforms and unwraps well but needs new UVs and newly baked (precomputed) textures. Remeshing rebuilds the whole surface at one even density.

pyrofx effects work today, and new accounts start with $5 of usage.

MODULE // meshfx AVAILABLE

meshfx measures faults, checks repairs and makes LODs for a triangle budget. meshfx runs on the hosted API: try it in the Playground.

  • Decimation: fewer triangles, same layout
  • Retopology: new clean faces, new UVs
  • Remeshing: even density everywhere
  • meshfx: measured outputs; hosted availability shown separately

01 // THE DIFFERENCE

Three ways to change a mesh

  • Decimation collapses edges where the surface is flattest, so a 500,000-triangle scan can drop to 20,000 triangles in one quick pass. The shape holds, and the triangles turn into long slivers.
  • Retopology lays new faces over the surface, usually quads with loops that follow the form. It takes longer and gives the cleanest result.
  • Remeshing, by voxels or a quad field, rebuilds the surface at an even density. It repairs holes and overlaps in a broken scan, and it loses the UVs and some sharp detail.

02 // WHICH TO USE

Pick one for your asset

Decimate static props, rocks, buildings and LOD levels, where nobody sees the triangle layout and the existing UVs and textures can stay. Retopologize characters, anything that bends, and assets you will texture by hand. Remesh first when a scan or generated model is too broken for either, then retopologize or decimate the remeshed result.

03 // SPATIAL COMPILER

meshfx and retopology vs decimation

meshfx reduces triangle counts and makes LODs while retaining source UVs. Rebuild quad loops by hand when your model needs them. Hosted meshfx runs are available in the Playground.

05 // FAQ

Retopology and decimation questions

All questions →

README.RETOPOLOGY_VS_DECIMATION
Should I retopologize or decimate a 3D model?

Decimate static models when existing UVs are worth keeping. Retopologize models that animate, need hand texturing or shade poorly after reduction.

Does decimation preserve UVs and textures?

Mostly. Edge collapse decimation keeps existing UVs on remaining vertices, though heavy reduction can stretch seams and require a fresh normal map.

How do I decimate a mesh without shading artifacts?

Reduce in steps, stop before the silhouette breaks, protect UV seams and hard edges and transfer normals from the original model.

Should LOD levels be generated by decimation or manual retopology?

Decimation works best for almost every LOD level because distant models are small on screen and keep their existing UVs.

What is remeshing in 3D modeling?

Remeshing rebuilds a mesh surface with new evenly spaced faces, cleaning broken geometry while discarding existing UVs and fine surface detail.

How do I fix messy shading after decimation?

Return to the original mesh and decimate less or retopologize it. Otherwise recalculate normals and transfer a normal map from the source.

Explore meshfx outputs

Inspect compiled meshfx outputs and their reports. Hosted meshfx runs are available in the Playground.

All effects, guides and explainers →