Key takeaways
- Does ray tracing use more VRAM? Yes, usually by a noticeable margin. See where the memory goes, a worked 8GB example and a step-by-step way to check your GPU.
Yes, ray tracing normally uses more VRAM than the same scene drawn with traditional rasterization, because the GPU has to keep extra data in memory: a structure that describes the scene’s geometry, additional render targets, and noise-removal buffers. The size of the increase is game dependent, so the useful question is not “how much in general” but “does my card have enough room left once ray tracing is on”. The rest of this page shows where the memory goes and how to check your own system.
This is an editorial explainer based on published documentation, manufacturer specifications and buyer reviews. It gives mechanisms and a method, not benchmark numbers, since results vary by title and driver. Where figures appear below they are labeled assumptions for illustration.
Why ray tracing needs more memory
A rasterized frame is mostly textures, geometry and a handful of screen-sized buffers. Ray tracing keeps all of that and adds more. To work out what a ray hits, the GPU needs the scene organized so it can search it quickly. That organization is called an acceleration structure, commonly a bounding volume hierarchy, and it must live in video memory next to the geometry it describes. Complex scenes with many objects produce a bigger structure, and dynamic objects such as characters need it updated as they move.
The rays themselves also leave a noisy result, since only a few rays per pixel are practical in real time. A denoiser cleans this up using extra buffers that hold previous frames, normals, depth and motion data. Effects such as reflections, shadows, global illumination and ambient occlusion each add their own buffers. Turning on more ray traced effects stacks the cost.
Finally, ray tracing is often switched on together with higher-end presets: sharper textures, higher draw distance, more detailed shadows. The preset, not the ray tracing alone, may be what pushes memory past a card’s capacity.
Where the extra memory goes
| Component | What it stores | Scales with |
|---|---|---|
| Acceleration structure | Scene geometry organized for fast ray lookup | Scene complexity and object count |
| Ray traced effect buffers | Reflection, shadow or lighting results per pixel | Render resolution and number of effects |
| Denoiser history | Previous frames, depth and motion data | Render resolution |
| Higher-quality material data | Extra texture or shading information used by reflections | Preset and texture setting |
| Frame generation buffers (if enabled) | Extra frames and motion data | Output resolution |
The table is conceptual. Different engines organize these items differently, and the game’s own documentation or patch notes are the best source of specifics.
What resolution changes
Several of the buffers above scale with the number of pixels, so moving from 1080p to 1440p to 4K raises memory use for the ray tracing part. The acceleration structure and the textures do not scale that way, which is why the same game can behave differently at the same resolution depending on scene content. Upscaling renders internally at a lower resolution, so the pixel-scaled buffers shrink, but frame generation and output-size buffers offset some of the saving.
For a planning rule that avoids invented numbers, treat the picture like this: at lower resolutions the textures dominate the budget, at higher resolutions the render buffers and ray tracing data join them. The more of the following you turn on, the sooner the total approaches the card’s capacity: high-resolution output, max textures, several ray traced effects and frame generation.
A worked example with stated assumptions
These figures are made up to demonstrate the arithmetic and are not measurements of any game or card. Assume a graphics card with 8 GB of VRAM, of which about 0.5 GB is taken by the desktop and background apps, leaving roughly 7.5 GB for the game.
| Item (assumed) | Ray tracing off | Ray tracing on |
|---|---|---|
| Textures and geometry | 5.0 GB | 5.0 GB |
| Render buffers | 1.0 GB | 1.0 GB |
| Acceleration structure | 0 | 0.8 GB |
| Effect and denoiser buffers | 0 | 0.9 GB |
| Total | 6.0 GB | 7.7 GB |
| Headroom against 7.5 GB | 1.5 GB spare | 0.2 GB short |
With ray tracing off the game fits comfortably. With it on, the total goes over the budget by a small margin, and the engine has to push some data to system memory. Dropping the texture preset one step might free around a gigabyte in this imagined case, which brings the total back under the line. The example shows why a modest overflow causes stutter without any change to the average frame rate.
How to check whether VRAM is the limit
- Pick a repeatable spot. Choose a location in the game with heavy scenery or many characters and stand in the same place each time.
- Show a memory overlay. Use the game’s own graphics menu if it has a VRAM meter, or a monitoring overlay that shows dedicated GPU memory in use.
- Record the reading with ray tracing off. Wait thirty seconds, as some games fill memory gradually.
- Switch ray tracing on and repeat. Compare the two figures. The difference is the cost of the feature in that scene.
- Compare against the card’s capacity. Remember that “allocated” memory can exceed “needed” memory, since many engines reserve more than they use. A reading that sits near the limit with smooth frame times may be fine.
- Watch for symptoms. Stutter after several minutes of play, textures that pop in late and sudden drops in the lowest percentile frames are the signs that the card is spilling into system memory.
If the overlay shows shared or system memory climbing while dedicated memory is full, that is the spill. Since the overflow travels over the PCIe link to system RAM, faster system memory helps a little at the margin; our DDR5 versus DDR4 comparison covers that side of the question.
Settings to adjust, in order
| Step | Setting to change | Memory saved | Visual cost |
|---|---|---|---|
| 1 | Texture quality, one notch | Often large | Usually small |
| 2 | Ray tracing quality level | Moderate | Varies by effect |
| 3 | Upscaling quality mode | Small to moderate | Some softness at lower modes |
| 4 | Disable frame generation if memory is tight | Small to moderate | Lower displayed frame rate |
| 5 | Reduce output resolution | Moderate to large | Sharpness loss |
| 6 | Turn off the least noticeable ray traced effect | Moderate | Depends on the scene |
Change a single setting, test the same spot, and keep a note. The order above puts the cheapest visual trade first, but a game that shows its reflections as the main attraction may suit a different order.
Buying implications and limits
When choosing a card for ray tracing, look at capacity alongside the ray tracing hardware. A card with strong ray tracing units but limited memory can run out of room before it runs out of speed, particularly at higher resolutions. Compare the memory size, and the bus width if the listing gives it, and read buyer reports about the specific games you play. Remember that a ray tracing label does not guarantee smooth play; the entry-level cards that support the feature may run it at low frame rates.
It is also worth knowing the limits of this guide. Games differ widely, drivers change behavior over time, and a patch can alter memory use in either direction. Use the method above on your own system, and treat any single figure from a forum post as a hint to verify.
Mistakes people make
The most common mistake is reading allocated memory as required memory, then buying a bigger card for no gain. The second is blaming ray tracing alone when the texture preset was raised at the same time. The third is relying on the average frame rate, which hides the stutter caused by overflow. The fourth is ignoring background applications: browsers with hardware acceleration and capture software can hold hundreds of megabytes. The last is forgetting that settings stack, so enabling ray tracing, frame generation and the maximum texture preset together is where most cards give up.
When to stop tuning
If you must lower textures to the lowest level and cut ray tracing to a minimum just to avoid stutter, the card is the limit and the cost of more tuning is higher than the benefit. At that point, consider playing without ray tracing, lowering the resolution, or planning an upgrade. If crashes continue with drivers freshly installed and settings low, check the game’s support page and the graphics card maker’s notes before assuming a hardware fault.
Related guides
- Business Laptops With Quad Core Processors
- Retro Game Storage Cases And Displays
- Solar Chargers For Camping And Hiking
Frequently asked questions
How much extra VRAM does ray tracing need?
There is no fixed figure, because it depends on the game, the scene, the effects enabled and the resolution. Expect a noticeable increase compared with raster-only rendering, often in the range of a few hundred megabytes up to a few gigabytes. The reliable way to learn the number for your game is to compare the memory reading with ray tracing on and off in the same spot.
Will an 8GB graphics card struggle with ray tracing?
It can in newer games at higher texture settings, because the ray tracing data and the textures compete for the same memory. At 1080p with moderate textures, many titles remain playable. If you see stutters, lower texture quality first, then reduce the ray tracing effect level. Raising the resolution or enabling frame generation tends to push the total up, so keep an eye on the overlay.
Does DLSS or FSR reduce ray tracing VRAM use?
Upscaling lowers the internal render resolution, which shrinks the buffers that scale with pixel count, so it often trims memory use a little. It does not shrink textures or the ray tracing acceleration structure, so the saving is limited. Frame generation adds its own buffers, which can cancel part of the gain. Treat upscaling as a helper for frame rate first and memory second.
What happens when ray tracing runs out of VRAM?
The game starts moving data into system memory over the PCIe link, which is much slower than the card’s own memory. You see stutter, sudden frame time spikes, textures that load late or look blurry, and sometimes a crash. Average frame rate can look acceptable while the worst frames feel bad, so judge by smoothness and the lowest percentile frames, not the average alone.
Is it better to turn ray tracing off or lower the texture quality?
Lowering texture quality one notch is usually the cheapest way to recover memory with little visible loss, so try that first. If the effect you care about is ray traced reflections or global illumination, keep it and reduce textures instead. If the game still stutters, drop the ray tracing quality level before turning it off completely. The best order depends on the game, so change one setting at a time.
