A texture atlas is a single image holding the textures of many objects, laid out side by side, so those objects can share one material. Each object's UVs point at its own region of the image. In games it is one of the oldest and most reliable ways to cut draw calls.
Why it matters
Renderers change state between materials, and every state change is a draw call. Fifty props with fifty materials is fifty draw calls; fifty props sharing one atlas can be a handful. On mobile and VR, where draw call budgets are tight, this is often the difference between shipping and not.
The costs
- Resolution is shared. Every object on the atlas divides the same pixels. A hero prop deserves its own texture.
- Tiling is lost. An atlased surface cannot repeat, because repeating would sample its neighbours. Anything that needs to tile — a long wall, a floor — needs a separate tiling material.
- Editing is coupled. Changing one object's texture means republishing the atlas.
- Mip bleeding. At small mip levels, neighbouring islands blur into each other. Padding between islands is not optional.
What to atlas
Small props, clutter, kit pieces that share a visual family, anything instanced heavily. Not: hero assets, characters, anything tiling, anything needing independent iteration.
Practical rules
- Pad generously. Enough that the smallest mip level still separates islands.
- Keep texel density even. An atlas mixing a crisp object and a blurry one looks worse than two separate textures.
- Group by material family. Metal with metal, fabric with fabric — atlases tend to share roughness behaviour.
How to make one
- Choose the set. Props that appear together and share a material type — the clutter for one room, a kit of crates and barrels.
- Unwrap them into one shared layout. In Blender, select every object, enter Edit Mode and pack the islands together, so all of them land in one 0-to-1 square without overlapping.
- Leave padding between islands — several pixels at full size, more if the atlas will be viewed small.
- Bake each object's existing texture into its region, or paint the atlas directly if the objects are new.
- Give every object the one material that uses the atlas, and check each still lines up.
Atlas, trim sheet or texture array?
An atlas gives each object its own unique region. A trim sheet gives many objects the same reusable strips, so it also covers surfaces that tile. A texture array keeps separate same-sized textures behind one material and avoids bleeding entirely, at the cost of engine and shader support. Props suit an atlas; architecture suits a trim sheet.
With generated assets
Generated models each arrive with their own texture, which is the opposite of an atlas. Consolidating a set into one is a deliberate step: re-unwrap the group into a shared layout, then bake each source texture into its allotted region.