- Top Pick: Lenovo Legion Go 2
- Runner-up: Lenovo Legion Go
- Also consider: ASUS ROG Xbox Ally
Every emulator has a resolution setting, and almost none of them label it the same way. One calls it internal resolution, another rendering resolution, a third just offers 2x or 3x — and the numbers are not comparable between systems, because each multiple starts from a different native resolution. A 3x setting in a PlayStation emulator renders fewer pixels than a 2x setting in a PlayStation 2 emulator, and neither label tells you how the result maps onto your screen.
As an Amazon Associate, we earn from qualifying purchases.
This guide explains the arithmetic underneath the slider, using only numbers you can check with a calculator: what a multiple multiplies, why the pixel count grows faster than the label suggests, when whole-number scaling matters, and how to pick the multiple that fits your panel. Everything here assumes games you dumped from your own discs and cartridges. Our separate FPS guide treats resolution as a performance lever; this one is about what the numbers mean.
This article contains affiliate links, and purchases made through them may earn us a commission at no additional cost to you.
Quick Answer
Resolution scaling multiplies a game’s native output in both dimensions, so 3x renders nine times the pixels, not three. Sharpness depends on how the rendered image maps onto your physical panel: whole-number multiples keep 2D pixels uniform, and rendering slightly above the panel then downsampling smooths 3D edges. Match the multiple to your screen, not to the biggest number.
Two Resolutions, One Confusing Slider
An emulator performs two separate scaling jobs. First it renders the game into an internal framebuffer — the resolution the scaling setting controls. Then it scales that finished image to your display, a second, simpler stretch. The names differ by project: Dolphin and PCSX2 call it Internal Resolution, PPSSPP calls it Rendering Resolution (its documentation defines it as a multiplier of the PSP’s original resolution), and DuckStation labels it Internal Resolution Scale. In every case the multiple refers to the original console’s output, never to your screen — and a ratio is meaningless until you know what it is a ratio of.
What a Multiple Actually Multiplies
The multiple applies to both dimensions at once, so the pixel count grows with the square of the label: 2x renders four times the pixels, 3x nine times, 4x sixteen times, and 5x twenty-five times. Worked examples make the cost concrete. A PlayStation frame at 320×240 holds about 77,000 pixels; at 5x it becomes 1600×1200, roughly 1.92 million — nearly a full 1080p panel’s 2.07 million. A GameCube frame at 640×528 holds about 338,000 pixels; at 3x it becomes 1920×1584, roughly 3.04 million — more than a 1080p screen can display.
This is also why a smaller label can produce the sharper image. Three times the PlayStation’s 240 lines is 720 rendered lines; two times the PlayStation 2’s 480 lines is 960. The 2x image is the taller, finer one because its starting point was twice as high. Whenever you compare settings across emulators, convert both to actual pixels first — the labels alone will mislead you.
Native Resolutions: Where Every Multiple Starts
| System | Native output |
|---|---|
| NES, SNES and Genesis era | About 240 lines (256×240 class) |
| PlayStation | About 240 lines, typically 320×240 |
| Nintendo 64 | 240p, with some titles at 480i |
| PlayStation 2 | 480i or 480p |
| GameCube | 480p class (640×528 framebuffer) |
| PSP | 480×272 |
| Nintendo DS | 256×192 per screen |
| Nintendo 3DS | 400×240 top screen |
Widths vary from game to game on the older consoles, but heights are stable enough to plan with, which is why this guide does its maths in lines. Find your main system’s line count above, and every calculation below becomes a single division.
Integer Scaling vs Fractional Scaling
Integer scaling multiplies by a whole number, so every source pixel becomes an identical block: 2×2 panel pixels at 2x, 5×5 at 5x, and pixel art stays perfectly uniform. Fractional scaling breaks that uniformity. Stretching 240 lines across a 1080-line panel takes 4.5x, so some source pixels land four panel pixels tall and their neighbours land five. In a still image you may not notice; in a scrolling 2D game the uneven columns shimmer as they move. RetroArch exposes exactly this choice as the Integer Scale option in its video scaling settings.
For 3D games the calculus flips. Polygon edges are continuous geometry rather than pixel blocks, so a fractional multiple renders them at whatever size you ask for, with no unevenness to shimmer. Integer scaling is a 2D discipline; for 3D libraries, filling the panel with a fractional multiple is usually the better trade. Display filtering sits on top either way: bilinear softens the final stretch, nearest-neighbour keeps pixel edges hard.
Panel Fit: Do the Division Before You Pick
Divide your panel’s height by the game’s native lines and you get the largest whole multiple that fits. A 1200-line panel divided by 240 lines is exactly 5 — the cleanest fit in handheld gaming. The table below uses the native figures above:
| Content | 1200-line panel | 1600-line panel | 1080p panel |
|---|---|---|---|
| 240-line games | 5x = 1200, exact fit | 6x = 1440 | 4x = 960, borders |
| PSP (272 lines) | 4x = 1088 | 5x = 1360 | 4x = 1088, 8 lines over |
| GameCube (528 lines) | 2x = 1056 | 3x = 1584, near-exact | 2x = 1056 |
| DS screens stacked (384 lines) | 3x = 1152 | 4x = 1536 | 2x = 768 |
PPSSPP’s own documentation walks through the PSP row: 4x renders 1920×1088 against a 1920×1080 screen, and the emulator trims the small difference to fit. Height and width can also disagree — the 3DS top screen at 5x is 2000×1200, so its height fits a 1200-line panel exactly while its width overshoots a 1920-wide panel. The 800p class works the same way: the Steam Deck OLED’s 1280×800 panel fits 240-line games at 3x (720 lines) with borders, and it is sold through Valve rather than Amazon, so it appears here as arithmetic only, with no product slot.
Downsampling: Rendering Above the Panel on Purpose
If the rendered image is larger than the panel, the display step shrinks it — and that shrink is a quality feature, not a waste. Each panel pixel becomes an average of several rendered pixels, smoothing jagged 3D edges much like supersampling anti-aliasing. PPSSPP’s documentation notes you can gain a bit of extra anti-aliasing by rendering above your monitor and letting the emulator downscale. DuckStation offers a Down-Sampling option that renders at your chosen scale and downsamples the finished frame, which also calms the 2D sprites and menus in mostly-3D games. The honest cost: you pay the square-law price for pixels nobody sees individually, so downsampling is a luxury for strong chips.
Why Upscaled 3D Still Shows Soft Textures
Scaling re-renders geometry; it does not redraw artwork. Textures are fixed assets, and a small texture stretched across a wall at 5x still contains only its original information, spread thinner. Texture filtering — bilinear, and anisotropic filtering for surfaces viewed at an angle — smooths how those samples blend, but smoothing is not detail. That is why an upscaled game can have razor-sharp polygon edges and muddy surfaces at once. Only replacement texture packs change the assets themselves, a separate topic with its own guide in this series.
Five Panels, Five Different Right Answers
The handhelds below are ordered by panel class, because the screen is the specification that decides your settings.
Lenovo Legion Go 2
The 1200-line OLED is the panel the maths loves most: 240-line games land on an exact 5x, PSP fits at 4x with room to spare, and the chip can render GameCube at 3x and downsample.
- Display: 8.8-inch OLED, 1920×1200, 144Hz
- Chip: AMD Ryzen Z2 Extreme
- Memory: 32GB LPDDR5X (top configuration)
- Battery: 74Wh
Lenovo Legion Go
The 1600-line panel is the near-exact GameCube screen: 528 lines at 3x gives 1584, filling almost the whole display, and 240-line games sit at 6x with slim borders.
- Display: 8.8-inch IPS, 2560×1600, 144Hz
- Chip: AMD Ryzen Z1 Extreme
- Memory: 16GB LPDDR5
- Storage: 512GB
ASUS ROG Xbox Ally
The 1080p panel asks for one compromise: PSP at 4x overshoots by eight lines, so you accept the emulator’s trim or drop to 3x — while 240-line games take a clean integer 4x with borders.
- Display: 7-inch IPS, 1920×1080, 120Hz
- Chip: AMD Ryzen Z2 A
- Memory: 16GB
- Storage: 512GB
Retroid Pocket 5
The same 1080p arithmetic as above, on a smaller AMOLED panel in a pocketable body — the sensible ceiling here is PS1 and PSP multiples, where its chip is comfortable.
- Display: 5.5-inch AMOLED, 1920×1080, 60Hz
- Chip: Snapdragon 865
- Memory and storage: 8GB, 128GB
- Battery: 5000mAh
Lenovo Legion Go S
Another exact-fit 1200-line panel, this time with variable refresh to keep fractional-scaled 3D smooth when frame pacing is uneven — the pragmatic pick for mixed libraries.
- Display: 8-inch IPS, 1920×1200, 48–120Hz VRR
- Chip: AMD Ryzen Z2 Go
- Memory: 16GB
- Storage: 512GB
How to Choose
Work through four steps. First, find the native line count of the system you play most in the table above. Second, divide your panel’s height by that number and take the whole number at or below the result as your default. Third, adjust by content: keep the strict integer for 2D libraries, but let 3D libraries use a fractional multiple that fills the screen. Fourth, if your chip has headroom left, render one step above the panel and let downsampling smooth the result — and if a game’s menus develop thin lines or seams at high multiples, an artifact PPSSPP’s documentation warns about, drop one step for that title rather than globally.
Who Should Skip
Skip the fine-tuning if you play at native resolution behind CRT shaders, because that look depends on low internal resolutions and this advice points the other way. Skip it if your handheld only just holds full speed at 1x, since every step up multiplies the rendering cost by the square law. And skip it if you use a single emulator whose automatic setting already matches your panel — the arithmetic just confirms what you already have.
FAQ
Is a higher internal resolution always better?
No. Up to your panel’s pixel count it adds real detail. Beyond that it only buys downsampling smoothness, paid for at square-law cost, and some games show HUD or sprite seams at high multiples. The best setting matches your screen and the specific game.
Why does 2x on PS2 look sharper than 3x on PS1?
Because multiples are relative. The PS2 starts at 480 lines, so 2x renders 960 lines. The PS1 starts near 240 lines, so 3x renders only 720. Convert labels to pixels before comparing, and the smaller number wins here.
Should I use integer scaling for 3D games?
It matters far less. Integer scaling protects the uniform pixel blocks of 2D art; 3D geometry is continuous, so fractional multiples render cleanly at any size. Reserve integer scaling for pixel-art libraries and use panel-filling fractions for 3D.
Does upscaling improve a game’s textures?
No. Upscaling re-renders the geometry at higher resolution, but textures are fixed-size artwork that only gets stretched and filtered. Sharper surfaces require replacement texture packs made for that game, a different feature entirely.
Final Verdict
A resolution multiple is a ratio, not a score. Convert it to pixels, compare those pixels with your panel, keep whole numbers for 2D and let 3D fill the screen, and spend spare power on downsampling rather than the biggest label in the menu. Do that, and the same setting produces the same result on every emulator you own.











