By Walter Jobs, Technology writer and editor · Published 9 October 2026
Short answer: no. Upscaling makes your graphics card’s job smaller, and when your processor is the limit, your graphics card’s job was never the problem. Turning DLSS on in a processor limited game typically changes the frame counter by a percent or two, which is within the noise. Frame generation is the one exception, and it is an exception with a catch worth understanding before you rely on it.
What upscaling actually does
When you enable DLSS Quality at 1440p, the game stops rendering 3.7 million pixels and starts rendering about 1.6 million, then reconstructs the rest. That is a reduction of roughly 57% in the pixel work handed to the card. It is a large saving, and it is entirely a graphics card saving.
Nothing about that touches the processor’s workload. Before any pixel is shaded, the processor has to decide what exists in the scene, run the physics, update the AI, work out what is visible, and issue the draw calls that tell the card what to render. That work depends on how much is happening in the world, not on how many pixels the result will occupy. A thousand objects is a thousand objects whether you are rendering them at 1080p or 4K.
So if your processor can prepare 90 frames per second and your card can draw 140, you get 90. Switch on upscaling, the card can now draw 220, and you still get 90. You have made the faster part faster.
The arithmetic, with numbers
| Scenario | CPU can prepare | GPU can draw | You get | Upscaling helps? |
|---|---|---|---|---|
| Card limited, native | 140 fps | 62 fps | 62 fps | Yes, substantially |
| Same machine, DLSS Quality | 140 fps | 96 fps | 96 fps | A 55% gain |
| Processor limited, native | 88 fps | 135 fps | 88 fps | No |
| Same machine, DLSS Quality | 88 fps | 205 fps | 88 fps | Nothing at all |
| Balanced, native | 105 fps | 100 fps | 100 fps | Partially, until you hit 105 |
Row five is the interesting one and the reason people report inconsistent results. On a well matched machine, upscaling helps right up to the point where you run into the processor ceiling, then stops abruptly. Someone who gains 20 frames and then nothing from a further quality reduction has not found a bug; they have found their processor.
Upscaling can turn a card limit into a processor limit
This is the part that goes unsaid, and it explains most of the confusion around the subject.
Before you enable DLSS, your card may well be the slower half, which means the processor has spare capacity and nothing reveals it. Enable DLSS and you remove most of the card’s work. The card is now far faster than it was, which means the processor is now the slower half. You have not caused a processor bottleneck; you have uncovered one that was always there and simply hidden behind the card.
This is why the first notch of upscaling often feels transformative and every notch after it feels useless. Quality mode took you to the processor ceiling. Performance mode has nowhere left to take you. If you set upscaling to its most aggressive level and the frame rate does not move from where Balanced put it, you have found the ceiling, and no graphics setting will move it.
Frame generation is different, and the difference matters
Frame generation does not render frames the normal way. It takes two rendered frames and manufactures an intermediate one, largely on dedicated hardware. Because that inserted frame does not require the processor to simulate anything, frame generation genuinely does raise the number on your counter when you are processor limited, which upscaling cannot do.
Three things to understand before treating that as a solution.
- It adds latency rather than removing it. The system must hold a rendered frame back in order to insert something between it and the next one. Your displayed rate goes up while your input response gets slightly worse. For a slow paced single player game that trade is often fine. For anything competitive it is the wrong direction.
- It costs some processor time of its own. Driving the feature is not free, so in a severely processor limited game the real frames underneath can actually arrive slightly slower than before.
- It needs a decent base rate to feel right. Generating from 30 frames per second produces 60 on the counter that still feels like 30 to your hands, with visible artefacts around fast movement. From 70 upward it works well. The feature multiplies what you have rather than rescuing what you do not.
So frame generation raises the number. Whether it improves the experience depends on what you were going to do with those frames.
Does it differ between DLSS, FSR and XeSS?
Not for this question. All three reduce the internal render resolution and reconstruct, all three save graphics card work, and none of them reduce the draw calls or the simulation the processor has to get through. They differ in image quality, in which hardware they run on, and in how they handle motion, but against a processor limit they are equally ineffective.
| Feature | Reduces GPU work | Reduces CPU work | Raises counter when CPU limited |
|---|---|---|---|
| DLSS Super Resolution | Yes | No | No |
| FSR upscaling | Yes | No | No |
| XeSS | Yes | No | No |
| Frame generation | Partly | No, costs a little | Yes, with added latency |
| Resolution scaling | Yes | No | No |
| Lower graphics preset | Yes | Sometimes, slightly | Rarely, and only a little |
The last row carries a small qualification. A few settings do carry processor cost, notably draw distance, crowd density, shadow cascade count and anything governing how many objects are simulated at once. Those are the settings to reduce when the processor is your limit, and they are usually filed under gameplay or world detail rather than under graphics quality.
What to do instead
If upscaling did nothing for you, the useful next step is to find out how far behind your processor actually is, because the answer determines whether this is worth money.
- Turn down the settings that cost processor time, not the ones that cost pixels. Draw distance and crowd density first.
- Check you are running two memory sticks. Single channel memory starves the processor and is free to fix if you have a spare slot.
- Raise your resolution. If you are processor limited, going from 1080p to 1440p costs you almost nothing and looks considerably better. This is the single most underused response to a processor limit.
- Measure the gap before buying. Put your parts into the bottleneck calculator to see the size of it and which upgrade changes the number.
If you are not certain the processor is your limit, the symptom list in 7 signs of a CPU bottleneck will settle it in a couple of minutes.
Frequently asked questions
Does DLSS reduce CPU usage at all?
Marginally, and not in a way you will notice. There is a small amount of processor work involved in managing the feature, and a small reduction in some driver side overhead because fewer pixels are being handled. The two roughly cancel. Nothing about upscaling reduces the simulation, the physics or the draw call submission that make up the bulk of a game’s processor load.
Why did DLSS give me frames in one game and nothing in another?
Because you were limited by different parts in each. In the game where it helped, your card was the slower half and upscaling made it faster. In the game where it did nothing, your processor was already the slower half, so making the card faster changed nothing. The same machine can be in both situations depending on the title.
Should I use frame generation if I am CPU limited?
For a slower single player game where the counter and the smoothness matter more than response time, yes, provided your real frame rate is already around 60 or above. For competitive play, no. Frame generation trades latency for displayed frames, and latency is the thing you are protecting in those games.
Does lowering my resolution help a CPU bottleneck?
It makes it worse in relative terms. Lowering resolution reduces the card’s work and leaves the processor’s unchanged, so the processor becomes a larger share of the limit and your frame rate barely moves. If the processor is your ceiling, raising resolution is the better move, since the extra visual quality is effectively free.
Is DLSS worth using when I am not bottlenecked by anything?
Yes, usually. On a balanced machine with no frame cap, Quality mode typically gains meaningful frames at image quality most people cannot distinguish from native in motion, and it lowers power draw and temperature as a side effect. The argument against it is specific scenes where reconstruction struggles, such as fine wires, dense foliage in motion and some particle effects.
The frame rate pairs in the table above are illustrative figures produced by our own model to show the arithmetic, not measurements from a particular game or machine. The model and its limits are described on how we calculate this.