Ray tracing destroys your frame rate because it forces your GPU to calculate the physical path of millions of light rays bouncing through a scene in real time, a workload that traditional rendering never had to handle. Enabling ray tracing typically cuts FPS by 30 to 60 percent depending on the game, the settings, and the resolution you play at. On mid-range cards the hit can be even worse, sometimes dropping frame rates below playable thresholds without help from upscaling.
I have spent the last several years benchmarking ray tracing across RTX 20-series cards all the way up to current-gen flagships, and the story has not changed much. Hardware gets faster, but games keep demanding more. In 2026, the question is not whether ray tracing looks good, it clearly does. The real question is whether the visual upgrade justifies the performance penalty for your specific setup and the games you actually play.
This guide breaks down exactly why ray tracing is so expensive computationally, how much FPS you can expect to lose across different GPU tiers, which games are genuinely worth the sacrifice, and when you should just leave the setting off. By the end you will have a clear framework for deciding whether ray tracing deserves a spot in your graphics menu.
Table of Contents
What Is Ray Tracing? (And Why It’s Different From Rasterization)
Ray tracing is a rendering technique that simulates how light behaves in the real world by tracing the path of individual light rays as they travel from a source, bounce off surfaces, and reach the virtual camera. Instead of faking reflections and shadows with pre-baked tricks, the GPU calculates physics-based lighting in real time.
Traditional rendering, called rasterization, takes a shortcut. It draws each triangle of a 3D model onto your screen and then paints on lighting effects using approximations like screen-space reflections and cube maps. These techniques are fast because they cheat, only showing reflections for objects already visible on screen and reusing pre-calculated shadow maps.
Ray tracing throws those shortcuts out the window. When you look at a puddle in Cyberpunk ukowith RT reflections enabled, the GPU traces actual light rays from your camera, off the water surface, and to every object reflected in it. Those reflected objects might be behind you, above you, or around a corner. The result is reflections, shadows, and global illumination that behave exactly like real light, but the computational cost is enormous.
This fundamental difference is the entire reason ray tracing destroys your frame rate. Rasterization has had over two decades of optimization. Ray tracing in real-time games is still relatively new, and even with dedicated hardware, it asks the GPU to do far more work every single frame.
Why Ray Tracing Destroys Your Frame Rate?
Ray tracing tanks FPS because it adds a massive layer of calculations on top of everything your GPU was already doing. Every frame, the GPU must build and search through a Bounding Volume Hierarchy (BVH), a spatial data structure that helps rays find objects efficiently. Then it traces thousands to millions of rays through that structure, testing each ray against geometry to compute reflections, shadows, and lighting.
Modern RTX and RX cards include dedicated hardware called RT cores (NVIDIA) or Ray Accelerators (AMD) specifically designed to handle these ray-triangle intersections. But even with that silicon, the sheer number of operations is staggering. A single reflective surface in a complex scene can generate hundreds of secondary rays, each requiring its own intersection test.
Here is what the performance hit looks like in practice based on benchmark data I have tracked across multiple titles:
- Cyberpunk 2077 with ray tracing on (reflections, shadows, lighting): roughly 45 to 55 percent FPS drop at 1440p native.
- Control with full ray tracing: 40 to 50 percent FPS reduction on most cards.
- Alan Wake 2 with path tracing enabled: 55 to 70 percent FPS hit without upscaling, often dropping below 30 FPS even on high-end cards.
- Hogwarts Legacy with RT reflections and shadows: 25 to 35 percent FPS drop, one of the more modest penalties.
VRAM is the second victim. Ray tracing requires the GPU to store BVH data structures and additional render targets, often consuming 1.5 to 3 GB of extra VRAM depending on the scene complexity. On a card with 8 GB of VRAM playing at 1440p, that extra allocation can push you past your memory limit, causing stuttering and texture streaming issues that further erode the experience.
Path tracing, the most demanding form of ray tracing popularized by games like Cyberpunk 2077’s Overdrive mode and Alan Wake 2, essentially traces rays for nearly every lighting calculation. It looks stunning but can cut frame rates in half compared to even standard ray tracing. This is why path-traced modes are effectively unplayable without DLSS or frame generation on anything below an RTX 4070 Ti class card.
The FPS cost also scales with resolution. At 4K, ray tracing overhead compounds with the already massive pixel workload. At 1080p, the relative hit is often smaller because the GPU has more headroom, but you are also giving up the visual fidelity that makes ray tracing worthwhile in the first place.
Ray Tracing Performance Impact by GPU Tier
How much ray tracing hurts your FPS depends almost entirely on what card you are running. I have grouped the current landscape into tiers based on real-world performance data from 2026 benchmarks.
Entry-Level RT Cards (RTX 3060, RX 7600, ARC A750)
At this tier, ray tracing is generally not worth enabling for most games. These cards have enough RT hardware to run the calculations, but not enough to maintain playable frame rates once the workload lands. Expect 30 to 50 percent FPS drops, and in heavier titles like Cyberpunk or Alan Wake 2, you will often fall below 30 FPS even at 1080p with aggressive DLSS or FSR upscaling. Ray tracing here is a tech demo, not a practical feature.
Mid-Range Cards (RTX 4060 Ti, RTX 4070, RX 7800 XT)
This is where ray tracing becomes viable but conditional. On an RTX 4070, you can run medium RT settings at 1440p with DLSS Quality and hold 45 to 60 FPS in most titles. Path tracing is still off the table without frame generation. AMD’s RX 7800 XT offers stronger rasterization performance than the 4070 but weaker ray tracing, so expect larger FPS drops when RT is enabled. NVIDIA’s DLSS advantage is most felt at this tier.
High-End Cards (RTX 4070 Ti Super, RTX 4080 Super, RX 7900 XTX)
This is the sweet spot for ray tracing. Cards in this range can handle standard ray tracing at 1440p and 4K with DLSS or FSR and maintain 60-plus FPS in most games. Path tracing becomes playable at 1440p with DLSS Balanced and frame generation, though 4K path tracing may still dip into the 40s. Forum data consistently shows that RTX 4070 Ti Super owners are the most satisfied with their ray tracing experience relative to the price they paid.
Enthusiast Cards (RTX 4090, RTX 5090)
At the top end, ray tracing is essentially free in most titles. An RTX 4090 can run Cyberpunk 2077 with path tracing at 4K with DLSS Performance and frame generation and hold 80 to 100 FPS. Standard ray tracing barely registers as a performance hit at 1440p. This is the only tier where you can realistically max out every RT setting without thinking about it, but it requires a massive financial investment.
Consoles (PS5, Xbox Series X)
Console ray tracing is real but limited by hardware that sits roughly between entry-level and mid-range PC GPUs in RT performance. Most console games offer a Quality mode with RT at 30 FPS or a Performance mode at 60 FPS without RT. Mark Cerny’s data showed that roughly 75 percent of PS5 Pro users prefer Performance mode over Quality mode with ray tracing, which tells you how most players actually value the tradeoff.
Why DLSS, FSR, and Frame Generation Are Now Mandatory
The dirty secret of modern ray tracing is that it was never designed to run at native resolution on current hardware. DLSS, FSR, and XeSS exist specifically to offset the ray tracing tax by rendering the scene at a lower internal resolution and then upscaling it with AI or algorithmic reconstruction.
Without upscaling, ray tracing is unplayable on anything below an RTX 4080 or RX 7900 XTX in demanding titles. With DLSS Quality mode (which renders at roughly 62 percent resolution before upscaling), an RTX 4070 can go from an unplayable 28 FPS to a smooth 52 FPS in Cyberpunk 2077 with RT on. The upscaler effectively pays for the ray tracing overhead.
DLSS remains the best upscaler in 2026, particularly with Ray Reconstruction enabled, which replaces older denoiser passes with an AI-trained model that produces cleaner lighting and fewer artifacts. FSR 3.1 has closed much of the gap and works on all GPU brands, but still trails DLSS in motion stability and fine detail. Intel’s XeSS sits between the two, with excellent image quality on Arc hardware but softer results on other cards.
Frame generation is the second tool, and it is more controversial. By interpolating between rendered frames, frame generation can double your displayed FPS without doubling the actual rendering workload. In a game running at 45 FPS with RT on, DLSS 3 frame generation can push the displayed rate to 85-plus FPS. The tradeoff is latency, since the generated frames are predictions rather than real renders. In single-player games this is usually fine. In competitive shooters, the added input lag can be the difference between hitting and missing a shot.
The catch with all of this is that you are now stacking techniques. Ray tracing lowers FPS, DLSS trades resolution to recover it, and frame generation adds latency to smooth the result. Whether that chain of compromises produces a better experience than simply turning RT off and running at native resolution with high FPS is a judgment call every player has to make for themselves.
When Ray Tracing Is Actually Worth It?
Ray tracing is worth it in a specific subset of games where the lighting and reflections are central to the visual experience and where your hardware can maintain at least 40 to 60 FPS with RT enabled. In every other scenario, the performance cost outweighs the visual benefit.
The games where ray tracing genuinely transforms the visuals fall into a short list:
- Cyberpunk 2077 with RT reflections and global illumination, or path tracing on Overdrive mode. The neon-soaked streets and reflective surfaces make RT the clear star.
- Alan Wake 2 with path tracing. This is arguably the best-looking ray-traced game available, with lighting that fundamentally changes the atmosphere.
- Control. One of the earliest great RT showcases, with stunning reflections on every surface and accurate volumetric lighting.
- Metro Exodus Enhanced Edition. The RT global illumination here replaces baked lighting entirely, and the difference is immediately obvious.
- Minecraft RTX. The blocky art style becomes genuinely beautiful with realistic light bouncing through every scene.
- Black Myth Wukong. One of the newer path-traced titles, with reflections and shadows that dramatically enhance the environment.
Then there is a larger category of games where ray tracing exists but is hard to notice or actively underwhelming. Hogwarts Legacy RT shadows and reflections are subtle enough that many players cannot tell the difference in side-by-side comparisons. Indiana Jones offers RT global illumination that looks good but comes with a stiff FPS penalty. Many sports titles and strategy games have RT modes that barely change the visuals.
The most visible ray tracing effects, ranked by how much they actually change what you see on screen:
- RT Reflections are the most obvious improvement, especially on wet surfaces, glass, and water.
- RT Global Illumination transforms how light fills a space and is often the feature that makes a game look next-generation.
- RT Shadows add softer, more realistic shadow falloff but are easy to miss in fast gameplay.
- RT Ambient Occlusion is the least noticeable setting and usually the first one I disable to recover FPS.
For single-player, visually-driven games, the tradeoff is often worth it. For competitive multiplayer where reaction time matters, ray tracing is almost never worth the FPS cost, regardless of how powerful your card is.
When You Should Disable Ray Tracing
Disable ray tracing in any situation where frame rate directly impacts your gameplay experience or your hardware cannot sustain a playable rate. The visual upgrade is real, but it is never worth an unplayable or stuttering experience.
Competitive games like Counter-Strike 2, Valorant, Apex Legends, and Call of Duty should never have ray tracing enabled. The added latency from frame generation and the reduced frame rate from RT calculations will put you at a measurable disadvantage. In these games, every millisecond of input lag and every extra frame of visibility matters more than any lighting effect.
If you are running a card with 8 GB of VRAM or less, ray tracing at 1440p or 4K is likely to cause stuttering from VRAM exhaustion even if your raw FPS numbers look acceptable. The BVH data and additional render targets push memory usage past what budget cards can handle. In this case, either drop to 1080p or disable RT entirely.
On entry-level RT cards like the RTX 3060 or RX 7600, the performance hit is so severe in most modern titles that ray tracing simply is not practical. You will spend more time fighting settings menus than enjoying the game.
When you want to keep some RT but recover FPS, disable settings in this order: ambient occlusion first, then shadows, then global illumination, and keep reflections as long as possible since they are the most visually impactful. If you are still below your target frame rate after trimming those, disable ray tracing entirely and rely on rasterized alternatives.
Games that implement ray tracing poorly are another reason to turn it off. Some titles slap an RT badge on settings that barely alter the visuals but still carry the full performance cost. If you cannot tell the difference between RT on and off in a screenshot, leave it off and enjoy your extra frames.
Your Ray Tracing Decision Framework
Use this framework to decide whether ray tracing belongs in your next gaming session. It is built around the GPU tier, the game type, and the frame rate you need.
Step 1: Identify your GPU tier. If you are on an entry-level RT card, skip ray tracing except in older or well-optimized titles. If you are mid-range, enable RT only in visually-focused single-player games with DLSS or FSR on. If you are high-end or enthusiast, enable RT freely in single-player titles.
Step 2: Check your VRAM headroom. At 1440p you want at least 12 GB of VRAM for ray tracing. At 4K you want 16 GB or more. If you are below those numbers, either lower your resolution or keep RT off.
Step 3: Identify the game type. Competitive multiplayer means RT off, no exceptions. Single-player narrative or exploration games are the prime candidates for RT. Strategy and simulation games rarely benefit.
Step 4: Check the specific implementation. Look up whether the game is known for good ray tracing. Cyberpunk 2077, Alan Wake 2, Control, and Minecraft RTX are worth it. If reviews say the RT is subtle or unnoticeable, save your frames.
Step 5: Enable an upscaler. DLSS Quality at 1440p or DLSS Balanced at 4K recovers most of the FPS you lose to RT. Without an upscaler, only enthusiast cards should run RT in modern AAA titles.
Quick reference by card and use case:
- RTX 4090 / RTX 5090: Enable everything, including path tracing, at 4K.
- RTX 4080 Super / RX 7900 XTX: Full RT at 1440p, selective RT at 4K.
- RTX 4070 Ti Super: Full RT at 1440p with DLSS, path tracing with frame generation.
- RTX 4070: Selective RT at 1440p with DLSS Quality.
- RTX 4060 Ti / RTX 3060: RT only at 1080p with DLSS, and only in well-optimized games.
- Competitive gaming (any card): RT off.
FAQs
Does ray tracing make FPS worse?
Yes. Ray tracing almost always reduces FPS because the GPU must calculate light bounces, reflections, and shadows in real time on top of its normal rendering workload. The drop typically ranges from 30 to 60 percent depending on the game, settings, and resolution, with heavier implementations like path tracing in Cyberpunk 2077 or Alan Wake 2 cutting FPS by more than half without upscaling.
Is it better to have ray tracing or high frame rate?
For competitive multiplayer games, high frame rate is always better because input latency and responsiveness directly affect performance. For single-player, visually-focused games like Cyberpunk 2077, Alan Wake 2, or Control, ray tracing is often worth the FPS tradeoff as long as you can maintain at least 40 to 60 FPS with DLSS or FSR enabled. The right choice depends on the game and your hardware tier.
Is 200 FPS overkill?
For most gamers and most games, yes. Beyond roughly 144 FPS, the visual benefit diminishes for the average player, though competitive shooters can still benefit from 240 Hz or higher refresh rates. The real value of 200-plus FPS is the reduced input latency it provides in fast-paced competitive play. For single-player narrative games, 60 to 120 FPS is more than enough.
Is 40 FPS choppy?
40 FPS can feel choppy compared to 60 FPS, but it is playable for many single-player games, especially with frame generation smoothing out the presentation. Console Quality modes often target 30 to 40 FPS, and many players find 40 FPS acceptable on a VRR display. For competitive or fast-paced games, 40 FPS is too low and you should disable ray tracing to reach 60 or higher.
What GPU do I need for ray tracing at 1440p?
For solid ray tracing performance at 1440p, you want at minimum an RTX 4070 with DLSS Quality enabled, though the RTX 4070 Ti Super is the real sweet spot where RT becomes comfortable rather than a compromise. For path tracing specifically, you need an RTX 4070 Ti Super or higher with DLSS and frame generation to stay above 40 FPS. AMD alternatives like the RX 7800 XT work but deliver weaker RT performance than equivalent NVIDIA cards.
Does ray tracing work on AMD graphics cards?
Yes. AMD Radeon RX 6000 and RX 7000 series cards support hardware ray tracing through their Ray Accelerators. However, AMD cards generally deliver lower ray tracing performance than equivalently-priced NVIDIA RTX cards, and AMD lacks a direct equivalent to DLSS and Ray Reconstruction. FSR 3.1 helps close the gap, but NVIDIA remains the stronger choice if ray tracing is a priority for you.
Conclusion: Should You Enable Ray Tracing?
Why ray tracing destroys your frame rate comes down to one simple fact: simulating real light requires dramatically more computation than faking it. The performance cost is real and unavoidable on current hardware, and it will remain significant even as GPUs get faster because games keep pushing RT features further. Path tracing, ray reconstruction, and more complex scenes ensure the workload scales upward alongside the silicon.
The decision is straightforward once you know your constraints. If you have a high-end card and play visually-driven single-player games, ray tracing is worth the hit in the right titles. If you play competitively, have a budget GPU, or are VRAM-limited, leave it off. Upscaling and frame generation have made ray tracing far more accessible than it was three years ago, but they are workarounds, not cures. The technology will eventually become cheap enough to run everywhere, but in 2026, it remains a premium feature that demands a deliberate choice every time you load a new game.