Why assets go through stages
A game asset is any piece of content the game uses: a character, a tree, a sword, a door. It rarely appears fully formed. An asset passes through a sequence of stages, and the order of that sequence is usually called the art pipeline. The structure exists for a practical reason: changes are cheap early and expensive late. Redrawing a sketch takes minutes; reworking a textured, rigged and animated character can take days.
Studios vary in how they organize this, so treat the stages below as a typical path rather than a standard.
Stage 1: Reference and concept art
Work often starts with a design request: what is this thing, what does it do in the game, and how will the player see it? Artists gather reference images and produce concept art, ranging from quick thumbnail sketches to more finished paintings.
Concept art answers questions before anyone builds anything:
- What is the silhouette, and does it read at a distance?
- What are the main shapes and colors, and do they fit the art style and palette?
- What would the object need to do (open, break, animate)?
A good brief at this stage includes how the asset is viewed. A character seen from far above in a strategy game needs a different design than one shown in close-up. Approval usually happens here, because this is the cheapest point to change direction.
Stage 2: Modeling
For 3D games, a modeler builds the shape in three dimensions. Often there is a rough blockout first, using simple volumes to check proportions and scale in the game itself. Only after that does the detail get added.
The modeler works within a budget, such as how many polygons the asset should use. The budget depends on the platform, the camera distance and the art style; lightweight approaches are discussed under low-poly models. Models are also built with clean surfaces and sensible edge layout, particularly where parts will bend during animation.
For 2D games, the equivalent step is producing the final drawing or sprite at the needed size.
Stage 3: UV mapping and texturing
A flat image cannot wrap around a 3D shape unless the surface is first “unwrapped” into a flat layout. This is called UV mapping. Texturing then paints or generates the surface: colors, patterns, wear, and information about how shiny or rough a material is.
Artists often create several texture layers. One holds color, others describe how light bounces off the surface. Texture size matters, because large images use more memory, and a small prop does not need the same resolution as a main character’s face. Consistency with the project’s color palettes happens at this stage as well.
Stage 4: Rigging and animation
If the asset moves, it needs a skeleton, called a rig. The model is attached to the rig so that moving the bones deforms the surface. Animators then pose and key the motion, drawing on the timing and weight principles covered under character animation. A prop that only sits still skips this stage.
Rigging mistakes show up here: a joint in the wrong place can make a shoulder collapse or a knee twist. These are cheaper to catch with a quick test pose than after dozens of animations have been made.
Stage 5: Export and import into the engine
The finished asset is exported in a file format the game engine reads, then imported. This step often brings surprises. Scale may be off, textures may appear black or stretched, or materials may look different under the engine’s lighting. Teams usually settle conventions early, such as units, naming rules, folder structure and file types, so that every artist exports the same way.
Version control and a shared structure for files help here, because many people touch the same assets. Good naming prevents the common problem of finding “tree_final_v2_REAL” in three places.
Within the engine, the asset might also get:
- Collision shapes, simplified invisible shapes used for physics rather than the detailed model. These connect to how collision detection works.
- Levels of detail, lower-detail versions swapped in at a distance to save performance.
- Materials and shader settings, so it responds correctly to light.
Stage 6: Review, test and revise
Once in the game, the asset is viewed in context. It may look excellent in the modeling software and poor under in-game lighting or from the actual camera angle. Reviewers check readability, style consistency, performance cost and whether it behaves correctly. Feedback loops back to the artist for revision.
Small teams often compress these stages. One person may sketch, model and texture an asset in a single afternoon, and some projects skip concept art for simple props. The stages still exist as questions to answer, even if they are not separate jobs.
Common problems
- Approving too late. Changing a design after texturing wastes work.
- Ignoring the budget. A beautiful model that is too heavy for the target hardware has to be rebuilt.
- Inconsistent style. Assets made by different people drift apart without shared references.
- Skipping in-engine checks. Problems found at import are fixable; problems found near release are costly.
Seeing the pipeline this way also explains why art takes a significant portion of the time in a production schedule, and why planning scope around art capacity is common in small projects.