Pushing a realistic head to tens of millions of polygons in ZBrush feels great. The problem starts the moment you try to do anything with it. Drop it into a game engine and the engine chokes. Try to rig it and there's nothing to grab onto. Open the UVs and it's a disaster. The hard truth is that a high-poly sculpt isn't the finished asset—it's a detail blueprint. Nothing more.

What actually ships is a clean, low-density mesh with sensible topology, wearing the high-poly's detail as a normal map. Getting from one to the other involves two steps that beginners constantly run together: retopology and decimation. They sound similar, but they solve completely different problems. Not understanding that difference is the single biggest reason people get stuck at the "I can sculpt it but I can't use it" stage.

This guide walks the whole pipeline: why this step exists, what good topology actually looks like, when to reach for ZRemesher versus manual retopo, where Decimation Master fits in, and a full start-to-finish workflow that takes you from a finished sculpt to a bakeable, riggable low-poly. If you haven't sculpted a complete head yet, start with Sculpting a Realistic Face: Skull, Proportion, and a Six-Step ZBrush Workflow first—this article assumes you already have a high-poly in hand.

1. Get the vocabulary straight first

This section looks like basics, but read it anyway. Every workflow decision later in the article rests on the distinction between these four terms.

High-poly. A very dense model, usually somewhere between a few million and tens of millions of polygons. Its only job is to hold detail—pores, wrinkles, fabric folds, scratches in armor. It doesn't care whether the topology is tidy. A DynaMesh result made entirely of chaotic triangles is fine, because all it has to do is carry the sculpt.

Low-poly. An optimized model built for its final purpose. A game character might land anywhere from a few thousand to tens of thousands of polygons; film assets run higher. The low-poly's mesh has to behave: it needs to deform properly, take a clean UV layout, and render in real time. All that high-poly detail eventually gets baked onto its surface as a normal map.

Topology / retopology. Rebuilding a clean, mostly-quad mesh from scratch over the sculpt. Retopology is about flow—the way the edges run should follow muscle movement and the directions the surface deforms. This is the proper road from high-poly to a usable low-poly.

Decimation. An algorithm that slashes triangle count while preserving the silhouette as closely as possible. What you get back is a mass of unevenly distributed, completely irregular triangles. It holds the shape, but the topology is noise.

Burn this one line into memory and you'll dodge most of the trouble:

Decimation is not retopology. Decimation processes the high-poly. Retopology produces the low-poly.

A decimated mesh is lighter, sure, but its messy triangulation can't be rigged, can't deform, and won't unwrap cleanly. It has its own legitimate uses—we'll get to them—but it is not a game-ready low-poly. Treating a decimated mesh as your low-poly is the most classic beginner mistake there is.

2. What "good topology" actually means

Retopology isn't just "make the polycount go down." You're redesigning the skeleton of the mesh. Good topology follows a handful of principles.

Quads first

In game and animation pipelines, quads are the default choice, for three reasons. They form continuous edge loops, which makes detail easy to add and control. They subdivide cleanly, whereas triangles tend to pinch and artifact when you smooth them. And they deform predictably.

Triangles aren't forbidden—everything gets triangulated on its way into an engine anyway—but during the modeling stage you want to stay quad-dominant and tuck whatever triangles you need into flat areas that don't deform or subdivide. N-gons (five-sided faces and up) are a different story: avoid them entirely. They almost guarantee shading errors and broken deformation.

Edge flow that follows deformation

This is the soul of retopology. The mesh should run with the muscles and the regions that stretch and compress. The face is the strictest case:

  • Wrap edge loops around the eyes and mouth—concentric rings that follow the orbicularis muscles—so the mesh contracts and relaxes naturally when the character blinks, talks, or makes an expression.
  • Give the nostrils, eye corners, and mouth corners enough loop density, since they deform heavily—but don't pile up poles there.
  • Let flat regions like the forehead and cheeks breathe with sparser geometry.

If your edge flow runs perpendicular to how the muscles move, expressions will tear and pull in ugly ways the moment they animate.

Pole placement

A pole is a vertex where some number of edges other than four meet. The common ones are the E-pole (three edges) and the N-pole (five edges). Poles are unavoidable—the question is where you put them.

Poles disrupt the surrounding edge flow and mess with subdivision smoothing, so keep them out of heavy-deformation zones like eye corners, mouth corners, and joints. Hide them instead in flat, low-movement areas—the top of the scalp, the side of the cheek.

Polygon budget

Lower isn't automatically better. The goal is "enough, distributed well." Spend polygons where there's deformation and the camera gets close (face, hands); economize where the surface is flat and rarely seen (back of the head, the inside of the torso). Decide what the asset is for—mobile, console, or film—and work backward to a budget from there. That's where a professional process starts.

3. Two roads: retopology vs. decimation, and where each belongs

Once you know what good topology looks like, the next question is how to get there. From high-poly to low-poly you have two families of tools, and they serve two very different purposes.

Road A: Retopology — building a real low-poly

If your asset needs rigging, animation, expressions, or subdivision, you must retopologize. This comes in automatic and manual flavors.

Automatic: ZRemesher. ZBrush's built-in ZRemesher is the workhorse for auto-retopo. One click reprocesses the high-poly into a mostly-quad mesh with fairly even flow. The settings that matter:

  • Target Polygons Count, paired with the Adaptive / Half / Same modes above it, controls final density.
  • ZRemesher Guides lets you paint guide curves directly on the surface, and ZRemesher routes the flow along the lines you draw. Drawing loops around the eyes and mouth dramatically improves the result on a face.
  • Color Density uses Polypaint to steer resolution—paint the areas that need density (the face) bright and the low-density areas dark, switch on Color Density, and ZRemesher allocates polygons accordingly.
  • Keep Groups / Detect Edges preserves polygroup boundaries and hard edges, which is gold for armor and hard-surface props.

ZRemesher is great for intermediate meshes, hard-surface props, assets where the topology doesn't need to be perfect, or as a starting point for manual cleanup. But stay honest about it: its automatic flow on a human face is usually not good enough, and the loop structure around the eyes and mouth almost always needs hand fixing. Don't one-click it and assume you're done.

Manual: maximum control. When you need top-tier topology—main characters, hero assets, faces built for nuanced expression—you sit down and retopologize by hand. Tool options:

  • Inside ZBrush: ZSphere topology, the Topology brush, the ZModeler brush.
  • External specialists: Topogun (the old reliable), Maya's Quad Draw, Blender (RetopoFlow or Poly Build), 3ds Max.

Manual is slow, but every edge is one you placed deliberately. Eye and mouth loops, pole positions—all of it under your control. For a face that has to carry refined expressions, this is the only dependable approach.

Road B: Decimation — processing the high-poly to serve the bake

So what is Decimation Master for? Its core job is crushing an unmanageably heavy high-poly down to something you can actually move around:

  • A source for baking normal maps. Baking software—Substance Painter, Marmoset, xNormal—can't swallow a raw multi-million-polygon ZBrush mesh. Decimation Master takes the high-poly down to a few hundred thousand or a couple million polygons (it preserves the silhouette and surface detail beautifully even at heavy reductions), so you can export it for baking.
  • Static props and 3D printing. For objects that never deform, a decimated mesh is fine to use as-is.
  • Quick LODs. Tiered levels of detail for distant models.

Practical options in Decimation Master: run Pre-process first to compute the decimation, use Keep UVs to protect existing UVs through the reduction, and Freeze Border to lock the boundaries in place.

So retopology and decimation aren't an either/or choice—they have separate jobs. Retopology builds a clean low-poly; decimation crushes the high-poly into a bakeable source. A complete character pipeline uses both.

4. The full workflow: a seven-step pipeline from sculpt to shippable asset

String the tools together and a standard game/film character pipeline runs like this.

Step 1: Finish and freeze the high-poly. Confirm every detail is sculpted and there's nothing left to revise. Going back to change the high-poly after you've retopologized is a headache—lock it down first.

Step 2: Decide strategy and budget. Is this a game low-poly or a film asset? Does it need expressions? That determines whether you go automatic or manual, and it sets your polycount target.

Step 3: Retopologize the low-poly. Use manual retopo for the face and deformation zones (ZRemesher guides can assist); ZRemesher is fine for hard-surface and secondary parts. The output of this step is your real low-poly—clean flow, quad-dominant, on budget.

Step 4: Check topology and polycount. Audit it against the principles from Section 2, item by item. Any N-gons? Poles sitting in deformation zones? Are the eye and mouth loops complete? Is the polygon distribution sane? Don't skip this.

Step 5: Project detail (optional but common). Back in ZBrush, subdivide the low-poly a few levels and use Project All to cast the high-poly's detail back onto your clean topology. Now you have a mid-poly with clean flow and full detail—higher bake quality, and easier to tweak on the low-poly later.

Step 6: Unwrap UVs. You need UVs before you can bake. Unwrap the low-poly, lay the islands out sensibly, leave enough padding. Get the order wrong—baking before unwrapping—and everything before it was wasted.

Step 7: Bake the maps. Use the decimated high-poly (or the projected mid-poly) as your high source and the low-poly as the target, then bake normal, AO, curvature, displacement, and so on. The normal map paints the high-poly's pores and wrinkles onto the low-poly surface, so the low-poly looks every bit as refined as the sculpt at a fraction of the polygons.

After that it's into the engine: rig, skin, and shade. The "data monster" that couldn't move a moment ago has finally become an asset you can actually use.

5. The mistakes beginners make every time

Just about everyone trips over these at least once. Knowing them in advance saves you a lot of rework.

  1. Using a decimated mesh as the low-poly. The most frequent error by far. A decimated mesh is all chaotic triangles—it can't be rigged, can't do expressions, and won't unwrap. It's a bake source, not a game low-poly. When you need a low-poly, retopologize.
  2. Triangles where quads belong. Anything that deforms or subdivides needs to stay quad-dominant, or you get broken deformation and subdivision artifacts.
  3. Polycount out of control or badly distributed. Either the low-poly is so dense it defeats the purpose, or the face is too sparse to hold an expression while the back of the head is packed with geometry. Set the budget before you start.
  4. Wrong edge flow in deformation zones. Skip the loops around the eyes and mouth, or run flow perpendicular to muscle movement, and expressions will tear and stretch the moment they animate.
  5. Poles in deformation zones. An N-pole at the corner of the mouth or eye breaks both subdivision and deformation. Keep poles in flat, low-movement areas.
  6. Forgetting to UV before baking. No UVs, no bake. The order is UV first, then bake—don't reverse it.
  7. Mismatched high and low causing bake errors. If the low-poly's shape strays too far from the high-poly, or doesn't fully envelop it, you get intersections and bad projection during the bake. Set the cage and projection distance properly before you bake.
  8. Trusting ZRemesher blindly. Auto-retopo is a helper, not an autopilot—especially on a human face. Always inspect the result and fix the eye and mouth loops by hand.

Wrapping up

Going from high-poly to low-poly is, at heart, a translation: detail that the sculpt stored as raw mesh density gets translated into the far more efficient combination of a low-poly plus maps. In that pipeline, retopology gives the asset a skeleton that can actually move and deform, while decimation crushes the high-poly into a bakeable source. It takes both working together to make a sculpt come alive.

Internalize the one rule—decimation is not retopology—and pair it with the topology principles (quads, edge flow, poles, polygon budget), and you've cleared the most important hurdle there is: the one between "I can sculpt it" and "I can use it."