Skip to main content
All posts
Material workflows

Blender to glTF Normal Map Looks Wrong? Fix the Export

Trace broken normal shading from Blender's Non-Color setting through the glTF normal texture and target viewer.

Quick answer

For Blender to glTF, load the normal texture as Non-Color, connect it through a tangent-space Normal Map node to Principled BSDF, and export a Y+ tangent normal. Test the exported GLB in a second viewer. If a seam follows mesh edges, check UVs, tangents, and triangulation before changing green.

Which data settings survive export?

InputBlender setupglTF expectation
NormalNon-Color → Normal Map → Principled NormalY+ tangent space
Base ColorsRGB → Principled Base ColorsRGB color texture
RoughnessNon-Color → RoughnessGreen of metallicRoughnessTexture
MetallicNon-Color → MetallicBlue of metallicRoughnessTexture
OcclusionData texture with export-supported hookupRed of occlusionTexture
A purple tangent normal texture beside a cube representing a Blender-to-glTF export
A normal texture passes through a tangent-space Normal Map node before export.

How do I find the export mismatch?

  1. On a UV plane, test a clear directional bump with the texture treated as Non-Color. Select tangent space on the Normal Map node and use a known Y+ source.
  2. Check that the texture’s UV set matches the surface and the normal node’s chosen UV map. Give mirrored islands a deliberate test so you see tangent mismatches before exporting.
  3. Export a small GLB with the mesh, material and image. Open it in an independent glTF viewer. If the independent viewer is correct, inspect the target application’s material assignment and loader settings.
  4. When using Three.js, compare the material loaded from GLB with a manually created material. Loading images manually can require matching texture orientation and color settings. A mismatch on every texture can indicate upload orientation. A normal-only mismatch can indicate the green direction or texture decode.

Where do packed occlusion and roughness go?

The metallic-roughness texture reads roughness from green and metalness from blue. Occlusion reads red through a separate material texture property which can reference the same image. Ensure the exporter recognizes both uses. A correct-looking ORM file can still export with missing AO if the material has no recognized occlusion hookup. When creating the packed source, confirm the channel layout independently before exporting the 3D model.

Open the free browser tool to try this workflow with your own texture.

Frequently asked questions

Should I invert green for GLB?

Use the authored green convention to decide. glTF uses Y+. Leave a Y+ file unchanged, or convert a Y− source once. Confirm on a known ridge before editing multiple assets.

Why does the normal differ on a low-poly triangulated model?

A baker and viewer may interpolate tangent bases across different triangle diagonals. Triangulate consistently before baking and export mesh tangents when the receiving pipeline supports them.

References