Skip to content
Tutorials Center
My learning

Topics

Lesson 20 of 37 ยท Lighting and Rendering

Eevee vs Cycles: Choosing a Blender Render Engine

Compare Blender's Eevee and Cycles render engines, learn samples, denoising, light bounces and noise, and pick settings that balance quality and render time.

Blender ships with two main render engines. Eevee is a real-time engine: it draws a frame in a fraction of a second, like a game. Cycles is a path tracer: it simulates light bouncing around the scene, which is slower but physically accurate. Picking the right engine, and the right settings for it, is the difference between a render that finishes in ten seconds and one that takes ten hours.

Blender cannot run here, so this lesson describes the settings and uses small Python stand-ins to show how sampling noise and render time behave.

Choosing the engine

Open the Render Properties tab (the camera-back icon) in the Properties editor. The Render Engine drop-down lists the engines. A third one, Workbench, is the fast viewport engine used for previews and does not do realistic lighting.

Eevee Cycles
Method Rasterization with approximations Path tracing (simulates light rays)
Speed Very fast (often real-time) Slow, depends on samples
Reflections, glass, bounced light Approximated; needs setup Naturally correct
Hardware GPU CPU or GPU (CUDA, OptiX, HIP, Metal, oneAPI)
Best for Animation, previews, stylized looks, motion graphics Photorealistic stills, product shots, complex glass and indirect light

Recent Blender versions replaced the old Eevee with a redesigned engine ("Eevee Next" in 4.2) that adds real global illumination and better shadows, so the old advice that Eevee cannot do bounced light is only partly true now. Menu names and defaults change between versions, so check the manual for yours.

You can switch the engine at any time. Lights, materials made with the Principled BSDF and cameras work in both. Only a few engine-specific effects (for example Cycles-only volumetric details or Eevee-only screen-space tricks) look different.

How a path tracer works

Cycles shoots rays from the camera through every pixel. Each ray hits a surface, bounces in a random direction chosen by the material, and keeps going until it reaches a light or runs out of bounces. One ray is a very noisy guess. The pixel color is the average of many rays. Each ray is a sample.

Noise falls with the square root of the sample count: four times the samples cut the noise in half. The stand-in below simulates a pixel estimate so you can see that law.

Python Stand-in: noise versus samples

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Each time the samples grow by 4x, the noise roughly halves. Doubling render time gets you far less visible improvement than people expect.

Samples and denoising

In Cycles open Render Properties > Sampling. Two numbers matter:

  • Viewport > Max Samples (for example 64): used in Rendered viewport shading.
  • Render > Max Samples (for example 256 to 1024): used in a final render (F12).

Turn on Noise Threshold: Cycles stops sampling pixels that are already clean. Then enable Denoise (OpenImageDenoise on the CPU or NVIDIA OptiX on RTX cards). A denoiser removes remaining grain, so 128 samples with denoising often looks better than 2000 without. Too aggressive denoising smears fine texture, so compare a crop at 100 percent zoom.

In Eevee the equivalent is Render > Max Samples, used for anti-aliasing and soft shadows. 64 is the usual default.

Light paths and bounces

Render Properties > Light Paths limits how many times a ray may bounce:

  • Total: overall bounces (12 default).
  • Diffuse: bounces off rough surfaces (4).
  • Glossy: bounces off shiny surfaces (4).
  • Transmission: through glass and water (12).
  • Volume: through fog and smoke.

Fewer bounces render faster but make shadows darker (less bounced light), and glass may look black if transmission bounces run out. Clamping (Direct Light, Indirect Light) caps extremely bright samples that cause white "fireflies". A value of 10 for indirect is common.

A tiny render-time model

Render time is roughly proportional to pixels ร— samples ร— bounces-cost. The stand-in estimates how long a change will take, so you can plan an animation.

Python Stand-in: estimate animation render time

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The numbers are made up for the example. To get yours, render one test frame at low resolution, time it, and scale up.

Practical settings

  1. Model and light in Material Preview (Eevee) or Rendered view with low samples.
  2. Test render at 50 percent resolution (Output Properties > Resolution %).
  3. Enable denoising and a Noise Threshold in Cycles.
  4. Use GPU compute (Preferences > System > Cycles Render Devices) if you have a supported card.
  5. For animations, render a short still sequence first and check one hard frame.
flowchart TD
  A["Need photorealism or glass?"] -->|Yes| C["Cycles"]
  A -->|No| B["Need fast animation?"]
  B -->|Yes| E["Eevee"]
  B -->|No| C

A simple engine decision.

Common mistakes

  • Cranking samples to 4096 instead of enabling the denoiser.
  • Forgetting that the viewport and the final render have separate sample counts.
  • Rendering with the CPU when a GPU is available (or the other way round for scenes that do not fit in GPU memory).
  • Ignoring fireflies; use clamping or fix the bright source.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which statement about Cycles is true?

    Cycles is a path tracer. It can use CPU or GPU and handles glass naturally.
  2. 2. If you want half the noise, roughly how many times more samples do you need?

    Noise falls with the square root of the sample count, so 4x samples gives half the noise.
  3. 3. What is the main purpose of the denoiser?

    The denoiser cleans up noise so you can use fewer samples.
  4. 4. Which engine is usually the better choice for a fast stylized animation?

    Eevee renders frames in seconds or less, which makes long animations practical.

Summary

  • Eevee is real-time and approximate; Cycles is a slower, accurate path tracer.
  • Noise falls with the square root of samples, so use Noise Threshold and a denoiser.
  • Light-path bounce limits and clamping trade realism, speed and fireflies.
  • Measure one test frame to estimate the cost of a full animation.

Next: World Lighting and HDRI