Resolution Scale Calculator

Calculate render resolution from native resolution and a scale factor (DLSS, FSR, XeSS modes).

Everyday DLSS / FSR Bidirectional
Rate this calculator · 4.5 (2)

Resolution Scale

DLSS / FSR / XeSS presets · scale factor or target res · pixel count

Instructions — Resolution Scale Calculator

1

Pick the native resolution

The native (display) resolution is what your monitor shows physically. Quick picks cover the standard sizes: 720p, 1080p, 1440p, 4K, 8K. The default is 1920×1080.

2

Set scale factor or target resolution

"By scale factor" mode multiplies native by the scale to get the render resolution — pick from DLSS quality presets (Ultra Performance 0.50, Performance 0.67, Balanced 0.75, Quality 0.89, Native 1.0). "By target res" mode goes the other way: enter the render resolution and get the scale factor back.

3

Read the FPS estimate

FPS multiplier is approximated as 1 ÷ scale², because GPU shader work scales with pixel count. A 0.75x scale reduces pixels to 56 percent and gives a 1.78x FPS multiplier (78 percent more frames). Actual gain varies by game and upscaling quality.

Sweet spot: 0.75x scale (DLSS Balanced) is the standard recommendation for high-end gaming — near-native quality at 1.78x FPS.
Avoid bilinear: the FPS gain is the same whether you use DLSS, FSR, XeSS, or no upscaler at all. The image quality is not. A good upscaler is what makes the trade-off worthwhile.

Formulas

The calculator works in two directions: native × scale gives render resolution, or render ÷ native gives scale. Pixel count and FPS estimate follow from the dimensions.

Render resolution
$$ W_{render} = W_{native} \times s, \;\; H_{render} = H_{native} \times s $$
Both width and height are multiplied by the same scale s. Aspect ratio is preserved as long as scale is uniform.
Scale factor from target
$$ s = \frac{W_{render}}{W_{native}} = \frac{H_{render}}{H_{native}} $$
If the render width and height divided by native give the same number, the aspect ratio matches. If they differ, the calculator warns of an aspect-ratio mismatch.
Pixel reduction
$$ \Delta P = \left(1 - \frac{P_{render}}{P_{native}}\right) \times 100\% $$
Pixel count scales with scale². A 0.75 scale gives 0.75² = 0.5625, so render uses 56 percent of native pixels and reduction is 44 percent.
FPS multiplier
$$ k_{fps} \approx \frac{1}{s^2} $$
In GPU-bound games, frame time scales with pixel work. Half the pixels, roughly double the frame rate. CPU-bound titles see smaller gains.
DLSS Quality Modes
$$ s \in \{0.50, 0.67, 0.75, 0.89, 1.00\} $$
NVIDIA documents these as Ultra Performance, Performance, Balanced, Quality, and DLAA. AMD FSR and Intel XeSS use the same ratios with their own names.
Supersampling
$$ s > 1: \;\; \text{e.g. } 1.5\times\text{ DSR} \Rightarrow s = 1.5 $$
NVIDIA Dynamic Super Resolution and AMD VSR render above native and downscale. The image is sharper but pixel work grows with scale², so a 1.5x scale costs 2.25x GPU work.

Reference

Render Resolution from Common Scales (Native 1920×1080)
ScaleRenderPixelsReductionFPS ×Mode
0.50x960×5400.52 MP75%4.00xDLSS Ultra Performance
0.58x1113×6260.70 MP66%2.94xDLSS Ultra Performance (4K)
0.67x1280×7200.92 MP56%2.25xDLSS Performance
0.75x1440×8101.17 MP44%1.78xDLSS Balanced
0.89x1707×9601.64 MP22%1.26xDLSS Quality
1.00x1920×10802.07 MP0%1.00xNative / DLAA
1.50x2880×16204.67 MP-125%0.44xDSR / VSR (downsample)
2.00x3840×21608.29 MP-300%0.25x4K DSR from 1080p

Native resolutions and DLSS modes

DLSS quality modes target an internal render resolution that scales with native. Source: NVIDIA DLSS technical documentation.

Native resolutions
NamePixels
720p1280×720
1080p1920×1080
1440p2560×1440
4K UHD3840×2160
5K5120×2880
8K UHD7680×4320
DLSS internal res @ 4K
ModeRender
Ultra Performance1280×720
Performance1920×1080
Balanced2227×1253
Quality2560×1440
DLAA / Native3840×2160

Source: NVIDIA DLSS official documentation; AMD FSR Whitepaper; VESA Display Standards. The FPS multiplier figures are pure shader-pixel approximations; real gains depend on engine, ray tracing, and CPU bottlenecks.

Article — Resolution Scale Calculator

Resolution Scale Calculator: Render vs Display Resolution

A resolution scale calculator multiplies a native (display) resolution by a scale factor to get the internal render resolution. For 1920×1080 at 0.75 scale, the GPU renders 1440×810 (44 percent fewer pixels, roughly 1.78x more frames per second). DLSS Balanced uses 0.75, DLSS Performance 0.67, DLSS Ultra Performance 0.50. The pixel count scales as the square of the scale factor.

What the resolution scale calculator does

The calculator answers two related questions. Forward: at this native resolution and this scale factor, what is the GPU rendering internally? Reverse: at this native and this target render resolution, what scale factor is in play? It also reports the pixel count, the pixel reduction versus native, and a rough FPS multiplier.

The pixel reduction matters because GPU shader work scales linearly with pixel count. Halving the pixels roughly halves the time spent on per-pixel computation (lighting, shadows, post-processing), which is the dominant cost in modern rendering pipelines that use deferred shading and ray tracing.

Did you know

Console games have used dynamic resolution scaling since the Xbox 360 era. Microsoft’s Forza Motorsport on Xbox Series X targets 4K 60 FPS but drops the render resolution as low as 2560×1440 (0.67 scale) during heavy scenes, then ramps back to native when the GPU has headroom. The screen never blanks; only the internal pixel count changes.

How resolution scale is computed

Render width equals native width times the scale factor. Render height uses the same scale factor, which keeps the aspect ratio fixed. The pixel count of the render image is render width times render height, and it scales as the square of the scale factor: a 0.5 scale gives 0.25 the pixels, a 0.75 scale gives 0.5625 the pixels, a 0.89 scale gives 0.79 the pixels.

Going the other direction, dividing render width by native width recovers the scale factor. The calculator does both, and warns if the x and y scales differ — an asymmetric scale changes the aspect ratio and produces a stretched image.

Resolution scale presets: DLSS, FSR, XeSS

The three major upscaling technologies use overlapping but not identical scale factors. NVIDIA DLSS uses 0.33 (Ultra Performance), 0.50 (Performance), 0.58 (Balanced), 0.67 (Quality), and 1.0 (DLAA, anti-aliasing only). AMD FSR 2 and later use 0.50, 0.59, 0.67, and 0.77. Intel XeSS uses 0.50, 0.67, and 0.77. All three apply the scale uniformly to width and height.

  • Ultra Performance: scale 0.50, ~4x FPS gain, AI rebuild required
  • Performance: scale 0.67, ~2.2x FPS gain, common for 4K targets
  • Balanced: scale 0.75, ~1.78x FPS gain, recommended default
  • Quality: scale 0.89, ~1.26x FPS gain, almost native-quality
  • DLAA / Native: scale 1.0, no FPS gain, anti-aliasing only
  • Supersampling: scale > 1.0, FPS cost, sharper image

Resolution scale and FPS

The textbook approximation for FPS multiplier is one divided by scale squared. At 0.75 scale that gives 1.78x, at 0.67 it gives 2.23x, at 0.50 it gives 4.00x. Real-world numbers are lower because some work in a frame — geometry processing, CPU draw calls, post-processing — does not scale with pixel count. A typical AAA game at 0.75 scale sees 50 to 70 percent more FPS, not 78 percent.

Balanced 0.75x
+78% FPS
recommended
Performance 0.67x
+123% FPS
competitive
Ultra Perf 0.50x
+300% FPS
8K targets

Pixel count by resolution scale

1080p native is 2.07 megapixels. At 0.75 scale that drops to 1.17 MP (44 percent reduction). 4K native is 8.29 MP and 0.5 scale takes it down to 2.07 MP — the same pixel count as 1080p native. This is why DLSS Ultra Performance at 4K renders internally at 720p and reconstructs upward.

An 8K native target of 33.18 MP at 0.50 scale becomes 8.29 MP, which is 4K native. Most current GPUs can run 4K reasonably but struggle with 8K, so DLSS Ultra Performance is the way 8K gaming is actually rendered. The image you see is reconstructed by the AI upscaler from a 4K internal buffer.

The same arithmetic explains why DLSS Performance at 4K renders at 1080p internally: 3840 × 0.50 = 1920, 2160 × 0.50 = 1080. A GPU that draws 1080p comfortably at 100 FPS can drive a 4K monitor at the same 100 FPS, with the upscaler doing the heavy lifting. This is the central trick of every modern upscaling technology.

Resolution scale above 1.0: supersampling

A resolution scale greater than 1.0 is supersampling: the GPU renders above native and downsamples to the display. NVIDIA Dynamic Super Resolution (DSR) and AMD Virtual Super Resolution (VSR) expose this in driver settings. A 1.5x DSR scale renders at 1.5 times native in each dimension, costing 2.25x the GPU work for sharper geometry and built-in anti-aliasing.

Supersampling is expensive

A 1.5x scale halves your frame rate (cost rises as scale² = 2.25x). 2.0x supersampling renders 4x the pixels and slashes FPS to roughly 25 percent of native. Reserve supersampling for older or visually demanding titles where you have headroom, not for the latest releases.

Picking a resolution scale

If the goal is image quality, run 1.0 (native) or 0.89 (DLSS Quality), which is almost indistinguishable from native in motion. If the goal is the most playable result on a mid-range GPU at 1440p or 4K, 0.75 (Balanced) is the standard recommendation: roughly 1.5x to 1.78x FPS with a barely perceptible quality loss in motion.

Tip

For competitive shooters where input latency matters more than fidelity (CS2, Valorant, Apex Legends), drop to 0.67 (Performance) or 0.50 (Ultra Performance). The reduced rendering time also shortens the input-to-photon latency by 5 to 15 ms.

Common resolution scale mistakes

The most common mistake is assuming the FPS gain is linear with scale. A 0.5 scale does not double FPS — it quadruples it, because pixel count is scale squared. A 0.9 scale does not lose 10 percent of FPS — it loses about 23 percent (1 − 0.9² = 0.19). The relationship is quadratic in both directions.

The second mistake is comparing DLSS at 0.67 with native upscaling at 0.67. The scale factor is the same, but the image quality is not. DLSS reconstructs detail using motion vectors and trained networks; native bilinear upscaling does not. Without a quality upscaler, anything below 0.85 looks visibly soft. With one, even 0.5 stays sharp in motion.

Resolution scale cheat sheet
0.50x 1/4 pixels, 4x FPS
0.67x 45% pixels, 2.23x FPS
0.75x 56% pixels, 1.78x FPS
0.89x 79% pixels, 1.26x FPS
1.00x native, 1x FPS
1.50x DSR 2.25x pixels, 0.44x FPS

FAQ

Resolution scale is the ratio between the resolution the GPU renders at and the native (display) resolution of the monitor. A 0.75 scale on a 1080p monitor means the GPU renders 1440×810 internally, then upscales the image to 1920×1080 for display. Lower scale = fewer pixels to draw = more frames per second.
Render width = native width × scale, render height = native height × scale. For 1920×1080 native at 0.75 scale, render is 1440×810. Both dimensions use the same scale, so the aspect ratio stays 16:9.
NVIDIA DLSS: Ultra Performance 0.50, Performance 0.67, Balanced 0.75, Quality 0.89, DLAA 1.0. AMD FSR: Performance 0.50, Balanced 0.59, Quality 0.67, Ultra Quality 0.77 (FSR 2 and later). Intel XeSS Performance 0.50, Quality 0.67, Ultra Quality 0.77. All are uniform XY scales.
Pixel count goes as scale², so FPS multiplier is roughly 1 ÷ scale². Scale 0.75 gives 1.78x FPS, scale 0.67 gives 2.23x FPS, scale 0.50 gives 4.00x FPS. The model assumes GPU-bound gameplay; if you are CPU-bound the gain is smaller.
Resolution scaling is the underlying technique; DLSS is one implementation of it. DLSS renders at a lower internal resolution and uses a neural network to upscale to display resolution. FSR and XeSS do the same thing with different upscaling algorithms. Pure resolution scaling without an AI/temporal upscaler relies on bilinear filtering, which looks blurry.
Yes. Most modern games expose a percentage slider (50 to 200 percent) independent of DLSS/FSR. Some games allow setting an internal render resolution directly. The calculator above supports any scale from 0.25x to 2.0x and reports the render dimensions, aspect ratio, and FPS estimate.
On a strong GPU at high refresh rate, 0.89 (DLSS Quality) preserves image quality almost perfectly. On mid-range hardware at 1440p or 4K, 0.75 (DLSS Balanced) is the standard recommendation. For competitive shooters where FPS matters more than fidelity, 0.67 (Performance) is common. Below 0.50 the upscaling artifacts start to show.
Supersampling means rendering above native (scale > 1.0). NVIDIA DSR and AMD VSR let you render at, say, 1.5x and downsample to native. Visual quality improves — especially anti-aliasing — but GPU cost grows with scale², so 1.5x supersampling costs 2.25x the rendering work.
Only if the width and height use different scales. The standard practice is a single uniform scale applied to both, preserving aspect ratio. If you enter mismatched target dimensions in the calculator, it warns “aspect mismatch” and reports both x and y scales.
The calculator uses 1 ÷ scale², a textbook approximation for fragment-shader-bound games. Real titles see smaller gains because some work (geometry, CPU, post-processing) does not scale with pixels. DLSS 3 frame generation adds another multiplicative speedup on top, but that is independent of the render scale.