01 / 21

UV vs. Procedural
Coordinates

Understand how Blender maps textures onto 3D surfaces using UV unwrapping and generated/object coordinates: when to use each, and why it matters.

Blender

What Are Texture Coordinates?

Every point on a 3D surface needs a way to look up its color, bump, or roughness from a texture. Texture coordinates are the mapping system that tells Blender: "For this point on the mesh, read this pixel from the texture."

In Blender's Shader Editor, you choose a coordinate system via the Texture Coordinate node. The three most common outputs are UV, Generated, and Object.

Two Families of Coordinates

UV Coordinates
Manually unwrapped. Each face is "flattened" onto a 2D plane. Stored per-mesh. Gives you pixel-perfect control.
Procedural Coordinates
Auto-calculated from position. Generated and Object coordinates need no unwrapping: they derive \( (x, y, z) \) directly from the mesh or world.

UV Mapping: Flattening a Surface

3D Mesh Unwrap UV Space U V (0,0) (1,0) (1,1) (0,1)

UV coordinates range from \( (0,0) \) to \( (1,1) \). Each polygon face is "flattened" into the UV square. The U axis runs horizontally, the V axis vertically. Where you place these "islands" determines which pixel of the texture each face reads.

Generated vs. Object Coordinates

Generated (0,0,0) (1,1,1) Bounding box = 0 to 1 Moves with mesh topology Object Origin +Z +X +Y Object origin = (0,0,0) Moves with object transform

The Core Mapping Rule

1
UV: \( \text{Coord}(P) = (u, v) \) from the unwrapped layout. Stored per-vertex.
2
Generated: \( \text{Coord}(P) = \frac{P - P_{\min}}{P_{\max} - P_{\min}} \), normalized to the bounding box.
3
Object: \( \text{Coord}(P) = M^{-1} \cdot P_{\text{world}} \), the inverse object-transform applied to world position.

Shader Editor: The Node Flow

Texture Coordinate UV Generated Object Mapping Location Rotation Scale Image / Noise Vector Color / Fac BSDF

The flow is always: Coordinate source → optional Mapping transform → Texture lookup → Shader. The coordinate type you choose at the first node determines the entire behavior.

Key Distinction: Stored vs. Computed

UV Coordinates Generated / Object
Source Stored per-vertex in mesh data Computed at render time
Requires unwrap? Yes No
Deforms with mesh? Yes (follows vertices) Yes (stretches with mesh)
Best for Image textures, painted details Procedural noise, patterns
Precision Pixel-perfect (artist controls seams) Automatic but no seam control

When to Use Each Type

UV
Character skins, logos, decals, hand-painted textures, photographic textures on specific faces.
Generated
Quick procedural noise, prototype materials, patterns that should "stick" to the mesh shape during animation.
Object
World-space patterns (marble veins, wood grain), matching textures across multiple separate objects via a shared empty.

Step-by-Step Approach

1
Identify the texture type. Is it an image file or a procedural node (Noise, Voronoi, Wave)?
2
Image texture? You almost certainly need UV coordinates. Unwrap the mesh first (Edit Mode → U → Unwrap).
3
Procedural texture? Start with Generated for simplicity. Switch to Object if the pattern must stay fixed in world space.
4
Add a Mapping node between the Coordinate and Texture nodes to adjust Location, Rotation, and Scale of the pattern.
5
Test with animation. Move/deform the object. Does the texture slide? If so, re-evaluate your coordinate choice.

Example 1: Brick Wall Texture

Brick Texture Node Best Coordinate? Generated ✓ Brick Texture is procedural. No image file needed. Pattern auto-fills the mesh. UV unwrap: not required

Example 2: Character Skin

3D Character UV Unwrap Head Body Arm L Arm R Leg L Leg R UV Layout → Image Texture

Example 3: Shared Marble Across Objects

Cube A Cylinder B Empty (Shared ref) Object Coordinates → shared Empty Both objects sample the same marble volume in world space

Moving an Object: What Happens?

Generated Texture moves with mesh ✓ Object Texture slides through mesh ✕

Common Mistakes

✕ Using UV for Procedurals
Unwrapping a mesh just to apply a Noise Texture is wasted effort. Generated or Object coords work without any UV map.
✕ Using Generated for Images
An image texture on Generated coords stretches unpredictably. The bounding box doesn't match the artist's intended layout.
✕ Ignoring Texture Sliding
Using Object coords on an animated character makes the texture "swim." The pattern stays fixed while the mesh moves through it.

Summary: Coordinate Comparison

UV Generated Object
Setup Manual unwrap Automatic Automatic
Range \( 0 \) to \( 1 \) (UV space) \( 0 \) to \( 1 \) (bounding box) Unbounded (local space)
Sticks to mesh? ✓ Always ✓ Yes ✕ Slides
Best for Images, paintings Procedural, quick World-space patterns
Multi-object? Each needs own UV Per-object bounding box ✓ Shared via Empty

Question 1 of 5

You want to apply a hand-painted color map to a game character. Which coordinate type should you use?

Question 2 of 5

When using Object coordinates, what happens to the texture when you move the object in the viewport?

Question 3 of 5

Generated coordinates map the mesh's bounding box to which range?

Question 4 of 5

You want two separate objects to share the same continuous marble vein pattern as if carved from one block. What is the best approach?

Question 5 of 5

A Noise Texture is plugged into a Principled BSDF. No Texture Coordinate node is connected. Which coordinate system does Blender use by default?