A Cinema 4D PBR workflow depends on which renderer the scene actually uses. Redshift (bundled with many Maxon subscriptions) is a metalness-roughness GPU engine. Physical and older Standard materials still appear in legacy files. This article focuses on a Redshift-first setup that also keeps maps reusable in Blender or Unreal, using Locker3d as the CC0 texture source.
Redshift Standard Material slots
Create a Redshift Standard Material. Set the BRDF to GGX. Connect a Texture node for albedo into Base Color; leave that texture in sRGB. Connect roughness to Roughness with the texture in Raw / gamma 1.0. Connect metalness to Metalness the same way. For normals, add a Bump Map node, set Input to Tangent-Space Normal, and choose the correct green channel (OpenGL vs DirectX). Displacement is a separate port and needs tessellation or a displaced mesh. Start with a Locker3d set from the catalog—wood for dielectrics, metal for the metallic path.
Color management in C4D
Turn on OCIO / ACES if your studio uses it, but do not double-apply sRGB on albedo. Data maps must not go through the sRGB curve. In the Redshift Texture node, Color Space is the control that matches Blender’s Non-Color. If a concrete floor looks like wet clay, roughness is probably still sRGB. If chrome looks like gray plastic, metalness is not reaching 1 or the albedo is too bright. You can verify the same files in Blender with the Blender PBR steps before you blame Redshift.
Physical, Standard, and when to convert
Physical Material in C4D can take roughness and reflectance layers; it is usable for CPU Physical renders. Legacy Standard with a texture in Specular Color is the old path—avoid it for new PBR libraries. If a client file is Standard-only, convert to Redshift Standard and reconnect maps rather than eyeballing specular. Node materials (newer C4D) make this closer to Blender’s graph: one Mapping-style transform driving every texture. Keep UV scale in real-world centimeters so a 20 cm tile is not a 2 meter slab.
- Albedo → Base Color (sRGB)
- Roughness → Roughness (raw)
- Metalness → Metalness (raw)
- Normal → Bump Map, tangent normal (raw)
- AO → multiply on albedo or a dedicated AO slot if present
Motion, stills, and resolution
Cinema 4D is often used for product orbits and archviz fly-throughs. Motion hides some texture error; stills do not. Use 1K on background boxes. Use 2K on the product body. Use 4K when the camera dollies into a logo or stone edge. Redshift caches textures on the GPU: ten unused 4K materials in the content browser still hurt if they are in the scene. Convert PSD to PNG/TIFF. Locker3d is a free CC0 PBR library, so commercial motion work is allowed; read CC0 details.
Common C4D PBR mistakes
Leaving Texture Preview Size tiny so you “think” 4K is loaded, mixing Reflection and Metalness layers that both add spec, forgetting to enable Redshift on the object tag, and using a bump map plus a strong normal until the surface crawls. Another classic: exporting from Substance or Photoshop with the wrong normal orientation, then “fixing” it by flattening roughness. Check a gray sphere under the same HDRI. Map theory is in the complete PBR guide; start simpler with PBR textures for beginners. More C4D and material posts sit on the blog.
Frequently asked questions
How do I apply PBR textures in Cinema 4D?
For Redshift, use a Standard Material in metalness-roughness mode. Connect albedo to Base Color, roughness to Roughness, metalness to Metalness, and a normal through a Bump Map set to Tangent-Space Normal. Color maps use sRGB; data maps use raw/linear.
Should I use Cinema 4D’s old Standard material for PBR?
Prefer Redshift Standard or the Physical/Standard Surface workflow your version documents. Legacy Standard with a specular color is harder to keep energy-conserving across lights.
What texture size should I use in Cinema 4D?
Use 2K for most motion and stills, 4K for hero products, and 1K for background set dressing. GPU renderers like Redshift pay VRAM for every 4K you forget to downsize.