Photorealistic rendering in Blender: light, materials, camera and Cycles settings
Short answer
Photorealistic rendering in Blender comes down to five things: the Cycles engine, believable lighting (an HDRI and lights at real-world size), imperfect PBR materials, bevelled edges, and a camera set up like a real one (focal length, height, depth of field). The AgX view transform, the default since Blender 4.0, and the exposure finish the job.
A render that looks "3D" is spotted in a second, even when you cannot say why. Photorealism comes from an accumulation of details the eye expects from a photo, and almost never from one magic setting. This guide goes through them in the order they matter, from lighting to output settings.
1. Render with Cycles
Cycles is Blender's path tracing engine: it calculates the path of light, with its bounces, reflections and soft shadows. It is the basis of a photorealistic render. EEVEE is much faster and improves with every release, but it approximates part of these effects. Turn on the graphics card in the preferences and set Device to GPU Compute; the guide on OptiX vs CUDA explains how to choose the backend.
2. Light the scene as in real life
- An HDRI for the environment: a high dynamic range panoramic image lights the scene with the light of a real place and gives natural reflections. The guide to HDRI in Blender covers the setup.
- Lights at the right size: a small source gives sharp shadows, a large source soft ones. A window is better reproduced with an Area light the size of the window than with a point light.
- Indirect lighting: light bouncing off the walls brightens the areas in shadow. This is what the light bounces control (Light Paths, Max Bounces); the manual says Total should be at its maximum for the best quality.
- A single lighting logic: a sun, a sky and a few consistent lamps work better than ten sources placed to fill in every corner.
3. PBR materials, with imperfections
PBR describes a surface by its colour, how metallic it is and its roughness; in Blender, that is the job of the Principled BSDF. Realism then comes from imperfections: no real surface has perfectly uniform roughness. A slight variation in roughness, fingerprints on a glass, dust in the crevices with ambient occlusion do more for realism than an 8K texture. Free 3D textures under a CC0 licence (guide in French) give you a good base.
4. Bevel the edges
In real life, no edge is perfectly sharp: even a new piece of furniture has a slight rounding that catches the light. A perfect right-angled edge makes a model look artificial at once. The Bevel modifier, with a small width and two or three segments, is enough in most cases.
5. A camera set up like a real one
- Focal length: 35 to 50 mm for a natural point of view, longer for a portrait or a product. Very short focal lengths distort the image and give the 3D away.
- Height: at eye level for a room, and a level camera so that verticals stay straight in architecture, with the lens shift (Shift) to frame the shot.
- Depth of field: a slight background blur on a product or a detail recalls a real lens. The depth of field entry explains the setting.
The guide to the Blender camera (in French) goes through each of these settings.
6. The render settings that matter
| Setting | Where | Why |
|---|---|---|
| Noise Threshold and Max Samples | Render Properties, Sampling | Cycles stops when the image is clean enough |
| Denoise | Render Properties, Sampling | Removes the remaining noise (OpenImageDenoise or OptiX) |
| Max Bounces | Render Properties, Light Paths | More bounces, more indirect lighting |
| Clamping | Render Properties, Light Paths | Fewer isolated white dots, at the cost of some accuracy |
| View Transform AgX and Exposure | Render Properties, Color Management | Colours hold up better in overexposed areas |
Clamping reduces noise by limiting the intensity of very bright samples; set too low, it kills reflections and caustics. Caustics themselves can be turned off to save time if the scene does not need them.
7. The mistakes that give the 3D away
- A perfectly clean, uniform floor, without any variation.
- Floating objects: without contact shadows, nothing looks like it is resting on anything.
- Wrong scale: a three-metre door or a giant mug gets noticed, even when people cannot say why. Work in real-world units.
- Pure black or pure white materials, which reality almost never produces.
- A scene that is too empty: reality is cluttered, and a believable interior has objects, cables and books.
The cost of realism
Every step towards realism makes the render heavier: more bounces, more samples, more geometry. On a still image, this stays reasonable. On an animation, you have to multiply by the number of frames: the render time calculator gives the order of magnitude, and the guide to rendering faster in Cycles shows where to save time without losing quality.
Frequently asked questions
Which engine should you use for photorealistic rendering in Blender?
Cycles. It is Blender's path tracing engine: it follows light bounce after bounce, which gives the soft shadows, reflections and indirect lighting of a photo. EEVEE is faster but takes shortcuts with light, and suits stylised renders or previews better.
Why does my Blender render look "3D"?
Most often: perfectly sharp edges, materials that are too clean and uniform, flat lighting or no indirect light, and a camera placed at a height or focal length no photographer would choose. Bevelling the edges, varying the roughness and lighting with an HDRI fix most of it.
How many samples for a realistic render?
There is no universal number: it depends on the scene and on denoising. The simplest approach is to set a Noise Threshold and a maximum number of samples, then turn on denoising; Cycles stops as soon as the image is clean enough.
AgX or Filmic?
Since Blender 4.0, AgX has replaced Filmic as the default view transform for new files. According to the release notes, it handles colours better in overexposed areas, and very bright colours shift towards white, as they do with a real camera. For a realistic render, keep AgX and adjust the exposure instead.
Rendering the animation on TURNA
When a scene is already well optimised and the frame count is what takes the time, the remaining lever is rendering several frames at once. TURNA does this for Blender: an add-on (Blender 4.0 to 5.2, Cycles and Eevee) sends the scene in one click, and the frames are split across 1, 2, 4 or 8 GPUs in parallel, RTX 5090 first and RTX 4090 when none is free. The add-on shows the estimated cost before anything starts. Prices start at €2.90 per hour, billed on the time actually used, with a 30-second minimum, and new accounts get €25 of free credit. A single still image is still rendered by one machine, so the gain is on animations. Tiers and worked examples are on the Blender render farm page.
Realism costs render time: light bounces, samples, resolution. For an animation, TURNA splits the frames of a Blender scene across 1 to 8 GPU machines in parallel, in Cycles and EEVEE alike, billed on the time actually used, with a 30-second minimum.
