Skip to main content
All posts
Practical guides

Roughness vs Smoothness Maps: Invert and Calibrate PBR Reflections

Convert roughness to smoothness and verify reflection width, channel placement, and linear import.

Quick answer

Roughness controls how broadly a surface scatters reflections. Smoothness is its inverse in common game-material workflows. Convert in linear values with smoothness = 1 − roughness, or subtract each 8-bit sample from 255. Check which channel the shader uses and compare under a light that produces visible reflections.

What roughness values should I try first?

Example surfaceStarting roughnessComplementary smoothnessWhat to compare
Very calm water0.02–0.120.88–0.98Narrow environment highlights
Polished metal0.08–0.250.75–0.92Bright reflection and fine grain
Finished wood0.3–0.650.35–0.7Clear finish versus bare grain
Dry concrete0.6–0.90.10–0.4Broad reflection and subtle variation

These are visual starting ranges for conventional normalized shader controls. Surface finish and lighting matter more than the object name. A wet concrete patch can behave very differently from an adjacent dry patch.

Polished metal and matte stone spheres showing narrow and broad reflection highlights
Reflection width makes a channel inversion easier to diagnose in a neutral scene.

How do I do the conversion and confirm it worked?

  1. Decide whether the target reads roughness or smoothness. Unreal generally uses Roughness. Unity HDRP uses Smoothness in Mask Map alpha.
  2. Invert the actual grayscale data. Roughness 0.2 becomes smoothness 0.8. In an 8-bit texture, a stored value of 51 becomes 204.
  3. Use a data-texture setting or disable sRGB. If the source is packed ORM, use the texture channel packer to map and invert the channels for HDRP.
  4. Test two patches with clearly different values under a large light and an environment with identifiable features. Observe how the reflection shape changes while keeping metalness and exposure stable.
  5. Check the asset in the target build. If the apparent transition looks different, review compression and mip levels before rebuilding the texture.

Why can the same number look different across shaders?

Renderers can use different BRDF models, roughness remapping, and reflection filtering. Perceptual roughness and the internal microfacet parameter are often related nonlinearly. Invert the authored grayscale value once when moving to a shader that expects its complement. Let the shader apply its own internal math.

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

Frequently asked questions

Can I invert the entire RGB image to get smoothness?

Use only the roughness channel. Inverting every component of a packed image also changes occlusion and metallic data, which breaks the material.

Should I use a brighter roughness map for a softer highlight?

For a conventional roughness map, higher values usually scatter the highlight more broadly. For smoothness, higher values sharpen it. Confirm by testing a solid swatch.

References