R3f Materials

enzed/r3f-skills/skills/r3f-materials

by enzed4a11805f0973No license128 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 5 weeks ago

Choose and configure React Three Fiber surface materials, PBR, transparency, and transmission. Use for mesh appearance and material cost; use shader guidance for custom GLSL or TSL code.

Instructions onlySoftware Development
AI-generated overview

Guides choosing and configuring React Three Fiber surface materials, PBR, transparency, and transmission.

What it does
This skill provides guidance for selecting and configuring React Three Fiber surface materials, covering material choice, PBR settings, color space handling, transparency, and transmission. It includes a comparison table of material types, example code for environment lighting, and rules for material lifetime, sharing, and updates. It also lists verification steps and reference sources for Three.js and Drei materials.
When to use it
Use it when working on mesh appearance or material cost in a React Three Fiber scene. It is intended for decisions about PBR surfaces, transparency, glass, and material lifecycle. It is not for custom GLSL or TSL shader code, which the document directs elsewhere.
Requirements
No scripts are included; it is instructions only. It assumes a React Three Fiber project with Three.js and Drei, and references WebGL and WebGPU contexts.

React Three Fiber materials

Inspect the installed renderer, Three.js, Fiber, and Drei versions first. Examples use Fiber 9 / React 19 with WebGL. Do not assume Drei shader-based materials work unchanged with WebGPU.

Choose the least complex material that fits

NeedStarting pointConstraint
Unlit artwork or UI surfacemeshBasicMaterialStill participates in output color/tone-mapping policy
Ordinary PBR surfacemeshStandardMaterialMetals especially need an environment or suitable lights
Clearcoat, transmission, sheenmeshPhysicalMaterialEnable only needed features; more shader work
Stylized lightingmeshToonMaterialNeeds lights; gradient maps need appropriate filtering
Normal debuggingmeshNormalMaterialUseful for geometry/normal inspection
Custom shadingShaderMaterial or node materialMatch WebGL/GLSL versus WebGPU/TSL

PBR surface with environment lighting

Mount below Canvas. This small procedural environment avoids a remote preset dependency.

tsx
import { Environment, Lightformer } from '@react-three/drei'
export default function Example() {  return (    <>      <Environment resolution={64} frames={1}>        <Lightformer position={[0, 3, 2]} scale={[5, 5, 1]} intensity={3} />      </Environment>      <mesh>        <sphereGeometry args={[1, 32, 24]} />        <meshStandardMaterial color="goldenrod" metalness={1} roughness={0.3} />      </mesh>    </>  )}

PBR and color decisions

  • Use metalness near 0 for dielectrics and near 1 for bare metals; intermediate values usually describe mixtures or texture filtering. Roughness controls microsurface response, not opacity.
  • Color/albedo and emissive textures use sRGB; roughness, metalness, normal, AO, and masks use NoColorSpace. Preserve correctly loaded glTF texture metadata.
  • Maps multiply scalar settings: a metalness map with metalness={0} has no effect; an emissive map needs a nonblack emissive color.
  • A normal map alters shading; a displacement map alters vertices and needs enough geometry subdivisions. Normal maps do not alter the silhouette.
  • An emissive surface does not illuminate nearby geometry or automatically produce a halo. Add appropriate lighting and a bloom pipeline when those effects are required.
  • PBR appearance changed across recent Three.js releases. Validate with controlled lighting/exposure; do not blindly compensate for an upgrade with extra lights or color conversion.

Transparency and glass

  • opacity < 1 needs transparent for ordinary alpha blending. For cutout foliage or decals, consider alphaTest to avoid sorting artifacts; choose soft transparency only when required.
  • depthWrite={false} can help some transparent layers but is not a universal fix. Test overlap order, backfaces, and intersection with opaque objects.
  • Use physical transmission for glass, generally with opacity 1 and a meaningful thickness/IOR. Transmission is not equivalent to ordinary transparency.
  • Drei MeshTransmissionMaterial and MeshReflectorMaterial add scene renders. Start with low resolution/samples, and measure before enabling backside passes or one independent buffer per object.
  • A shared transmission sampler is cheaper in some scenes but cannot reproduce all visibility between transparent/transmissive objects. Read the helper's documentation before choosing it.
  • Do not enable DoubleSide everywhere: it changes rendering cost and may hide incorrect winding or normals.

Lifetime and updates

  • Share materials when objects should share appearance. Clone before changing one instance's color, maps, or uniforms; a cached glTF material may be used elsewhere.
  • R3F owns declarative material children. Externally allocated/shared materials need explicit lifecycle ownership. Disposing a material does not dispose its textures.
  • Animate ordinary material properties through typed refs. Value changes such as roughness or color do not require needsUpdate; shader feature changes such as adding/removing a map can require recompilation.
  • Material arrays require matching geometry groups. An array alone does not assign arbitrary materials to faces.

Verify

Render under the intended lighting and output pipeline, then test transparent overlaps, shadows, and repeated mount/unmount. Compare GPU cost before adding transmission or reflection passes.

Sources

Source and attribution

Source:enzed/r3f-skillsinskills/r3f-materialsat commit4a11805

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal