A 30% to 60% performance drop shows up on most modern GPUs when reflections, shadows, and global illumination stack together, since the graphics card trades approximation for per-pixel light path computation. Single-player games built around atmosphere often absorb that hit, while competitive shooters usually disable RT to keep frametimes tight.
The breakdown below covers where those frames actually disappear, which features cost the most, and how to tune settings so you keep the lighting you want without dropping below a smooth frame rate.
Ray Tracing Replaces Approximation With Computation
Traditional rasterization cheats. It paints shadows with shadow maps, fakes reflections with cubemaps, and guesses where indirect light lands using baked light probes. The result is fast, but the lighting often reads as flat or inconsistent.
Ray tracing flips that model. For every pixel, the GPU shoots a ray from the camera into the scene. That ray bounces off surfaces, picks up color, gets blocked by occluders, and accumulates light energy along the way. Done correctly, reflections curve around corners, shadows soften at the edges, and indirect light spills into corners naturally. Done naïvely, it grinds the card to dust.
Why BVH Structure Matters So Much
To keep that bouncing under control, engines organize every triangle into a Bounding Volume Hierarchy, or BVH. Think of it as a Russian nesting doll of boxes that lets the GPU quickly answer “does this ray hit anything in this region?” without checking every triangle one by one. A well-built BVH is the difference between a smooth ray traced scene and a slideshow. Unreal Engine 5’s Lumen system and Microsoft DirectX Raytracing (DXR) both lean heavily on BVH efficiency, which is why a poorly optimized PC build can run far worse than the same engine on console.
This shift from approximation to calculation is why ray tracing carries a fundamentally different cost profile. Rasterization scales mostly with triangle count and resolution. Ray tracing scales with every additional bounce, every extra sample per pixel, and every complex surface the ray has to test.
The Real FPS Cost of Enabling Ray Tracing
Enabling ray tracing on most GPUs cuts frame rate somewhere between 30% and 60%, depending on which effects you turn on. A single feature like reflections might cost 15% to 25%. Stack reflections, shadows, and global illumination together and the loss frequently tops 50% on mid-range cards like the RTX 3060 or RX 6700 XT.
Per-Effect Cost Breakdown
Not every ray tracing effect hits your frame rate the same way. Here is how the three most common features typically compare when enabled individually at 1440p on a mid-range card:
| Ray Tracing Effect | Typical FPS Loss | Why It Costs So Much |
|---|---|---|
| Reflections only | 15–25% | Tests rays against geometry per pixel; scales with shiny surfaces |
| Shadows only | 20–35% | Casts additional rays from each light source through the scene |
| Global illumination only | 25–40% | Requires multiple bounces per ray to simulate indirect light |
| All three stacked | 45–60%+ | Effects compound; BVH and shaders all load simultaneously |
The 1% and 0.1% Low Problem
Average FPS tells you almost nothing about how a game actually feels. The numbers that matter are the 1% lows and 0.1% lows, which measure the worst stutters during a session. Ray tracing punishes those numbers harder than the average because BVH traversal times spike when the camera enters a new region or many rays converge on complex geometry. Cyberpunk 2077 at max settings can post a 60 FPS average yet drop into the 30s during heavy combat, even on an RTX 4070. Stutter feels worse than a lower but consistent frame rate, so an overlay like MSI Afterburner or CapFrameX should sit on screen during any tuning session.
A stable frame rate matters more than a peak one when ray tracing is on, which is why resolution choices reshape the cost so sharply.
Average FPS is the headline. 1% lows are the experience. When ray tracing is on, the gap between the two often widens by 10–20%.
Resolution Amplifies the Ray Tracing Penalty
Running games at 4K instead of 1080p can double the per-pixel work that ray-traced lighting demands. At 4K, the GPU casts four times as many rays per frame compared to 1080p, and the BVH has to be traversed for every one of them. Rasterization overhead also rises at 4K, but the curve is far less steep.
That is why a GPU might lose 30% of its frame rate at 1440p with ray tracing on yet lose 50% or more at 4K with identical settings. Cyberpunk 2077 benchmarks show the RTX 4080 falling from a comfortable 90+ FPS at 1440p RT Overdrive to roughly 45 FPS at 4K native, a gap that traditional rendering never produces.
Why Lowering Resolution Helps More Than You’d Expect
Dropping from 4K to 1440p often recovers more frames than disabling an entire ray tracing effect. That makes upscaling technologies like DLSS, FSR, and XeSS especially valuable, because they cut the internal render resolution before the ray tracing math ever runs. The end result is fewer rays per frame, lower BVH cost, and significantly higher FPS, all while the final image stays close to native.
RT Cores and Hardware Acceleration Change the Math
NVIDIA’s RTX GPUs changed the ray tracing conversation by adding dedicated RT cores that handle ray-triangle intersection and BVH traversal in hardware. Without those cores, the shader units have to do that work themselves, which is dramatically slower. A card like the GTX 1080 Ti can technically run DXR titles, but the performance collapse is severe because the silicon is doing in shaders what an RTX card offloads to fixed-function hardware.
Cards With and Without RT Hardware
| GPU Class | RT Hardware | Typical RT Cost |
|---|---|---|
| NVIDIA RTX 20-series and newer | Dedicated RT cores | 30–50% FPS loss with full RT |
| AMD RDNA 3 (RX 7000-series) | Ray accelerators per CU | 35–55% FPS loss; software support trails NVIDIA |
| Intel Arc Alchemist and Battlemage | RT units per Xe-core | 40–65% FPS loss; performance varies by title |
| Older NVIDIA GTX and AMD RX 6000 and below | None (shader fallback) | 70–80% FPS loss; often unplayable with RT on |
That last row catches most gamers off guard. When RT cores are disabled in drivers or unavailable, the same engine that runs smoothly without ray tracing can fall to single-digit FPS in heavy scenes, and Vulkan RT behaves the same way.
Upscaling, Frame Generation, and the Ray Tracing Trade-Off
Upscaling has become the default answer to ray tracing’s performance cost, and for good reason. Rendering internally at 1080p or 1440p and upscaling to 4K dramatically cuts the number of rays cast, which directly translates to higher frame rates.
DLSS, FSR, and XeSS at a Glance
DLSS uses NVIDIA’s tensor cores to upscale with neural network reconstruction, which generally produces the cleanest image but ties you to RTX hardware. FSR 2 and FSR 3 run on virtually any modern GPU, which makes them the go-to for AMD and Intel users, at the cost of slightly softer detail. XeSS uses a hybrid approach with hardware acceleration on Intel Arc and a fallback path on other cards. Each has its own image quality and latency profile, so the right choice depends on the GPU in your system.
Frame Generation: A Separate Decision
DLSS 3 and FSR 3 add frame generation, which synthesizes intermediate frames to boost perceived FPS. The technology works, but it does not actually render those frames, so it does not fix 1% lows. If the base render is stuttering, frame generation amplifies the inconsistency rather than smoothing it out. Competitive Valorant and CS2 players should leave it off because the added input latency can show up in flick shots and tracking. Single-player games like Cyberpunk 2077 or Alan Wake 2 benefit from it because the visual fluidity outweighs the latency cost.
Knowing which genre your card actually handles is one thing, but tuning those settings to keep frames stable is the harder daily problem.
Frame generation is a presentation feature, not a performance fix. Treat it as a separate setting from ray tracing and test it on its own.
Matching Ray Tracing Settings to Your Hardware and Genre
Not every game demands the same approach. A cinematic RPG treats 30 FPS as acceptable when ray tracing adds meaningful visual depth, while a competitive shooter deliberately omits RT to preserve frametime consistency. Your hardware tier matters just as much as the genre.
What Different GPU Classes Can Realistically Handle
An RTX 3060 or RX 6700 XT handles one ray tracing effect, usually reflections, at 1080p with upscaling. Adding shadows or global illumination typically drops you below 60 FPS in modern titles. An RTX 4070 runs stacked ray tracing at 1440p with DLSS Quality and holds 60+ FPS in most games, though 4K remains demanding even on an RTX 4080.
Console implementations on PS5 and Xbox Series X use dynamic resolution scaling and selective ray tracing to hit performance targets, which often produces smoother results than equivalent PC presets because the engine can drop resolution mid-frame to absorb a spike.
Practical Strategies to Keep Frame Rates Stable With Ray Tracing On
The fastest way to find the right balance is to test one setting at a time. Enable a single ray tracing effect, note the FPS delta, then decide whether the visual gain is worth the cost before adding another.
- Test effects individually: Turn on reflections alone, measure the hit, then layer shadows and global illumination one at a time.
- Use per-effect quality sliders: Most modern games expose ray count or sample settings that cut cost without removing the effect entirely.
- Pair RT with quality upscaling: DLSS Quality or FSR Quality recovers more frames than performance mode while keeping the image sharp.
- Monitor 1% and 0.1% lows: Use an overlay tool and focus on frametime consistency, not just average FPS.
- Disable RT for competitive play: Reserve it for story-driven experiences where immersion justifies the cost, and leave it off in competitive multiplayer where consistent frametime matters more than visual fidelity.
Key Takeaway
Ray tracing is one of the most expensive features a modern game can ask of a GPU, with frame rate costs ranging from 15% on a single effect to 60% or more when reflections, shadows, and global illumination stack together. The damage scales hardest with resolution and ray count, while dedicated RT cores, smart upscaling, and per-effect quality sliders are the tools that keep it playable. Match your settings to your GPU tier, monitor 1% lows rather than averages, and you can keep most of the visual payoff without surrendering a smooth frame rate.
FAQ
How much does ray tracing reduce frame rate?
Most GPUs lose between 30% and 60% of their frame rate when ray tracing reflections, shadows, and global illumination are all enabled. A single effect like reflections typically costs 15% to 25%.
Is ray tracing worth the performance hit?
For cinematic single-player games, often yes. The visual depth from realistic reflections and soft shadows justifies a 30 to 60 FPS trade. For competitive multiplayer, the frametime cost usually outweighs the visual gain.
Which GPUs handle ray tracing best?
NVIDIA RTX 40-series GPUs lead the pack because their third-generation RT cores handle light intersections faster than the competition. AMD RDNA 3 and Intel Arc GPUs support ray tracing but trail in per-ray throughput and software optimization.
Does DLSS offset ray tracing performance loss?
DLSS significantly recovers frames lost to ray tracing by reducing the internal render resolution, but it does not fix 1% lows. Frame generation in DLSS 3 boosts perceived FPS but adds latency and can mask underlying stutter.
Why does ray tracing hurt 4K performance more than 1080p?
At 4K, the GPU casts four times as many rays per frame, and the BVH must be traversed for each one. Rasterization also costs more at 4K, but ray tracing compounds the increase because every additional pixel adds full ray traversal work.
Should I disable ray tracing for competitive games?
Yes, in most cases. Consistent frametime matters more than visual fidelity in titles like Valorant, CS2, or Apex Legends, and ray tracing introduces the kind of 1% low stutter that costs rounds.
