A metallic map can be connected to the right socket in Blender and still make the material look wrong. The surface may turn nearly black, read like plastic, become metallic everywhere, or show almost no visible change at all.
When a metallic map is not working in Blender, the map itself is only one possible cause. Metallic changes the material model, but the final appearance also depends on base color, roughness, lighting, color-space handling, and which texture channel is actually connected. Checking those parts in order is usually faster than editing the metallic texture blindly.
Start with the Principled BSDF Metallic input
For a standard metallic/roughness material, connect the metallic texture directly to the Metallic input of the Principled BSDF. Blender's current Principled BSDF documentation describes Metallic as the blend between dielectric and metallic shading. A value of 0 uses the non-metallic model, while 1 gives a fully metallic response tinted by Base Color.
A separate grayscale metallic texture is useful when one material contains both metal and non-metal regions. Worn painted steel is a common example: intact paint is non-metallic, while exposed steel is metallic. If the whole visible surface is one clean metal, a constant Metallic value of 1 can be enough.
If you are unsure what the values in the texture should represent, our metallic map black or white guide covers the underlying metalness convention in more detail.
Set the metallic texture to Non-Color
A metallic map stores material data rather than display color. In Blender, its Image Texture node should normally use Non-Color rather than sRGB.
This matters because color management changes how image values are interpreted. A grayscale texture left as ordinary color data can send different numerical values into the shader than the material author intended. The same general rule applies to roughness, normal, and height maps, while a normal base-color texture remains color data.
If several maps in the material look wrong at once, check their color-space settings before changing shader values. Our PBR texture color space guide explains which common PBR maps are color and which are data.
Make sure you connected the right texture output
A normal standalone metallic image should usually feed its Color output into Metallic. Accidentally connecting Alpha can make the entire object metallic if the image has no meaningful transparency and its alpha channel is effectively white.
Packed textures are different. If metallic is stored in one channel of an ORM, RMA, or another packed map, the combined RGB output cannot be connected directly and expected to produce the correct scalar value. Separate the channels and route the channel containing metalness to Metallic.
Blender's glTF documentation is a useful example of this distinction. In a glTF metallic-roughness texture, roughness is stored in the green channel and metallic in the blue channel. Blender recommends separating those channels before connecting them to their corresponding Principled inputs.
Our ORM texture guide covers common packed-map layouts and why the channel order matters.
If the metal looks black, check what it has to reflect
A dark metallic surface is not automatically evidence of a broken metallic map. Metals get much of their visible appearance from reflection. A scene with a dark or nearly uniform environment can therefore make a correctly configured metal look unexpectedly black or flat.
Before changing the texture, test the material in Material Preview or under an environment with visible variation. An HDRI, large area lights, bright cards, nearby geometry, or another controlled reflection source gives the surface something readable to reflect.
This is especially useful when comparing Blender with Substance Painter or another material viewer. Two applications can show the same PBR maps differently because their default environments are different.
If changing only the environment suddenly makes the metal readable, the metallic map was probably not the main problem.
Roughness can make correct metal look like plastic
Metallic and roughness control different parts of the material response. Metallic determines whether the surface follows the metallic or dielectric model. Roughness controls how broad or sharp the reflection becomes.
Blender defines Roughness from 0 for a sharp reflection to 1 for a broad, rough reflection. A metal can therefore be fully metallic and still look dull if its roughness values are high. Conversely, a non-metallic surface can be glossy when its roughness is low.
This is why increasing Metallic is not a reliable way to make a surface look shinier. If the material is already classified correctly, inspect the roughness texture and the lighting instead. Our roughness map vs gloss map guide goes deeper into that distinction.
Check whether the map should be mostly black or white
Metalness maps are often more binary than roughness maps. Exposed steel, aluminum, copper, brass, and similar bare metals are generally represented near 1. Paint, plastic, stone, wood, rust, dust, and other dielectric surface layers are generally near 0.
That means an almost-black metallic map can be completely correct for a painted metal object. The object may be made from steel underneath, but the shader describes the material visible at the surface. If only a few scratches expose the steel, only those regions need to become metallic.
Do not invert a metallic map simply because the result looks dark. Inverting the map changes which parts of the surface are treated as metal. First confirm what the black and white regions represent.
Check Base Color before blaming Metallic
Base Color participates differently once a surface becomes metallic. Blender's Principled shader uses Base Color to tint the reflection of a fully metallic surface rather than treating it like ordinary diffuse color.
This can expose problems in texture sets exported for a different PBR workflow. A diffuse texture from a specular/glossiness workflow is not necessarily interchangeable with the base-color texture expected by a metallic/roughness workflow.
If a material came from Substance Painter or another authoring tool, confirm that it was exported as a metallic/roughness set before wiring its maps into Blender's Principled metallic/roughness inputs. Our metallic roughness vs specular glossiness guide explains why simply renaming maps does not convert between the two representations.
Node Wrangler is a useful setup check
If you have a conventional set of separately named PBR textures, Blender's Node Wrangler can provide a useful reference setup. Select the Principled BSDF and use Ctrl + Shift + T to run Principled Texture Setup, then choose the material maps.
Node Wrangler uses filenames to identify common texture roles and can wire base color, roughness, metallic, and normal maps into a standard Principled graph. It is not a universal importer, but comparing its graph with a manually assembled material can quickly reveal a wrong socket or color-space setting.
Our Blender Principled Texture Setup guide covers the workflow and the cases where manual cleanup is still needed. twirl materials provide separate albedo, normal, roughness, metallic, and height maps, and twirl Connect for Blender can import completed twirl materials directly from the browser.
Metallic textures and diffuse baking are separate problems
A metallic material can look correct in the viewport and still produce a black or unexpectedly dark Diffuse bake. That does not necessarily mean the metallic map has failed.
A fully metallic surface does not have the same diffuse component as a dielectric surface. If what you need is the texture data itself, baking a data mask through an emission-style setup is different from baking the rendered diffuse contribution of a metallic shader. Keep the metallic mask, base color, and final shaded appearance conceptually separate when deciding what needs to be baked.
This distinction matters when preparing textures for another renderer or game engine. A metallic map is material data. It should remain a metallic mask in the exported texture set rather than being baked into a diffuse image as though the two represented the same property.
A reliable order for troubleshooting metallic maps in Blender
Start by disconnecting the metallic texture and testing the Principled Metallic slider at 0 and 1 under useful reflection lighting. That confirms whether the shader and environment can show a clear metallic response.
Reconnect the metallic texture to the Metallic input, set the image to Non-Color, and verify that you are using the correct output or packed channel. Then inspect the map itself to confirm that white corresponds to the regions that should expose metal. After that, check roughness and Base Color without changing the metallic map.
This order isolates one variable at a time. If the slider works but the texture does not, the problem is likely in the texture, channel, coordinates, or color-space setup. If neither the slider nor the texture produces a readable metal, lighting and roughness are better places to look.
For generated materials, the same checks apply. The twirl AI PBR material generator outputs separate albedo, normal, roughness, metallic, and height maps, so each property can be inspected independently rather than being hidden inside a renderer-specific packed texture.