Best RTX 5070 Ti Settings for 1440p and 4K: Driver, DLSS, VRR and Frame-Time Budgets

Published October 27, 2026 · Independent guide by RTX 50 Series

Set up the platform before the game

Most tuning failures start before a game launches. A short checklist removes the commonest problems.

Windows and display settings

Open Windows display settings and confirm that the monitor runs at its native resolution and highest refresh rate. A surprising number of systems default to 60 Hz after a driver install. If you use HDR, calibrate it with Microsoft's HDR Calibration app, and leave HDR off for competitive play if it adds latency on your display. The guide to running a 4K display at its native resolution and maximum refresh rate shows the steps.

Game Mode and background load

Keep Windows Game Mode on, and close recording or overlay tools you do not use. Each overlay adds a small cost and can interfere with frame pacing.

Hardware-accelerated GPU scheduling

This Windows setting changes how the GPU schedules work. It helps frame generation in some configurations and causes issues in others, so test it with your games, then keep the state that gives the smoother frame-time graph.

Driver and NVIDIA App

Install a current driver, either Game Ready or Studio, and use the NVIDIA App for per-game settings. Leave global settings at defaults except for a preferred power mode, and avoid forcing driver-level anti-aliasing, which conflicts with DLSS. The article on a sensible NVIDIA Control Panel profile explains which global options are worth touching.

Resizable BAR and BIOS

Enable Resizable BAR and Above 4G Decoding in the BIOS if your platform supports them, as the guide to PCIe 5.0 and RTX cards explains.

Variable refresh rate and frame caps

Enable G-SYNC Compatible or the equivalent in the monitor menu and the driver, turn on V-Sync in the driver panel for the game, and turn it off in the game. Cap the frame rate a few frames below the refresh rate, for example 141 on a 144 Hz display, so that the frame rate never touches the upper edge of the variable range, where V-Sync would add latency. The explainer on VRR, G-SYNC, FreeSync and V-Sync covers the reasoning.

Frame-time budgets: the engineering view

A refresh rate is a deadline. Converting it to milliseconds tells you how much work the card may do per frame.

The arithmetic

Frame time in milliseconds equals 1,000 divided by frames per second. At 60 frames per second the budget is 16.67 ms. At 120 it is 8.33 ms, at 144 it is 6.94 ms, at 165 it is 6.06 ms and at 240 it is 4.17 ms. Every effect you enable consumes part of that budget, and the sum must fit under the deadline in the heaviest scene, not the average one.

Why 1% lows decide feel

Averages hide the slowest frames. If 1% of your frames take twice the budget, the game feels uneven even though the average looks good. Track 1% lows and frame-time graphs, as the glossary entry on frame time and 1% lows explains.

How DLSS buys budget

DLSS Super Resolution lowers shaded pixels. At Quality, the internal resolution is about two thirds of each dimension, which is about 44 percent of the pixels, so shading cost falls steeply while a fixed reconstruction cost remains. The guide to DLSS quality modes lists the internal resolutions, and the DLSS overview explains the rest of the family.

Resolution targets for a 16 GB, 300 W card

The RTX 5070 Ti has 70 SMs, 16 GB of GDDR7 and 896 GB/s of bandwidth, which the complete RTX 5070 Ti guide details.

1440p at high refresh rates

At 1440p, many games reach 120 to 165 frames per second with high settings, and heavy titles need DLSS Quality or Balanced. DLAA suits lighter games when you have spare budget. Keep ray tracing to the effects you notice, for example reflections and global illumination, and test shadows separately.

4K at 60 to 120 frames per second

At 4K, the card relies on upscaling. DLSS Balanced renders at about 2227 by 1253, and Performance renders at 1920 by 1080, both of which keep a high-detail source. Add frame generation to reach 120 Hz targets, provided the base frame rate stays above about 60.

Native 4K

Native 4K at maximum settings is realistic only in lighter or older games. In heavy titles, it will miss budget.

A settings priority ladder for a 16 GB card

Not every setting deserves the same attention. Tune in order of impact.

Tier one: resolution and upscaling

Internal resolution dominates shading cost. Choose the DLSS mode first, because it moves the whole frame budget. The newest presets improve Performance mode on RTX 40 and 50 cards, as the guide to DLSS presets explains.

Tier two: ray tracing and global illumination

These effects are expensive, and their cost depends on the implementation. Test each separately, and keep the ones that change the image in a way you notice. Enable Ray Reconstruction where available, since it improves denoising, as the article on Ray Reconstruction describes.

Tier three: shadows, volumetrics and reflections quality

Shadow resolution, volumetric fog and screen-space effects are common budget hogs. Reduce them one notch and compare, because many players cannot distinguish adjacent presets in motion.

Tier four: textures

Textures cost VRAM, not shading time. With 16 GB, keep them at the highest preset that does not trigger stutter. The VRAM guide explains the budget in how much VRAM you need.

Tier five: post-processing

Motion blur, depth of field, film grain and chromatic aberration are cheap, and they are matters of taste. Turn off effects you dislike, since they can also obscure artefacts when you evaluate upscaling.

VRAM budgeting on a 16 GB card

A memory budget prevents surprises.

What fills the memory

A typical modern game fills VRAM with a texture pool, geometry buffers, render targets, ray tracing acceleration structures and upscaling or frame generation buffers. A single 4K render target at four bytes per pixel is about 33 MB, and a high dynamic range target at eight bytes per pixel is about 66 MB. Deferred renderers keep several such targets, so working buffers can reach several hundred megabytes before textures are counted.

Texture pools

Most engines stream textures into a pool sized by the quality preset. A high preset may reserve several gigabytes. When the pool exceeds free VRAM, the engine evicts textures, and you see blurry textures or stutter.

How to check usage

Use an overlay that distinguishes allocated memory from memory actually used by the process. Many tools show both. Judge by stutter, not by the highest number, because engines often reserve more than they need.

Frame generation buffers

Frame generation and Ray Reconstruction add buffers. With 16 GB you usually have room. If you see stutter after enabling them, lower textures one step first.

Choosing a frame generation strategy

Frame generation is powerful and context-dependent.

When to use it

Use it when your base frame rate is above about 60 and your monitor refresh rate is much higher. At 1440p on a 165 Hz display, a base of 80 with 2x gives a smooth picture. At 4K on a 120 Hz television, a base of 60 with 2x fills the screen. The guide to Multi Frame Generation explains the multipliers, and the explainer on input lag discusses latency.

When to avoid it

Avoid it in competitive games where response matters, or when your base frame rate is low. Use upscaling to raise the base instead.

Reflex

Leave Reflex on, particularly with frame generation, as the guide to NVIDIA Reflex explains.

Per-genre starting points

Game types respond differently to settings.

Competitive shooters

Prioritise a high, steady frame rate and low latency. Use DLSS Quality or native, medium shadows and effects, textures high, Reflex on and frame generation off. Cap just below the refresh rate.

Open-world and story games

Prioritise image quality. Use DLSS Quality or Balanced, ray-traced reflections and global illumination if affordable, textures high and frame generation on if the base is healthy.

Racing and simulation

Smooth motion matters, and pop-in distracts. Keep view distance and texture quality high, use DLSS Balanced and watch for shimmering on thin objects.

Strategy games

These are often CPU-limited. Check graphics usage, and use DLAA or native with high texture quality, since the GPU has spare capacity.

Measuring the effect of each setting

A simple method turns opinions into data.

A repeatable test

Choose a demanding scene, and run it for a minute with each setting you test. Use an overlay that logs average frame rate, 1% low, frame time graph, board power, core temperature and VRAM use.

Change one thing at a time

Change a single setting between runs, so that you can attribute the difference. Write results in a table with the setting, average, 1% low and notes about picture quality.

Interpret the table

A setting that costs 10 percent of your frames and changes the picture little is a candidate to lower. A setting that costs 2 percent and improves the picture clearly is worth keeping.

Watch for processor limits

If graphics usage drops below about 90 percent while the frame rate is below your target, the processor or memory may be the limit, as the guide to CPU and system bottlenecks explains.

Thermals, noise and power while gaming

Settings affect heat and noise as well as frames.

Frame caps reduce heat

In lighter games, a frame cap lowers GPU load, board power and fan noise. A cap at your refresh rate minus three frames per second is a sensible default.

Undervolting as a setting

An undervolt lowers power and heat at similar performance, and it fits easily into a tuned setup. The RTX 5070 Ti undervolt guide explains the method, and the overclocking guide covers the opposite approach.

Case airflow

A good airflow path keeps clocks steady. If clocks sag in long sessions, improve airflow before you lower settings.

A worked example at 1440p and 165 Hz

This example shows the reasoning with illustrative numbers, not measurements.

The goal

A player wants 1440p at 165 Hz in a demanding single-player game. The frame budget is 6.06 ms. The cap is 162 frames per second.

The path

At native settings the game averages 85 frames per second, which is 11.8 ms per frame. DLSS Quality lowers the shaded pixels to about 44 percent, and the game reaches roughly 120 frames per second, 8.3 ms. DLSS Balanced reaches about 135, 7.4 ms. The player then enables 2x frame generation on a base of 100 to fill 165 Hz, after lowering shadows one notch to hold a stable base.

The result

The final setting is DLSS Balanced, medium-high shadows, ray-traced reflections on, frame generation at 2x, Reflex on and a cap of 162. The player checks 1% lows and finds them acceptable. These numbers illustrate the method, not a specific game.

Common mistakes

Forgetting the monitor settings

A monitor stuck at 60 Hz or with variable refresh rate off wastes the card.

Stacking anti-aliasing methods

Use one anti-aliasing method, and prefer DLSS or DLAA. Forcing driver-level options conflicts with them.

Judging presets by name

Quality presets differ between games. Compare individual settings, not the preset label.

Ignoring 1% lows

An average hides stutter. Track the slowest frames.

Upscaler internal resolutions in numbers

Knowing the real render resolution helps you predict cost.

1440p output

DLSS Quality renders at about 1707 by 960, which is roughly 1.64 million pixels against 3.69 million at native 1440p. Balanced renders at about 1485 by 835, near 1.24 million pixels. Performance renders at 1280 by 720, which is 0.92 million pixels. The reconstruction pass then produces the full 2560 by 1440 image.

4K output

At 3840 by 2160, native shading covers 8.29 million pixels. Quality renders at 2560 by 1440, 3.69 million pixels. Balanced renders at about 2227 by 1253, near 2.79 million. Performance renders at 1920 by 1080, 2.07 million pixels, and Ultra Performance renders at 1280 by 720.

Why savings are not linear

Shading cost falls roughly with pixel count, yet geometry, ray tracing set-up, the processor and the reconstruction pass do not shrink. A 25 percent pixel share therefore rarely gives four times the frame rate. Expect gains between 1.5 and 2.5 times, depending on how shading-bound the game is.

Reading an overlay like an engineer

An overlay gives the data needed to diagnose a setting.

Metrics to log

Log average frame rate, 1% low, frame time, GPU utilisation, board power, core clock, memory clock, temperature and VRAM use. Power reveals whether the card hits its limit, and clock reveals whether it throttles.

Interpreting patterns

If GPU utilisation is near 99 percent and the frame rate is below target, you are GPU-bound, so lower resolution or heavy effects. If utilisation is far below, you are limited by the processor, memory or a frame cap. If the clock sags while power sits at the limit, you are power-limited, and an undervolt may help. If the temperature is high and the clock drops, improve airflow or fan curves.

Spikes and stutter

Spikes in the frame-time graph with steady averages point to shader compilation, asset streaming or background tasks. Let shader caches build in the first minutes of a session, and keep the game on a fast drive. The guide to NVMe storage for gaming discusses storage choices.

Display choices that change the plan

The monitor decides your target.

Refresh rate and panel type

A 144 Hz panel gives a 6.94 ms budget. A 240 Hz panel halves the room you have. OLED panels have fast pixel response, which makes low frame rates look juddery, so a steady high frame rate matters more. LCD panels with variable overdrive can show flicker at low frame rates.

HDR

HDR adds a small cost, and it requires correct Windows calibration. Use native HDR in games that support it, and avoid Windows auto-HDR in games with strong native tone mapping.

Connection and cable

At 4K and 120 Hz or more, use a certified DisplayPort or HDMI 2.1 cable, because poor cables cause black screens and dropped modes. The article on 4K cables and connections lists the checks.

Ray tracing settings in detail

Ray tracing is not one switch. Each effect has its own cost profile.

Ray-traced reflections

Reflections trace rays from surfaces toward the scene. Cost scales with the number of reflective pixels and the ray count. Water and glass scenes are expensive, while matte interiors are cheap. Lower the reflection resolution before disabling the effect, because many engines trace at reduced resolution and denoise the result.

Ray-traced shadows

Shadow rays cost less per ray, yet there can be many of them for each light. Shadows from the sun are cheap, while many dynamic lights get costly. Compare ray-traced shadows with the high raster shadow preset, since the visual gap is often small.

Ray-traced global illumination and ambient occlusion

These effects add bounced light and contact shading, and they usually produce the largest visible improvement. They also use many rays per pixel, which means a denoiser has to clean noisy samples. DLSS Ray Reconstruction replaces hand-tuned denoisers with an AI model, which improves detail, as the article on Ray Reconstruction explains.

Path tracing

Path tracing models many bounces and replaces rasterised lighting entirely. It is the most demanding option. On a card of this class, use DLSS Performance at 4K or Balanced at 1440p, enable frame generation if the base frame rate allows, and accept that settings elsewhere must drop.

Choosing which to keep

Order effects by visible improvement per millisecond. Global illumination and reflections are usually first, shadows second and ambient occlusion last. Test with a screenshot comparison in a scene with strong light and reflective surfaces, and keep only effects you can identify in motion.

Latency stack: from click to photon

Responsiveness depends on a chain of stages.

The stages

Input is sampled by the game, the processor prepares the frame, the render queue holds it, the GPU shades it, the display scans it out and the panel responds. Reflex shortens the render queue by synchronising the processor with the GPU. A frame cap keeps the queue short, and variable refresh rate removes the wait for the next scan.

Where frame generation fits

Frame generation holds one real frame to interpolate between two, which adds roughly one real frame time of latency before Reflex reductions. At a base of 60 frames per second, that is about 16 ms. At a base of 100, it is about 10 ms. For single-player games, this is acceptable. For competitive games, avoid it. The article on input lag and frame generation explains the measurements.

Practical latency settings

Enable Reflex, or Reflex Boost where needed, cap the frame rate below the refresh rate, avoid triple buffering in the game, keep V-Sync set in the driver, and test with a latency overlay if your hardware supports it.

Troubleshooting common symptoms

Match the symptom to the fix.

Stutter every few seconds

Check for background tasks, overlays and storage activity. Shader compilation at the start of sessions is normal, and it settles once the cache fills. If stutter persists, lower texture quality one step to rule out VRAM pressure.

Screen tearing

Confirm that variable refresh rate is on in the monitor menu and the driver. If tearing appears above the refresh rate, the cap is missing.

Blur or ghosting in motion

Try a different DLSS preset or mode, update the driver, and check that no sharpening filter stacks on top. Lower the monitor overdrive setting if you see overshoot trails.

Low usage with a low frame rate

If graphics usage is low, the processor, memory or a frame limiter is the limit. Check for a stray cap in the game, the driver or a third-party tool.

Crashes at the desktop or in games

If crashes follow an overclock or undervolt, return to stock settings and retest. The RTX 5070 Ti overclocking guide covers stability testing.

Power and clock behaviour while gaming

The card does not run at one fixed speed.

Boost behaviour

GPU Boost raises the core clock in small steps, roughly 15 MHz each, while headroom exists in power, temperature and voltage. In a light scene the clock rises, and in a heavy scene the card reaches its 300 W target and the clock settles lower. A frame cap lowers load, so the card idles part of each frame and uses less power.

Why settings change power

Heavier effects keep more of the SMs busy, so board power rises. Ray tracing and high resolution typically draw the most, and a competitive title at 1080p may draw far less. Watching board power in your overlay shows how hard each setting works the card.

Power mode in the driver

Normal power mode suits most games. Prefer maximum performance only if you see clock drops in light scenes that cause stutter, and expect slightly higher idle power in exchange.

A one-page checklist

Use this order when you set up a new game.

Step one: confirm the platform

Check the refresh rate, variable refresh rate, driver and cap before launching.

Step two: pick the resolution and DLSS mode

Start with native or Quality at 1440p, and Balanced at 4K. Verify the preset in the on-screen indicator.

Step three: set textures and ray tracing

Keep textures high. Enable global illumination and reflections, then check frame times.

Step four: trim the expensive extras

Lower shadows, volumetrics and screen-space effects by one notch each, and compare the picture.

Step five: enable frame generation if needed

Only use it when the base frame rate is healthy, and keep Reflex on.

Step six: save the profile

Store your settings and write down the average and 1% low you achieved, so you can compare later.

Sharpening, anti-aliasing and filtering choices

Image clarity depends on a few cheap settings.

Sharpening

DLSS already reconstructs fine detail, so extra sharpening can create halos around edges. If the image looks soft, raise the in-game sharpness slightly, or switch to a higher DLSS quality mode, instead of stacking driver filters.

Texture filtering

Anisotropic filtering at 16x costs very little on a modern card and clearly improves textures viewed at an angle, such as roads and floors. Set it in the game where possible.

Motion clarity

Disable motion blur if you prefer a sharper moving image, and test your monitor's overdrive setting. A well-tuned panel and a steady frame rate matter more for clarity than any single graphics option.

Building a profile library

Save what you learn.

Per-game profiles

In the NVIDIA App, store settings per game, such as the frame cap, DLSS override and power mode. Keep a short note in each profile file about why you chose the values.

Revisit after updates

Drivers, game patches and DLSS models change behaviour. After a major update, rerun your test scene for a few minutes, compare the table and adjust.

Summary

For the RTX 5070 Ti, set the platform correctly first, convert your refresh rate into a frame-time budget, and use DLSS to buy budget at 1440p and 4K. Keep textures high with 16 GB, spend budget on the ray tracing effects you notice, cap the frame rate a few frames below the refresh rate with variable refresh rate on, and use frame generation when the base frame rate allows. Test one change at a time in a repeatable scene, record 1% lows and revisit your settings after updates. For the card's full specification and tuning options, read the RTX 5070 Ti complete guide.

Frequently asked questions about RTX 5070 Ti settings

What are the best settings for the RTX 5070 Ti at 1440p?

Use native resolution or DLAA in lighter games and DLSS Quality or Balanced in demanding ones. Keep textures high, enable Reflex, use variable refresh rate with a frame cap about three frames below your refresh rate, and spend leftover budget on ray-traced reflections and global illumination.

What DLSS mode should I use at 4K on the RTX 5070 Ti?

Start with Balanced, and move to Performance if you need more frames. Both start from a source of at least 1080p, so detail stays good, especially with the newer transformer models. Add frame generation only if your base frame rate is above about 60.

How do I cap the frame rate correctly?

Set the cap a few frames below the refresh rate, such as 141 on a 144 Hz display, using the NVIDIA App or the driver. Keep variable refresh rate on and V-Sync on in the driver and off in the game. This keeps frame times even and avoids the latency that V-Sync adds at the limit.

Should I use ray tracing on the RTX 5070 Ti?

Yes, selectively. Reflections and global illumination give the most visible change, and shadows often cost more than they add. Use DLSS and Ray Reconstruction to afford them, and check 1% lows. Path tracing is possible in some games with Performance upscaling.

Is 16 GB of VRAM enough for 4K on this card?

For most games with DLSS, yes. Extreme combinations, such as path tracing with high-resolution texture packs, can approach the limit. Monitor VRAM in your overlay, and lower texture quality by one step if you see stutter when the budget fills.

Which preset should I pick for DLSS?

Preset K is a safe choice for Quality, Balanced and DLAA, and newer presets such as M may look better in Performance on RTX 40 and 50 cards. Use the on-screen indicator to confirm what runs, and see the guide to DLSS presets.