The high-to-low workflow

In the high-to-low workflow you build two versions of an asset: a detailed high poly that can be as dense as you like, and an efficient low poly that goes into the game. You then bake the high poly's surface into texture maps, above all a normal map, so the low poly looks far more detailed than its geometry. Matthew Murchison summarises the pairing as a low poly with a good silhouette plus a high poly baked to a normal map (ArtStation blog: Leveraging Multiple Workflows).

#The pieces

• High poly. The source of detail. It can be built with subdivision, booleans and bevels, CAD, or sculpting. Topology barely matters: in one Polycount reply, "it doesn't need to have great topology, it's going to be used to bake down onto a low poly and that's it" (Polycount forum: Advice for solving various normal map/edge…). Small details are often floaters.
• Low poly. The game mesh. It owns the silhouette and needs clean UVs. Silhouette-defining detail belongs here; detail that does not affect the silhouette can go into the bake (Polycount forum: I need some advice).
• Cage. An inflated copy of the low poly that tells the baker where rays start and how far they search. See bake cage.
• Bake. Usually normal, ambient occlusion and curvature, plus ID masks for texturing. See baking and fixing baking artefacts.

#Naming conventions for matching

Bakers need to know which high-poly pieces belong to which low-poly pieces, especially on assets with many parts. Matching by name is the usual solution. Marmoset Toolbag's Quick Loader uses suffixes: a community SmartBaker plug-in lists "_High - for High polygon meshes" and "_Low - for Low polygon meshes" (Polycount forum: Marmoset Toolbag 3 - SmartBaker). Marmoset's EarthQuake describes variant naming such as "Object_High/Low_Variant" for several pieces sharing a group (Polycount forum: Marmoset Toolbag 3 - SmartBaker). A Blender bridge add-on follows "naming rules as for Marmoset Toolbag's QuickLoader" and creates bake groups from objects with a "_low" suffix (Superhive Market: Blender <-> Marmoset Toolbag - Baker Bridge).

A simple, reliable scheme for any baker:

Name parts once, early, and keep names identical across files. Mismatches usually come from renaming at bake time. See naming conventions.

#Exploded bakes

When separate parts sit close together, rays meant for one part can hit its neighbour. That produces projected bits of the wrong part and dark AO where parts touch. The usual fix is an exploded bake: move each matched high and low pair apart by the same offset before baking, then put them back. Some bakers, such as Marmoset Toolbag, instead organise matched high and low pairs into bake groups by name (Polycount forum: Marmoset Toolbag 3 - SmartBaker); check your baker's documentation for how groups affect projection. Either way, decide on purpose which contact shadows you want in the AO. See fixing baking artefacts.

#Step by step

1. Block out the shape at real scale (see blockout and units, scale and axes).
2. Build the high poly. Make bevels wider than looks natural; one Polycount reply advised bevels "over double the current size/strength" to bake cleanly (Polycount forum: Advice for solving various normal map/edge…).
3. Build the low poly from the blockout or by retopology. Spend triangles on the silhouette.
4. UV the low poly. Split UVs at hard edges and keep padding (see UV packing and padding).
5. Name and group high, low and cage meshes.
6. Bake, inspect every map, and fix artefacts with cage edits, skew painting or by moving floaters.
7. Texture using the baked maps as masks.

If you make the high poly in a CAD tool, export it dense: Plasticity's OBJ export recommends a face plane tolerance of 0.0001 for high polys versus 0.01 for low polys (Plasticity documentation: Export OBJ).

#When high-to-low is the better choice

• Small props and hero assets with lots of unique detail. Patscheider keeps conventional high-low for small hero props, heavily varied materials and organic shapes (ArtStation blog: Quarry Bank Mill 3D #08 The mid-poly workflow).
• Mid-distance assets. Murchison uses baked meshes where the camera stays at a distance, such as facades, because the approach is familiar to teams and well supported by tools such as Substance Painter (ArtStation blog: Leveraging Multiple Workflows).
• Tight triangle budgets. A baked low poly is the cheapest way to show bevelled edges at runtime.
• Unique wear and damage. Sculpted dents and chips are captured directly in a bake.

It is less suitable where assets are huge (the bake spreads too thin), change often (every change means a re-bake), or are reused in many configurations. Angelic switched to mid-poly so feedback and geometry changes would not mean re-rolling low and high polys (80 Level: Creating Assets Within the Mid-Poly Workflow…). With Unreal's Nanite, Epic recommends "high-poly detailing rather than baking detail into normal map textures" (Unreal Engine documentation: Nanite Virtualized Geometry in Unreal Engine). See the mid-poly workflow and virtualised geometry.

#Further reading and watching