PBR helper
Normal Map Generator
Turn a height map or a photo into a tangent-space normal map, with adjustable surface strength. Runs in your browser — the image never leaves your machine.
Output is an 8-bit PNG in tangent space at the source resolution, ready for Unreal, Unity, Blender or three.js. No upload, no sign-up.
Why wrapping matters
The gradient is sampled with wrap-around, so a texture that already tiles produces a normal map that also tiles. It will not repair a broken source, but it will not add a new break at the border either.
A base colour texture tells a surface what colour it is. It cannot tell the renderer that the mortar between the bricks sits 4 mm lower, that the grain in the wood runs left to right, or that the stone is pitted. That information lives in a normal map: an image where red and green record the surface direction and blue records how far it faces the viewer.
This tool derives one from any image. Feed it a greyscale height map — the honest way, where you decided what is high and what is low — or feed it a photograph and let brightness stand in for height.
Greyscale or photo: pick deliberately
A greyscale height map is the better input. White means high, black means low, and you control it. Paint it, generate it, or take the luminance channel of a bump map you already used. Because you control the values, the normal map describes the surface you intended rather than the lighting that happened to fall on it.
A photograph is the fast input. It works well on surfaces where brightness really does follow depth: concrete, stone, rough plaster, bark. It works badly on anything glossy, anything photographed with a strong side light, and anything where a dark stain is a colour difference rather than a hole. The usual symptom is a normal map that lights up around a coffee-coloured patch as though it were a crater.
What the strength control changes
The strength slider multiplies the gradient it finds. At low values you get a soft, almost invisible relief — right for plaster, painted drywall, fabric. At high values edges become hard and the surface reads as deeply grooved, which suits stone courses, brick and machined metal.
There is a failure mode worth knowing: pushed too far, the normals on opposite sides of an edge point in conflicting directions and the surface starts to look metallic or “plastic”, because the renderer is computing reflections that no real surface would produce. If the render looks shiny rather than bumpy, the strength is too high, not the map.
Keeping the maps consistent at the seam
A normal map inherits every problem the height image had. If the height map does not tile, the normals do not tile either, and the seam shows as a sudden change in the direction of the light across the join — often more obvious than a colour seam, because the eye is very good at spotting a change in shading direction.
So the order matters: make the height (or the photo) tile first, then derive the normal map, and derive every other map from the same tileable source. If you blend the albedo over 14% and generate normals from an unblended version, the bricks will match in colour and disagree in lighting, which reads as a faint bruise along the join.
The tool samples the gradient with wrapping, so a texture that already tiles produces a normal map that tiles too. That does not repair a broken source — it only avoids adding a new break at the border.
Where the map goes
In a PBR material the normal map goes into the Normal input, tagged as tangent space — which is what this tool outputs. Nothing else changes: base colour in base colour, roughness in roughness. Do not put it in the base colour slot and multiply it; that produces grey-blue colour with no relief at all, a mistake that shows up as a strangely tinted surface under an otherwise correct light rig.
Export is an 8-bit PNG at the source resolution, which is what every game engine and DCC package accepts without conversion. For a full material set, run the tileable image through here, generate roughness from the luminance in your editor, and keep the three maps at identical dimensions — mismatched sizes are the second most common reason a material seams after the maps looked fine individually.
Normal map questions
Can I make a normal map from a photo?
Brightness stands in for height, so dark areas become low and light areas become high. It works well on concrete, stone, plaster and bark. It works badly on glossy surfaces and on photos lit strongly from one side, where the light is mistaken for shape.
Why is the output blue-purple?
In the normal map's RGB, the channels encode direction rather than colour: red is the horizontal component, green the vertical, blue how directly the surface faces the viewer. A flat surface is (128, 128, 255) — that pale blue is the signature of a normal map.
How strong should the normal map be?
Raise it until the relief reads at the distance the surface will be seen from, then stop. If the material starts looking shiny or metallic rather than bumpy, the strength is too high: the normals are conflicting rather than describing a surface.
Is the output tangent space or object space?
It outputs tangent-space normals, the default expectation of Unreal, Unity, Blender, three.js and every glTF viewer. Object-space normal maps are a narrow special case and are not what you want for a standard PBR material.
Can I use this for a seamless material?
Yes, but make the source tileable first — generate the normal map from the blended image, not from the original. Deriving normals from an unblended version while the colour is blended produces a visible change in light direction along the seam.