Ways to build a 3D model

There is no single "right" way to model. Most game assets are built with a mix of methods, and each method trades speed, control, precision and how much cleanup it leaves for later.

This page maps the main approaches, compares them in one table, and points to the pages that go deeper. If you are new, read box modeling and topology first: almost every other method still ends in a polygon mesh you have to understand.

#The common end product: a triangle mesh

Whatever you start with, a real-time game engine ultimately draws triangles. Even Unreal's Nanite system works on ordinary static meshes made of triangles (Unreal Engine documentation: Nanite Virtualized Geometry). Every approach below therefore leads to the same result: a mesh with good silhouette, sensible UVs and a polygon budget that fits the platform.

Approaches differ in where the shape comes from:

• You push polygons directly: box modeling, poly-by-poly, subdivision surface modeling.
• You describe exact surfaces: CAD and NURBS.
• You shape a dense surface like clay: sculpt-first.
• You write rules that generate the shape: procedural modeling.
• You reuse or capture existing shapes: kitbashing, photogrammetry, AI generation.

#The approaches

#Box modeling

You start from a primitive (usually a cube or cylinder) and refine it with extrudes, insets and loop cuts until it reads as the object. It is the default way most people learn polygon modeling, and it pairs naturally with subdivision. See box modeling.

#Poly-by-poly (edge extrusion)

Instead of carving a block, you build the surface outward one face or edge at a time, often over a reference image or a sculpt. This gives exact control over edge flow, which is why it is closely related to retopology: rebuilding a cleaner mesh over a dense one to keep nearly the same shape (Wikipedia: Retopology).

#Subdivision surface modeling

You model a low-resolution "cage" and let a subdivision algorithm, almost always Catmull–Clark, compute the smooth surface (OpenSubdiv documentation: Subdivision Surfaces). Blender's Subdivision Surface modifier, for example, uses Pixar's OpenSubdiv library as its backend (Blender Manual: Subdivision Surface Modifier). In games this is mostly used to make high-poly source meshes for baking. See subdivision surface modeling and support loop.

#Hard-surface boolean workflows

You add and subtract shapes with booleans, then clean up with bevels and weighted (custom) normals. This is fast for mechanical forms and is the backbone of the the mid-poly workflow. See hard-surface modeling.

#CAD and NURBS

CAD tools describe surfaces mathematically and convert ("tessellate") them to polygons on export. Plasticity describes itself as focused on "artistic workflows" and built on the Parasolid and xNURBS kernels (plasticity.xyz: Plasticity). MoI offers "precision and freeform NURBS drawing tools" and n-gon mesh export (moi3d.com: MoI 3D). Autodesk Fusion is a cloud-based product development platform that combines parametric, direct, surface and freeform modeling with CAM (autodesk.com: Autodesk Fusion overview). See CAD and NURBS modeling for games.

#Sculpt-first

You sculpt a dense mesh, then create a game mesh from it by retopology or decimation and bake the detail down. ZBrush is the best-known sculpting package; Maxon pitches it at character, creature and concept artists (maxon.net: ZBrush). Digitally sculpted models "often have a high number of polygons and poor edge flow," which is why retopology exists (Wikipedia: Retopology). See digital sculpting and remeshing.

#Procedural modeling

You build a network of operations instead of editing the mesh by hand, so you can change an early step and the rest updates. In Houdini, geometry nodes live inside Geo objects and "generate geometry", and finished networks can become reusable digital assets (Houdini documentation: Modeling). Blender's node system is now part of everyday modeling: since 4.1, its "Smooth by Angle" feature is itself a modifier node group asset (Blender Developer Documentation: Modeling — Blender 4.1 release notes). See procedural modeling and vegetation and procedural tools.

#Kitbashing

You assemble new objects or scenes from a library of existing parts. Commercial libraries such as KitBash3D sell themed sets of "over 20,000 premium 3D assets" meant to work together (kitbash3d.com: KitBash3D). In environment work the same idea appears as reusing your own modular kits. See kitbashing.

#Photogrammetry and scanning

You reconstruct real objects from photographs. Scans are dense, so they usually need retopology or decimation for games, unless the engine can render them directly: Unreal's documentation says Nanite makes it possible to import "ZBrush sculpts and photogrammetry scans" as source art (Unreal Engine documentation: Nanite Virtualized Geometry). See photogrammetry and photogrammetry and scanning tools.

#AI-assisted generation

A growing number of tools generate meshes from a text prompt or an image. Sloyd, for example, markets text-to-3D and image-to-3D generators and promises "game-ready assets in seconds" (sloyd.ai: Polygon Count). These are vendor claims. Before using any generated mesh in production, check its topology, UVs, scale and licence terms the same way you would check a bought asset.

#Comparison

The "when to use" and "limits" columns are practical guidance, not rules. Many studio pipelines combine three or four of these on a single asset.

#How to choose

Ask four questions:

1. Will it deform? Characters and cloth need clean edge flow. Static props do not.
2. Is it hard or soft? Mechanical shapes suit subdivision, booleans or CAD. Organic shapes suit sculpting or scanning.
3. How many variations do you need? Many similar objects suggest procedural or modular methods.
4. Where does the detail end up? If it is baked into a normal map, the high-poly can be messy as long as it bakes cleanly. If the mesh is rendered directly (for example with Nanite), the final geometry is what players see (Unreal Engine documentation: Nanite Virtualized Geometry).

#Further reading and watching