Render scale is a graphics setting that defines the internal resolution of the 3D scene as a percentage of the display or output resolution, while the user interface usually stays at native resolution. Among graphics settings in gaming, it is one of the most direct levers on performance, because the number of shaded pixels grows with the square of the scale factor.
A value of 100 percent renders the scene at native resolution. Lower values render fewer pixels and upscale the image, which raises frame rates at the cost of sharpness, while values above 100 percent perform supersampling, which improves image quality at a steep performance cost.
How render scale changes the rendering pipeline
Render scale works by resizing the render targets that the engine draws the 3D world into. Geometry, lighting, shadows and post-processing are computed at the reduced or increased resolution, and a final resampling pass maps the result to the output resolution before the HUD and menus are drawn on top at full sharpness.
Most games apply the percentage to each axis separately. A render scale of 50 percent at 3840 x 2160 therefore produces 1920 x 1080, which is one quarter of the pixels, not one half. Some titles apply the percentage to the total pixel count instead, so the same number can mean very different workloads in different games.
The table below shows typical values for a 4K output when the percentage applies per axis.
| Render scale | Internal resolution | Share of native pixels |
|---|---|---|
| 50% | 1920 x 1080 | 25% |
| 67% | 2560 x 1440 | About 44% |
| 75% | 2880 x 1620 | About 56% |
| 100% | 3840 x 2160 | 100% |
| 150% | 5760 x 3240 | 225% |
Because the per-pixel workload scales roughly with pixel count, pixel-bound scenes respond almost proportionally. Scenes limited by the CPU, draw calls or geometry processing gain much less, which is why lowering render scale does not always raise the frame rate.
Upscaling and supersampling methods
The quality of a reduced render scale depends heavily on the upscaling method that converts the internal image to the output resolution. Simple spatial filters such as bilinear filtering only interpolate between neighboring pixels and produce a soft image, while temporal upscalers reuse information from previous frames to reconstruct detail.
| Method | Type | Typical result below 100% |
|---|---|---|
| Bilinear scaling | Spatial | Soft, blurry detail |
| Spatial sharpening (FSR 1) | Spatial with sharpening | Crisper edges, some artifacts |
| Engine TAAU | Temporal | Good detail, some ghosting |
| DLSS, FSR 2 or later, XeSS | Temporal reconstruction | Near-native detail at 50-67% |
| Supersampling above 100% | Downsampling | Very clean edges, high cost |
In many modern titles, the presets of DLSS, FSR and XeSS are in effect fixed render scale values with a dedicated reconstruction algorithm. A “Quality” preset typically renders at about 67 percent per axis and a “Performance” preset at 50 percent. When such an upscaler is active, the separate render scale slider is often locked or hidden to avoid double scaling.
Values above 100 percent act as ordered-grid supersampling: the engine renders more pixels than the display can show and averages them down. This is a brute-force form of anti-aliasing that also reduces shimmering on fine geometry, but it is rarely efficient compared with dedicated anti-aliasing techniques.
Render scale compared with lowering display resolution
Reducing render scale is usually better than lowering the output resolution in the display settings. Changing the output resolution forces the monitor or the GPU driver to stretch the entire frame, including text and interface elements, while render scale keeps the interface sharp and lets the game choose a high-quality upscaler.
| Option | What it changes | Interface sharpness | Typical use |
|---|---|---|---|
| Render scale | 3D scene resolution only | Native | Fine-tuning frame rate |
| Output resolution | Entire frame | Reduced | Weak hardware or old monitors |
| Dynamic resolution | Scene resolution per frame | Native | Holding a target frame rate |
| Texture quality | Texture detail and memory | Not affected | Fixing VRAM shortages |
Dynamic resolution scaling is an automated variant of render scale. The engine measures GPU frame time and adjusts the internal resolution, often between 60 and 100 percent, to keep a target such as 60 frames per second. Consoles use this approach widely, while PC games often offer it as an optional mode next to a fixed slider.
Choosing a render scale value
The right render scale depends on output resolution, screen size, viewing distance and the available upscaler. Higher output resolutions tolerate lower percentages, because the internal image still contains many pixels; at 1080p, even small reductions become visible quickly.
| Situation | Suggested setting | Reason |
|---|---|---|
| 4K display, demanding game | 50-67% with temporal upscaler | Large frame rate gain, modest detail loss |
| 1440p display, mid-range GPU | 75-85% | Balanced sharpness and speed |
| 1080p display | 90-100% | Low base resolution shows blur quickly |
| Spare GPU headroom | 110-150% | Cleaner edges and less shimmer |
| CPU-limited game | Keep at 100% | Lowering it brings little benefit |
A practical method is to change one step at a time and compare both frame rate and image clarity in a demanding scene. Monitoring tools that show GPU utilization help: if the GPU is not near full load, the bottleneck lies elsewhere and render scale will not help.
Limitations and common mistakes
Render scale is powerful but often misunderstood. The most common mistake is assuming linear scaling, for example expecting 50 percent to halve the workload when it actually removes three quarters of the pixels on a per-axis implementation.
- Fine detail suffers first: foliage, wires, fences and distant text break up at low scales.
- Post-processing effects such as depth of field or screen-space reflections may also run at reduced resolution and look noisier.
- Stacking scalers by combining a low render scale with an upscaler preset can produce a very low internal resolution.
- Supersampling increases VRAM use, which can cause stutter on cards with limited memory.
- Competitive players may lose visibility of small distant targets when the scale is too low.
Another misconception is that render scale and field of view or draw distance interact in a simple way. They are independent: render scale changes pixel density, while the other two settings change how much of the world is drawn.
A plain-language summary
Render scale decides how detailed the picture is before it reaches your screen. Think of painting a picture on a smaller canvas and then enlarging it with a projector. A smaller canvas is faster to paint, but the enlarged picture looks softer.
Turning render scale down makes a game run more smoothly, and turning it up makes the picture cleaner but slower. Menus and text usually stay sharp either way, which is why this setting is a gentle way to gain speed without making everything blurry.
An example from practice
A player with a mid-range graphics card connects a PC to a 4K television and starts a demanding open-world game. At 100 percent render scale, the game averages about 38 frames per second, and camera movement feels uneven. The player sets render scale to 67 percent with a temporal upscaler, which renders the scene at 2560 x 1440 and reconstructs it to 4K.
The frame rate rises to roughly 62 frames per second, and from a couch about three meters away the image looks almost as sharp as before. Only thin power lines and distant tree branches show slight shimmer. The interface, subtitles and map text remain crisp, so the player keeps this setting and achieves smooth play near 60 frames per second without lowering any other quality option.