Digital Artists

Retopology From Zero: Edge Flow, and Why Automatic Remeshing Isn't Enough

What topology is for, where loops have to go, when one click is the right answer, and the three places automatic tools reliably fail.

Retopology is the task that stands between a model that looks good and a model you can use. It is unglamorous, it is skipped, and skipping it is why so many promising sculpts and scans never become anything.

CG Boost’s beginner walkthrough, which covers the manual workflow in Blender end to end.

What topology is actually for

A mesh’s topology is how its vertices are connected — not its shape, its wiring. Two models can have identical silhouettes and completely different topology, and the difference decides four things:

Deformation. When a joint bends, the surface has to compress on the inside and stretch on the outside. It can only do that cleanly if there are edge loops running around the joint, perpendicular to the direction of the bend. Triangles scattered without regard to the form crease, pinch and tear.

UV unwrapping. Quads unwrap predictably. A dense triangle mesh unwraps into confetti, which means no sensible texture painting and no reusable texture layout.

Subdivision. Catmull-Clark subdivision is defined for quads. Feed it triangles and n-gons and you get pinching at every irregular vertex.

And editability. Selecting an edge loop and sliding it is a one-second operation on good topology and impossible on bad.

If your model will never deform, never be subdivided, and never be UV-unwrapped by hand, you may not need any of this. A static background prop can stay as triangles. Be honest about which case you are in before spending a day.

The rules, which are few

Quads everywhere. Triangles are tolerable in flat, hidden, non-deforming areas. Avoid n-gons entirely.

Loops follow the form. This is the whole craft. On a face, loops run concentrically around the eyes and the mouth, because those are the two features that deform most and need to purse and close. On a limb, loops encircle the joint. On any crease, a loop runs along it.

The test: if this bends, will the edges be positioned to let it?

Poles go where nothing moves. An irregular vertex — three or five edges meeting instead of four — is unavoidable wherever topology has to change direction. They are fine; they just pinch under subdivision. So put them in flat, hidden, static regions: the top of a skull under hair, the inside of a nostril, under an arm.

And density follows detail, not uniformity. More polygons where the form changes fast, fewer on large smooth areas. An evenly dense mesh is wasting polygons on the flat parts and starving the interesting ones.

The three approaches

Automatic remeshing — one click.

  • Blender: Quadriflow (Object → Quad Remesh) or the Voxel remesher
  • ZBrush: ZRemesher
  • Standalone: Quad Remesher (Exoside), which is the same technology behind several integrations

Use it when the model is static — props, environment pieces, scanned objects for display, anything you will bake and never bend. For that case it is the correct answer and manual work is a waste of a day.

It fails in three specific places, and these are not tuning problems:

  1. At joints, because it has no idea which parts bend. You get an even grid across an elbow with no loop around it.
  2. At faces, for the same reason — no concentric loops around eyes and mouth, so every expression creases wrong.
  3. At hard edges, where it rounds or wanders across a crease that should be a clean line.

Manual, quad by quad. Snap vertices to the high-poly surface and build by hand. In Blender: add a plane, Shrinkwrap it to the target, and extrude edges with snapping on. Total control, perfect flow, and slow — a character head is a serious day’s work. Correct for hero assets.

Boundary-first patch modelling, which is the middle path and usually the right one. You draw the patch layout — the division of the surface into quadrilateral regions and the seams between them — and let the tool fill each patch with an even grid. You make the judgement calls; it does the vertex placement. RetopoFlow is the long-standing free Blender add-on for this, and Nitro Retopo is a recent paid one aimed at dense scans, sculpts and generated meshes.

The workflow that actually works

  1. Decide if you need it. Static prop? Remesh and move on.
  2. Block out the patch layout first, before any vertices. Where are the seams? Where do the loops need to run? Sketch it on the surface.
  3. Work low, then subdivide. Build the lowest polygon count that captures the form’s structure. Subdivision adds smoothness; it cannot add edge flow you did not place.
  4. Test the bend early. Put a quick armature in and rotate the joints before you finish. Topology problems are cheap to fix at 2,000 polygons and expensive at 40,000.
  5. Then bake. Transfer the high-poly detail to the low-poly as a normal map. The sculpt’s detail survives; the structure is now yours.

The one thing to internalise

Automatic tools solve polygon count. Only you can solve edge flow. Those are different problems, and a 16x polygon reduction with loops in the wrong places has not improved the model for anything that moves.

If you take one habit: before you place a single vertex, decide where the loops go. Everything else is execution.