Normal Map in Blender
Make a normal map from any texture here, then connect it in Blender's Shader Editor in four steps. Below: the settings that matter and what to fix when it looks wrong.
- Exports OpenGL normal maps, the convention Blender reads
- Runs in your browser: files are not uploaded
- Height, AO and roughness maps from the same image
Blender reads OpenGL normal maps (green up), so the generator on this page is already set to OpenGL Y+.
Drag anywhere to move the light
Green channel read the wrong way: bumps look like dents. Match the export to your engine.
Advanced settings
Exports above 1024 px come with Pro.
Pro is $6.00 a month or $48.00 a year. It adds exports up to 4096 px, 16-bit height maps, batches of up to 200 files in one ZIP, and batch green-channel flips. Everything you can do now stays free.
Pro checkout is not open yet. Nothing on this site takes payment until it is.
Drop files or a whole folder here
Uses the settings above. Free: 3 files per batch at up to 1024 px. Pro: up to 200 files at up to 4096 px.
How to use a normal map in Blender, step by step
Generate the map above (or use one you have), download it as OpenGL, then in Blender:
- Open the Shader Editor with your object selected, and make sure it has a material with a Principled BSDF. The object needs a UV map; the Normal Map node uses it to know which way is "up" on the texture.
- Add an Image Texture node (Shift + A → Texture → Image Texture), open the downloaded PNG, and set its
Color SpacetoNon-Color. This is the step most often missed. - Add a Normal Map node (Shift + A → Vector → Normal Map). Leave
SpaceonTangent Space. Connect Image TextureColor→ Normal MapColor. - Connect Normal Map
Normal→ Principled BSDFNormal, and switch the viewport to Material Preview or Rendered. Adjust the node'sStrength(1.0 by default) if the relief is too faint or too strong.
Blender's node setup has worked this way since Blender 2.8, so these steps apply to every current version. Page last updated 2026-11-18.
Normal map not working in Blender? Symptoms and fixes
People search for this because something already looks wrong. Find your symptom:
| What you see | Cause | Fix |
|---|---|---|
| Nothing changes at all | Viewport is in Solid mode, which ignores material textures | Switch to Material Preview (Z → Material Preview) or Rendered |
| Nothing changes, even in Rendered | No UV map, or every face unwrapped onto one point | UV Editing workspace → U → Smart UV Project (or unwrap properly), then check the node's UV Map field |
| Surface goes dark, blotchy or rainbow-shaded | Image plugged straight into the BSDF Normal input | Put a Normal Map node between them |
| Relief too strong, light looks bent | Image Color Space left on sRGB | Set Color Space to Non-Color |
| Light from above makes bumps look like dents | The map is DirectX (Y−), made for Unreal or 3ds Max | Download the OpenGL version here, or in Blender: Separate Color → Math (1 − G) → Combine Color before the Normal Map node |
| Hard lines along UV seams | Mirrored or rotated UV islands, or a map that is not tileable | Turn on Wrap edges here for tiling textures; avoid mirrored islands for normal-mapped areas |
| Everything looks pressed in from every side | The height was read upside down (dark parts of the texture are the raised ones) | Tick Invert height under Advanced and download again |
The other maps in Blender
The generator also exports height, AO and roughness. In Blender:
- Roughness: Image Texture (Non-Color) → Principled BSDF
Roughness. It is an estimate from brightness; adjust with a Map Range node if the material looks too glossy or too dull. - AO: Blender's Principled BSDF has no AO input. For a painted-in look, multiply it into Base Color with a Mix node set to Multiply at a low factor. Skip it for Cycles renders, which compute their own occlusion.
- Height: Image Texture (Non-Color) → Displacement node → Material Output
Displacement. In Cycles, real displacement also needs the material's displacement method set to Displacement and enough mesh subdivision.
Normal maps in Blender: questions
Do I need the Normal Map node, or can I plug the image into the Normal input?
You need the node. The Principled BSDF's Normal input expects a direction in world space, while the image stores directions in tangent space as colors from 0 to 1. The Normal Map node does that conversion using the mesh's UVs. Plugged in directly, the surface turns dark and blotchy.
Should I use a normal map or the Bump node in Blender?
For renders made in Blender, the Bump node with a height map is fine and lets you change strength freely. For anything exported to a game engine or another app, use a normal map: Bump is computed by Blender's shader and is not exported. You can chain them: Normal Map node into the Bump node's Normal input adds height detail on top.
Does the normal map survive glTF export?
Yes. glTF uses the same convention as Blender (OpenGL, green up), and the glTF exporter picks up an Image Texture that feeds a Normal Map node into the Principled BSDF, including the node's Strength.