October DealsAmazon USOctober deal check: compare before you payAmazon US: current deals, useful picks and tech finds.Check DealsSlow PC?RecommendedPC slow today? Run a repair scan before it gets worseResolve common Windows issues and optimize system performance.Scan NowOctober DealsAmazon USDeal season is back - check today's better picksAmazon US: current deals, useful picks and tech finds.See Picks×
Skip to content
ThatPainter
3D rendering

Mastering Ray Tracing in Blender: A Practical Cycles Step-by-Step Guide

Create convincing reflections, refractions, soft shadows, and indirect light in Blender with Cycles—and learn how to configure your GPU, reduce noise, optimize memory, and troubleshoot failed renders.

By ThatPainter Team 10 min read
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

ThatPainter is reader-supported. When you buy through links on our site, we may earn an affiliate commission. Learn More

For most Blender users, “ray tracing” means rendering with Cycles. Cycles is Blender’s physically based path tracer: it follows light through reflections, refractions, shadows, and indirect illumination to produce a convincing final image. Eevee is a separate physically based real-time renderer, not simply a faster version of Cycles.

This guide uses a controlled scene to create visible reflections, glass refraction, soft shadows, and bounced light. It also explains GPU backends, samples, denoising, light bounces, memory limits, command-line rendering, and the most common failures.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Version note: The menu paths below are checked against Blender 5.0 documentation. Labels can differ between releases, so confirm them against the Blender version installed on your computer.

Ray tracing, path tracing, Cycles, and Eevee

Ray tracing follows rays through a scene to calculate how light interacts with surfaces. In Cycles, this process is generally called path tracing: a ray can reflect, refract, scatter, or terminate at each interaction. More light interactions usually produce more realistic illumination, but they also require more computation.

Reflections and refractions are not effects that can be switched on independently of the scene. They depend on geometry, surface normals, material values, visible light sources, the world background, and the number of permitted light bounces. A glossy object in an empty, black environment may look black even when Cycles is working correctly.

Blender describes Cycles as a physically based path tracer and Eevee as a physically based real-time renderer. Their results, controls, and performance characteristics are different. See Blender’s rendering introduction for the conceptual distinction.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Choose Cycles when… Choose Eevee when…
Physically grounded light transport matters. Fast, interactive iteration matters most.
You need convincing indirect lighting, glass, volumes, or soft reflections. You are creating previews, motion graphics, or stylized work.
You can tolerate sampling and denoising time. Hardware or delivery time is limited.

Eevee is a legitimate production choice. Use it when its speed and visual control suit the project; use Cycles when path-traced light transport is central to the desired result.

Before you begin

  • Install an official stable Blender build and save the project before making major changes.
  • Know the basics of objects, transforms, materials, and camera placement.
  • A three-button mouse is helpful but not mandatory.
  • Update your graphics driver.
  • Leave enough system RAM and GPU VRAM for textures, geometry, displacement, volumes, and the final resolution.

Blender’s general requirements page lists 8 GB of RAM and 8 GB of VRAM as recommended figures, but those numbers do not guarantee that a complex Cycles scene will fit. Cycles GPU rendering has additional hardware and driver requirements; check the official requirements for your system.

Build a controlled ray-tracing test scene

A useful test scene should reveal several kinds of light transport at once. You can use the default scene as a starting point or create the following:

  1. Add a large plane as the floor.
  2. Add a beveled sphere and assign it a metallic material.
  3. Add a glass object, such as a UV sphere or a cube with real thickness.
  4. Add a colored diffuse object to provide something for reflections and bounced color.
  5. Add a large plane or curved backdrop.
  6. Add an Area Light or a large emissive plane.
  7. Place a camera so the metallic object can see the light, a dark region, the colored object, and the floor.

Why bevels improve reflections

Perfectly sharp edges often produce unhelpful highlights and can make an object look unnaturally computer-generated. A small bevel creates a surface transition that catches light, making reflections easier to read.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Why the environment matters

A reflective object reflects its surroundings. A scene containing only a gray object and a uniform world background may produce technically correct but visually empty reflections. Add contrasting cards, a backdrop, colored objects, or visible light shapes so the material has something informative to reflect.

Enable Cycles and configure your GPU

  1. Open Render Properties.
  2. Set Render Engine to Cycles.
  3. Set Device to GPU Compute.

If the labels are difficult to find, search the Properties editor for “Render Engine” and “Device.” The device selector will only be useful after a compatible backend and device have been enabled in Preferences.

Select a Cycles backend

  1. Open Edit → Preferences → System.
  2. Find Cycles Render Devices.
  3. Select the backend appropriate to your hardware.
  4. Enable the available GPU.
  5. Return to the scene and confirm Render Properties → Device → GPU Compute.

Blender 5.0 documentation lists these backend families:

Hardware Backend to test Important qualification
NVIDIA OptiX or CUDA OptiX is a natural first test on supported RTX hardware, but it is not guaranteed to be faster for every scene.
AMD HIP The Blender 5.0 manual lists RDNA1-or-newer support; hardware ray-tracing support is available on Radeon RX 6000 and newer with suitable drivers.
Intel oneAPI Support covers listed Intel Arc A-Series and B-Series hardware, not every Intel GPU.
Apple Metal Apple Silicon is supported; macOS 13 or newer is required for all listed features.

Check Blender’s current Cycles GPU documentation for the exact operating-system, architecture, and driver requirements. VRAM capacity and driver maturity matter as much as the vendor name. If GPU rendering fails, switch to CPU temporarily: it is a useful diagnostic fallback and may succeed when the scene does not fit in VRAM.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Create reflective and transmissive materials

Metal

On the beveled sphere, use a Principled BSDF and set Metallic close to 1.0. Then adjust Roughness:

  • Low roughness creates sharper reflections.
  • Higher roughness creates broad, blurred highlights.

Do not judge the metal until the object has an environment to reflect. Material settings cannot create a reflection where there is no visible scene detail.

Glass

Use a Principled BSDF with transmission enabled. Give the object realistic thickness where appropriate, check its normals, and place an object or background behind it. Refraction is much easier to see when light passes through something recognizable.

If glass looks opaque, inspect the transmission setting, object thickness, normals, transmission-bounce limit, internal geometry, and the amount of light behind the object. Many “broken glass” problems are scene-design problems rather than ray-tracing failures.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Matte surfaces

Use a diffuse or rough material for the floor and colored test object. Matte surfaces reveal soft shadows, indirect color bounce, contact with the floor, and overall exposure more clearly than a scene made entirely from reflective materials.

Light the scene so reflections are visible

Start with one large Area Light rather than many small lights. A larger light generally produces softer shadows and broad highlights; a smaller light produces harder shadows and sharper highlights. Move and resize the light while watching both the cast shadow and the reflection in the metal.

A light can illuminate a surface without appearing as a useful reflection. Reflective materials look more convincing when the light source, a bright card, or a shaped reflector is visible from the object’s point of view. Cycles’ light settings and optimizations also affect how efficiently rays reach light sources.

Tune samples and denoising

Use low samples while composing and increase them only after the scene is technically correct. A practical progression is:

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Preview: 16–64 samples.
  • Intermediate check: 128–256 samples.
  • Final: choose a value based on visible noise, materials, lighting, volumes, resolution, and denoiser behavior.

These are starting ranges, not universal answers. More samples generally reduce stochastic noise, but they will not fix incorrect lighting, missing reflections, bad normals, insufficient bounce limits, or unrealistic materials.

Enable denoising in Render Properties or add a denoise node in the compositor. Denoising can make a low-sample preview useful, but aggressive denoising may erase texture, hair, thin geometry, or small highlights. Compare the raw and denoised result before delivering the final image. Blender documents GPU acceleration for OpenImageDenoise on supported devices in its GPU rendering and performance documentation.

Control light bounces

Open Render Properties → Light Paths. Relevant limits include Total, Diffuse, Glossy, Transmission, Volume, and Transparent. These categories limit how many times different rays can interact with the scene.

  1. Begin with the default bounce settings and confirm that the scene works.
  2. Reduce Total only after confirming the image’s lighting and materials.
  3. Increase Transmission if glass becomes incorrectly dark or opaque.
  4. Increase Transparent for layered alpha or transparent surfaces.
  5. Reduce unnecessary Volume bounces when volumetric lighting is not important.

Zero bounces means direct lighting only. Lower limits can reduce render time, but they can also remove important indirect illumination, reflections, or refractions. Blender’s Light Paths documentation explains the ray categories in detail.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Handle caustics separately

Caustics are concentrated bright patterns created when light reflects or refracts. They can be beautiful, but they are often slow to converge and noisy. Do not use a caustics-heavy scene to diagnose ordinary reflections or indirect lighting.

First create a clean render without depending on caustics. Then add them as an advanced effect. If they produce instability or unacceptable noise, disable reflective or refractive caustics where the relevant controls are available. This improves render behavior at the cost of those physical light patterns. Support and performance can differ by backend; Blender’s documentation notes limitations affecting some HIP caustic features. See the guidance on reducing noise and the Cycles object settings.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Optimize render speed and memory

GPU versus CPU

GPUs can provide high throughput for parallel Cycles workloads, but their memory is often more limited than system RAM. A scene that fits in RAM may fail on a smaller GPU. Do not assume that combining CPU and GPU is faster; test CPU, GPU, and CPU-plus-GPU separately on the actual scene.

When possible, use one GPU for display and another for rendering. Textures, displacement, volumes, hair, subdivision, and large geometry are common VRAM bottlenecks.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Performance settings

In Render Properties → Performance, inspect the available controls for threads, BVH behavior, Compact BVH, Persistent Data, viewport pixel size, and the compositor or denoising device.

Persistent Data can speed repeated renders and animation frames by keeping render data in memory. Enable it when geometry is mostly unchanged and the machine has sufficient RAM and VRAM. On a memory-constrained system, it can make failures more likely. Blender documents these controls in its Cycles performance settings.

Change one variable at a time

For a noisy or slow scene, use this order:

  1. Improve light position and composition.
  2. Adjust light size.
  3. Correct exposure and material values.
  4. Enable or refine denoising.
  5. Adjust sample count.
  6. Reduce unnecessary bounce limits.

Render at 25–50% of the target resolution while testing. Doubling linear resolution creates roughly four times as many pixels, although actual render time also depends on scene complexity and settings.

Render from the command line

Background rendering is useful for repeatable stills and animations. Blender 5.0’s command-line documentation lists:

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
blender -b animation.blend -o //render_ -F PNG -x 1 -a

To render a specific frame with a Cycles device:

blender -b file.blend -f 20 -- --cycles-device OPTIX

Listed device values include CPU, CUDA, OPTIX, HIP, ONEAPI, and METAL. A GPU can be combined with the CPU using the documented form:

blender -b file.blend -f 20 -- --cycles-device OPTIX+CPU

Use render statistics when supported:

blender -b file.blend -f 20 -- --cycles-device OPTIX --cycles-print-stats

Device names must match the installed Blender build and the hardware available on that machine. See the command-line arguments documentation before automating a render pipeline.

Troubleshooting by symptom

Symptom Likely cause First fix
GPU Compute is unavailable No backend selected, unsupported hardware, driver issue, or wrong panel. Check Edit → Preferences → System → Cycles Render Devices, update the driver, restart Blender, and test CPU.
CUDA or OptiX kernel compilation fails An older Blender build or toolkit may not support a newer NVIDIA GPU. Update Blender and the driver; try the other NVIDIA backend or use CPU temporarily. Official builds normally include precompiled kernels.
Render runs out of GPU memory Textures, displacement, volumes, hair, geometry, or resolution exceed VRAM. Reduce texture and volume resolution, simplify geometry, lower subdivision, render smaller, use memory-oriented BVH options, or switch to CPU.
Reflections are black Nothing useful exists to reflect, the world is black, or normals/ray visibility are wrong. Add an environment or reflection cards; check roughness, normals, world lighting, and visibility settings.
Glass is opaque Transmission, thickness, normals, background, or bounce limits are wrong. Check geometry and transmission bounces, then add light and recognizable objects behind the glass.
Noise remains at high samples Small bright lights, volumes, caustics, dark exposure, thin geometry, or difficult glossy highlights. Improve lighting, use larger lights, enable denoising, adjust bounces, and disable unnecessary caustics before raising samples further.
Denoising removes detail Too little source data or aggressive denoising. Increase samples modestly, compare raw and denoised passes, and inspect hair, textures, fine geometry, and small highlights.

OSL warning

Open Shading Language supports custom surface, volume, and displacement shaders, but Blender 5.0 documentation states that GPU rendering for OSL is not generally supported except through the OptiX backend, with additional limitations. If your workflow depends on OSL, confirm that your preferred GPU path remains available. See Blender’s OSL documentation.

Cycles, Eevee, and paid upgrades

You do not need to buy anything to follow this tutorial: Blender and Cycles are free. Spend money only when it solves a real constraint.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • More VRAM: useful for large textures, geometry-heavy scenes, volumes, and animation.
  • Structured training: Blender Studio offers training, production assets, and open-movie production material at studio.blender.org; subscription pricing and availability should be checked at checkout.
  • Paid assets: HDRIs, material libraries, scanned textures, and models can improve the visual information available to reflections, but they do not automatically make a scene physically correct.
  • Cloud rendering: useful for deadlines or scenes that exceed local hardware, but factor in upload time, configuration, licensing, queue time, and cost. Test a representative frame first.

Final checklist

  • Cycles is selected when path-traced light transport is required.
  • The correct backend and render device are enabled.
  • Drivers and Blender are current enough for the hardware.
  • The camera sees the floor, objects, light, and environment.
  • Metal has a visible environment to reflect.
  • Glass has appropriate transmission, thickness, normals, and background detail.
  • Light size produces the intended shadows and highlights.
  • Bounce limits preserve the reflections and refractions the image needs.
  • Denoising has been checked against the raw render.
  • A low-resolution preview has been rendered before the final.
  • VRAM and system memory have been tested at the intended resolution.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

More from the Paint Desk

Recommended PC Tool
Recommended PC Tool
PC Slower Than It Used to Be?Free scan - under a minute
Crashes, No Sound, or Screen Glitches?Free driver scan

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.