If 3D textures feel like a pile of random PNGs, start with fundamentals, not software menus. A texture is either color (what the eye reads as pigment) or data (numbers that drive roughness, metalness, or fake height). PBR is just a consistent way to plug those images into a lighting model. This lesson is the map literacy you need before Blender, Unreal, or V-Ray will make sense.
Color maps vs data maps
Albedo (also called base color) is a color map. It should look like a flat, evenly lit photograph of the surface—no highlights, no contact shadows. Roughness, metalness, ambient occlusion, and height are data maps: grayscale images the shader reads as values, not as pretty pictures. Normal maps are data too, even though they look blue-purple. If you color-correct a roughness map as if it were a photo, you break the material. If you leave lighting in albedo, the render will fight every new HDRI. Deeper map roles: albedo, normal, and roughness and diffuse vs albedo.
The four maps that matter first
Albedo — pigment. sRGB. Roughness — 0 is mirror, 1 is chalk. Linear / Non-Color. Normal — fake bumps; use the engine’s Normal Map node and the right convention (OpenGL vs DirectX). Metalness — 0 dielectric (wood, stone, paint), 1 metal. Most free packs, including Locker3d, use this metalness workflow. AO and height are extras: AO can multiply into cavities, height can drive displacement or parallax. You can produce a believable still with only the first three maps. Full list: what are PBR textures.
Color space is not optional
Wrong color space is the number-one beginner bug. In Blender, Image Texture nodes default to sRGB. That is correct for albedo and wrong for everything else. Set roughness, metallic, normal, AO, and height to Non-Color. In Unreal, use sRGB on base color only. In Unity, uncheck sRGB on data maps. If a material looks too shiny, too dark, or “wet,” check this before you tweak lights. Common fixes: common PBR mistakes.
Scale, UVs, and tiling
A perfect 4K oak still looks fake if the planks are 80 cm wide on a table and 8 cm on the floor. Measure. Use a reference object (a 2-meter human or a credit card). Seamless tiles need even UVs; stretched islands stretch the grain. For hard-surface blocks, a box or triplanar projection is faster than a bad unwrap—see triplanar mapping and how to tile textures without seams. Resolution: 1K for distant props, 2K for most sets, 4K for hero close-ups (resolution guide).
Three practice exercises
1) Download one wood and one concrete pack from Locker3d. Apply each to a UV cube. 2) On the wood, invert roughness and note how the surface dies—then restore it. 3) Make a metal from a metal pack and a painted metal by putting metalness at 0 and using the same albedo as paint. Light with a single HDRI. That is a complete fundamentals loop. Wiring: apply PBR textures in Blender. Next reading: PBR textures for beginners and the blog.
Frequently asked questions
What is the first texture map I should understand?
Albedo (base color): the surface color with no lighting baked in. If albedo is wrong—too dark, too shiny, or full of shadows—every other map fights it. Get albedo right, then add roughness and a normal map.
Why do my textures look wrong in Blender?
Usually color space. Albedo must be sRGB. Roughness, metalness, and normal must be Non-Color. The normal map also needs a Normal Map node, not a direct link into the BSDF Normal input.
How do I practice without buying textures?
Download one CC0 pack from Locker3d (wood or concrete), apply it to a simple UV-unwrapped cube and a plane, then change only roughness or scale. Repeat with a metal. That loop teaches more than collecting 200 unused files.