Legion Go resolution scaling is a trade-off among sharpness, frame time, battery draw, and display presentation. The original Legion Go 8APU1 uses an 8.8-inch 2560 x 1600 (16:10), up to 144 Hz panel. You can render at a lower game resolution to reduce pixel workload while preserving a high desktop resolution, but Windows display scaling, GPU scaling, and in-game upscalers are different controls. The practical test is to change one scaling layer at a time while watching both image clarity and frame-time stability. Otherwise, overlapping scaling controls can obscure which setting helped.
Separate display scaling from in-game render resolution
Windows Display scale at 125%, 150%, or 200% enlarges interface elements; it does not make a game render fewer pixels when the game uses its own render target. A game’s render resolution controls the workload on the integrated GPU. GPU scaling determines how that rendered image is enlarged to the physical panel. Temporal upscalers such as FSR produce a reconstructed higher-resolution image from a lower internal render resolution; whether a specific game supports one must be confirmed inside that game.
For the 8APU1 panel, 2560 x 1600 has 4,096,000 pixels, 1920 x 1200 has 2,304,000, and 1280 x 800 has 1,024,000. Relative to the panel’s native pixel count, 800p is one quarter as many rendered pixels. That reduction does not imply four times the frame rate; CPU load, memory bandwidth, shaders and game engine limits still matter.
Three practical starting points
| Game workload | Game render setting | Display or scaling choice | Trade-off |
|---|---|---|---|
| Light 2D or older game | 2560 x 1600 | Native | Finest text and HUD detail; greatest render workload |
| Typical demanding 3D | 1920 x 1200 | Game upscaler or GPU scaling | Balanced compromise; noninteger interpolation can soften fine lines |
| Heavy 3D or battery-focused | 1280 x 800 | 2x integer scaling if available | Lower GPU workload; sharper pixel steps but less source detail |
Match 16:10 inside the game so elements are not stretched from 16:9. If 1920 x 1080 is the only available option, expect letterboxing or cropping depending on aspect and scaling choices; do not force full-panel stretch without checking geometry.
Configure AMD integer scaling carefully
AMD’s documentation explains integer scaling as replication of source pixels at whole-number multiples. On compatible Radeon software/drivers, open AMD Software > Gaming > Display, enable GPU Scaling, and select Integer Scaling where available. AMD notes that menu names and option availability differ among driver packages. The original Legion Go received AMD graphics-driver updates supporting integer scaling, but a particular installed Lenovo driver can expose a different interface. Do not use third-party registry patches solely because a screenshot from 2023 shows a missing toggle.
Set an appropriate 1280 x 800 game resolution and test a high-contrast UI or pixel-art title. An exact 2x mapping should preserve hard edges, but it is not necessarily attractive for photorealistic games. If the image is centered with borders or scaling is absent, verify the display and game resolutions separately rather than assuming the toggle took effect.
Refresh rate, frame limit and smoothness
The panel can run at 60 or 144 Hz, but a 144 Hz display setting does not create 144 rendered frames per second. A measured frame time of 16.7 ms corresponds to about 60 FPS; 33.3 ms corresponds to about 30 FPS. For portable gaming, a stable capped frame rate and consistent frame times are usually more useful than a high peak with irregular spikes. Test the same gameplay route for several minutes before comparing profiles.
Reduce shadow quality and expensive postprocessing first when GPU bound. If the game is CPU bound, lowering from 1200p to 800p can fail to improve its low-percentile frame rate. Measure GPU utilization and frame time rather than automatically blaming the screen.
Fix black screens or the wrong orientation after switching
Back out of an unsupported custom mode with Windows’ built-in display revert prompt. The original Legion Go uses a portrait-native panel, so avoid creating unsupported timings in GPU control software as a first solution. If an external monitor rotates after changing refresh/resolution in Legion Space, use Lenovo’s specific 8APU1 external-monitor support guidance, which deals with that clone-mode symptom.
Avoid stretching a non-native aspect ratio by accident
AMD distinguishes three GPU-scaling choices: Preserve aspect ratio, Center and Full panel. Preserve aspect ratio maintains the image proportions and may leave black bars; Center leaves the image at its original size; Full panel can stretch a non-native aspect ratio to fill the display. Those options are not equivalent to integer scaling, which needs compatible resolution multiples and software support. For a 16:10 Legion Go screen, compare a 16:10 game resolution first and keep Preserve aspect ratio when a 16:9 title would otherwise distort. Do not promise that changing a Windows desktop resolution automatically changes a game running in borderless mode.
Run one resolution experiment with a measurable outcome
For the Legion Go’s 2560 × 1600 panel, 1280 × 800 is a clean 2:1 linear step in each direction, so its source image contains one quarter as many pixels. A game may render at the smaller size while Windows still outputs the panel’s native resolution. Record both values separately, then capture frame times and a screenshot of detailed text at the same camera position. Do not claim that a 2× ratio guarantees driver-level integer scaling in every game or display configuration.
Compare three cases under identical frame caps: native render and output, lower in-game render at native output, and an explicitly selected display/driver scaling mode. If shimmering changes but frame times barely move, the bottleneck may not be GPU pixel shading; if the panel becomes stretched, restore aspect-ratio preservation before chasing more FPS.
The best default
Use native Windows desktop resolution for readable menus, choose game-specific rendering at 1920 x 1200 for a first compromise, and try 1280 x 800 plus integer scaling when performance is otherwise insufficient. Keep a small table of average FPS and worst frame-time spikes per game; only keep a change when it helps both visual clarity and actual playability.
