Support loop (holding edge)

A support loop is an extra edge loop placed close to an edge so that the edge stays tight when the mesh is subdivided. It is also called a holding edge, control loop or supporting edge.

Without support, Catmull–Clark subdivision "rounds off edges, and often this is not what you want" (Blender Manual: Subdivision Surface Modifier).

Three subdivided cubes: one rounded into a blob, one with tight bevelled edges, one with sharp creased edges. — Three cubes with the same Subdivision Surface modifier (level 2). Left: no support loops, so it rounds into a blob. Middle: a bevel adds support loops next to every edge, so the edges stay tight. Right: full edge crease keeps the edges sharp without extra loops.Rendered in Blender 5.2 (Cycles) by the handbook author

#How it works

Subdivision smooths each vertex towards its neighbours. If an edge's nearest neighbours are far away, the corner melts into a broad curve. Put a loop close to the edge and the smoothing has much less room, so the corner becomes a tight radius.

The Blender Manual describes the same control: adding loops near an edge keeps it crisper, and removing them softens it (Blender Manual: Subdivision Surface Modifier). The distance between the support loop and the edge sets the radius of the final bevel.

Three cross-sections of a subdivided box cage. With no support loops the result is nearly round. With support loops placed close to each corner the result has tight rounded corners. With full creases the corners stay perfectly sharp. — Cross-sections computed with the curve form of Catmull–Clark subdivision. Support loops (centre) give a controllable radius; a full crease (right) gives no radius at all.Diagram by the handbook author

#Three ways to keep an edge tight

Support loops: plain geometry, added by loop cuts or by insetting and bevelling.
Creases: a sharpness value on the edge. In OpenSubdiv, 0 has no effect and 10 makes the edge "completely sharp" (OpenSubdiv documentation: Subdivision Surfaces). A higher crease value makes a Blender edge "more resistant to the smoothing effect" (Blender Manual: Subdivision Surface Modifier). Cinema 4D has equivalent edge weighting, with options for how weights blend between edges (Cinema 4D R23 Help: Subdivision Surface).
Bevels: chamfer the edge in the cage, by hand or with a bevel modifier, before subdividing. The bevel's extra segments act as support loops with an exact, even width. See bevels and chamfers.

Different viewsSupport loops, creases or bevels?

Support-loop advocates value predictability. FrankPolygon on Polycount describes high-poly subdivision topology that controls smoothing with support loops, keeping any smoothing artefacts away from visible shapes (Polycount: Need opinion on what a good topology is). Geometry exports the same way to every baker and engine.

Crease advocates point to cleaner, lighter cages. The OpenSubdiv documentation treats semi-sharp creases as a core feature and says that, since real edges are never infinitely sharp, "it is often preferable to set the sharpness lower" than the maximum (OpenSubdiv documentation: Subdivision Surfaces). The risk is that crease data may not survive every export.

Bake-focused artists care mostly about the size of the result. Simon Péloquin advises that you "exaggerate your chamfers" so they read at normal-map resolution (80 Level: Best Practices for Hard Surface Normal Map…). A bevel modifier makes that width easy to control and change.

In practice: use bevels (or bevel-generated loops) when you want a consistent radius across a hard-surface model, hand-placed support loops for special cases, and creases for quick iteration inside one tool. If a file must leave your tool, convert creases to geometry first or check that the target reads them.

#Common mistakes

Support loops running everywhere. Each loop continues round the whole mesh. End loops at a pole in a flat area, or use creases locally.
Uneven spacing. Different distances on each side of a corner give lopsided bevels.
Pinching at corners. Where three supported edges meet, the corner often needs extra cuts or a careful bevel to avoid a pinch.
Too tight for the bake. A 1 mm radius can vanish in the normal map.

edge loop · edge ring · subdivision surface modeling · bevels and chamfers · hard-surface modeling · the high-to-low workflow

#Further reading and watching

Blender Manual: Subdivision Surface Modifier (2.83)

"Keeping Sharp Edges" covers loops and creases. Beginner, free.

DocsBeginnerFree

OpenSubdiv: Subdivision Surfaces

see "Semi-Sharp Creases". Advanced, free.

DocsAdvancedFree

80 Level: Best Practices for Hard Surface Normal Map Baking

why bevel width matters for bakes. Intermediate, free.

ArticleIntermediateFree

References

Blender Foundation · Subdivision Surface Modifier · Blender Manual (2.83), 2020 · docs · accessed 2026-10-20

Pixar Animation Studios · Subdivision Surfaces · OpenSubdiv documentation (source file on GitHub) · docs · accessed 2026-10-20

Maxon · Subdivision Surface · Cinema 4D R23 Help · docs · accessed 2026-10-20

Polycount forum (replies by FrankPolygon and GlowingPotato) · Need opinion on what a good topology is · Polycount, 2020 · forum · accessed 2026-10-20

Simon Péloquin (guide); Arti Sergeev (editor) · Best Practices for Hard Surface Normal Map Baking · 80 Level, 2018 · article · accessed 2026-10-20