What Resolution Scaling Actually Means
Resolution scaling sets an internal render size separately from the output resolution. A per-dimension scale of 67% makes both width and height about 67% of the output dimensions, so the rendered pixel area is roughly 0.67 × 0.67 = 44.89% of native. A game may then enlarge and reconstruct the frame for display.
This calculator models those dimensions mathematically; it does not inspect the game's live rendering buffers, monitor resolution, upscaler settings, GPU usage or measured FPS. DLSS, FSR, XeSS and engine-built scaling can choose their own ratios, align internal dimensions, or adjust resolution dynamically.
How to Use This Calculator
- Enter the intended output width and height, or choose a common resolution preset. These values are entered manually; they are not detected from your hardware.
- Choose a per-axis scaling percentage. Named choices are illustrative, not exact vendor-mode guarantees. Use Custom for your game's documented render percentage; values above 100% model supersampling.
- Read the integer-rounded render dimensions, total output/render pixels, actual relative pixel area, and the mathematical difference from native.
- Compare the bar chart and reference table to see how two-dimensional scaling compounds. The illustration does not simulate DLSS/FSR image quality or predicted FPS.
- Optionally enter both target internal dimensions in the reverse calculator. If their aspect ratio matches the output, click USE TARGET SCALE to apply the derived percentage. Check rounding and any mismatch notice.
- Use COPY SUMMARY or DOWNLOAD JSON to save your browser-local calculation, or RESET to restore the default example.
For example, enter a 3840 × 2160 output, then load the 4K → 1440p example. It uses an approximately 66.666667% linear scale to produce a rounded 2560 × 1440 internal resolution.
How the Calculation Works
Internal width ≈ round(output width × scale ÷ 100)
Internal height ≈ round(output height × scale ÷ 100)
Rendered pixels = internal width × internal height
Pixels relative to native = rendered pixels ÷ output pixels × 100.
Ignoring integer rounding, area percentage is the square of the linear scale percentage divided by 100. So 67% per axis corresponds to about 44.89% of output pixels, not 67% of the pixels. Because frames require whole-number dimensions, the calculator rounds each axis to its nearest integer and uses the actual rounded totals for final percentages.
The reverse calculator divides your target width and height by their respective output dimensions. When those ratios differ, one uniform scale cannot reproduce both target dimensions. Small engine-specific alignment or crop rules may also change real-world render dimensions.
Understanding Your Result
The figures below show example per-dimension percentages, assuming an ideal uniform scale and ignoring engine-specific alignment. Mode names in games and upscaler libraries can correspond to different percentages, and dynamic resolution can change the actual input size over time.
| Example linear scale | Approximate pixel area | Meaning |
|---|---|---|
| 100% | 100% | Native internal dimensions |
| 77% | 59.29% | Illustrative high-resolution render |
| 67% | 44.89% | Illustrative lower-resolution render |
| 58% | 33.64% | Illustrative balanced area |
| 50% | 25% | Quarter of the native pixels |
| 33% | 10.89% | Very low input pixel count |
| 150% | 225% | Supersampling: more input pixels than output |
Pixel workload proxy is not an FPS estimate. Actual game performance depends on GPU, CPU, shading complexity, memory bandwidth, upscaler overhead, frame generation, frame rate limits and engine design.
Benefits and Practical Uses
- See how many pixels an internally scaled frame would contain at a selected output resolution.
- Understand why halving both dimensions leaves only one-quarter of the original pixel area.
- Work backwards from a target such as 2560 × 1440 inside a 3840 × 2160 output, when ratios match.
- Compare standard example scales to determine a sensible input-resolution range for manual testing.
- Export transparent, reproducible calculations without uploading data or claiming a hardware benchmark.
Common Mistakes to Avoid
- Treating the scale percentage as total pixel percentage. The number applies to each axis; pixel area changes approximately with its square.
- Assuming every Quality/Balanced mode uses the same fixed scale. Technology, game, version and dynamic resolution settings can alter input dimensions.
- Assuming fewer pixels guarantees a proportional FPS gain. CPU bottlenecks, upscaling cost and other factors prevent exact FPS prediction from geometry alone.
- Ignoring integer and engine-alignment rules. This page uses nearest-integer rounding; a game might align dimensions to specific pixel multiples.
- Confusing scaling with physical pixel density. PPI comes from display size and native resolution; a game’s internal render dimensions do not change physical PPI.
Frequently Asked Questions
Why does 67% scale look almost as sharp as native?
Modern temporal upscalers like DLSS and FSR reconstruct detail using information from previous frames, not just simple pixel stretching, which is why they preserve far more clarity than the raw render resolution alone would suggest.
Is a lower scale percentage always a bigger FPS gain?
Generally yes for the GPU-bound render workload, though the actual FPS gain also depends on how much of your frame time is spent on GPU-bound rendering versus CPU-bound game logic, which scaling doesn't affect.
What's the difference between resolution scaling and PPI?
Resolution scaling changes what the GPU renders internally before upscaling it back to your native resolution; PPI is a fixed property of your physical display's pixel density and doesn't change with in-game settings. Check that separately with the PPI Calculator.
Why Games Render Below Your Display's Native Resolution
Games sometimes render internally at fewer pixels than the selected output resolution to reduce certain GPU workloads. The resulting frame can be upscaled using spatial, temporal or machine-learning reconstruction, but its appearance depends on motion, image content and the actual upscaler settings. Some modes use dynamic resolution, so there is no single fixed input resolution.
At 3840 × 2160 output, a uniform 50% scale gives 1920 × 1080 internally—one-quarter of the output pixel count. That arithmetic is useful for understanding workload changes, but it cannot tell you the actual GPU frame time or FPS on a particular PC.
Conclusion
Use the calculated render dimensions and pixel percentages as a consistent way to compare geometric scaling options, then check real game settings and benchmark results before drawing performance conclusions. For display aspect geometry, use the Aspect Ratio Calculator; for physical pixel density, use the PPI Calculator.