iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For true pixel art, start with DLSS off. Render at the game’s native internal resolution and enlarge the image with nearest-neighbor or integer scaling so each source pixel remains a clean block. DLSS is a temporal reconstruction system: it creates a higher-resolution frame from a lower-resolution render, using information from multiple frames. That process can soften, blend, or add halos around deliberately discrete sprite pixels.
For a low-resolution 3D game, begin with DLSS Quality, then move to Balanced only when the GPU is still limiting your frame rate. Use Performance or Ultra Performance as increasingly aggressive compromises, not as automatic “best” settings. If the game already renders at your monitor’s native resolution and you only need anti-aliasing, choose DLAA instead of Super Resolution.
Choose a starting setting by game type
The right choice depends first on how the image is drawn, not on the game’s genre. A 2D game that intentionally places colored squares on a grid has different needs from a 3D game whose low-resolution look comes from a small internal render scale.
| Game or rendering situation | Starting setting | Reason | Next check |
|---|---|---|---|
| Deliberate 2D pixel art or emulator output | DLSS Off; native internal resolution; nearest-neighbor or integer scaling | Maintains hard pixel boundaries and exact palette transitions | Look for an integer-scale option and turn off unnecessary sharpening |
| Low-resolution 3D game with DLSS support | DLSS Quality | Preserves the most source detail among the usual Super Resolution modes | Inspect thin geometry, foliage, text, and moving edges |
| GPU-limited low-resolution 3D game | Balanced, after testing Quality | Trades some input resolution for additional frame-rate headroom | Stop if shimmer, ghosting, or blur becomes distracting |
| Severe GPU constraint at a high output resolution | Performance, then Ultra Performance only if necessary | Provides the largest reconstruction gains when other changes are insufficient | Compare against a lower native output or a spatial/integer scaler |
| Native-resolution rendering already meets the target | DLAA | Applies DLSS anti-aliasing without reducing internal resolution | Disable it if the game’s intentionally blocky style becomes too smooth |
These are starting points, not universal measurements. Image quality depends on the title’s motion vectors, anti-aliasing integration, post-processing, output resolution, GPU, and DLSS version. No broadly applicable performance or quality statistic establishes one mode as best for every pixel-art or low-resolution game.
#1 Best Overall
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
What DLSS is doing to the image
NVIDIA describes DLSS Super Resolution as reconstructing a higher-resolution frame from a lower-resolution render. The game supplies the current low-resolution image and motion information; the reconstruction uses data from prior frames to estimate detail that was not fully present in the current input. The result can contain more apparent detail than a simple resize, but it is not the same as rendering every final pixel natively.
NVIDIA defines DLAA separately: it uses DLSS technology for anti-aliasing at native resolution. DLAA therefore does not provide the internal-resolution reduction that Super Resolution modes use to increase performance. It is useful when your GPU already reaches the desired frame rate and the game’s edges need smoothing.
DLSS presets are tuned for different scaling ratios and content types. A preset that looks excellent in one title may be less stable in another because developers integrate motion vectors, depth data, anti-aliasing, and sharpening differently. Treat the in-game mode label as a controlled starting point, then judge the actual output at your display’s resolution.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesWhy pixel art is unusually sensitive
Pixel art relies on exact placement and color of individual pixels. A one-pixel outline, a two-color checkerboard, or a deliberately limited palette is part of the design rather than noise waiting to be reconstructed. Temporal reconstruction can interpret those intentional shapes as subpixel detail or movement.
- Edge blending: a hard diagonal may acquire intermediate colors, making a sprite look antialiased when it was designed to be stepped.
- Ringing and halos: sharpening or reconstruction around a high-contrast boundary can produce a light or dark fringe.
- Temporal shimmer: a sprite, tile edge, or scrolling background can change subtly as the camera moves and the history buffer is updated.
- Ghosting: a moving character or UI element may leave a faint trail when the motion data does not describe the object accurately.
- Text softening: small bitmap fonts and HUD icons can lose their intended grid alignment, especially at 1080p or below.
These effects explain the practical preference for native rendering and integer scaling in 2D pixel-art games. NVIDIA’s technical definitions describe how reconstruction and scaling work; they do not establish a universal rule that DLSS is unacceptable for every pixel-art title. Some games combine 3D scenes with pixel-styled overlays, and their results must be judged separately.
Separate 2D pixel art from low-resolution 3D
Pure 2D sprites, tiles, and emulator output
Use the game or emulator’s native internal resolution, then scale the complete image by an integer factor when possible. Integer scaling enlarges each source pixel to a square group of identical display pixels. Nearest-neighbor scaling performs the same kind of discrete enlargement without introducing blended colors.
If your monitor cannot fill the screen at an integer multiple, you have to choose between black borders, a non-integer resize, or a different output resolution. Black borders preserve geometry; a non-integer resize fills more of the panel but may make pixels uneven. DLSS is generally the wrong tool for this decision because it reconstructs temporal detail rather than preserving a fixed pixel grid.
3D scenes with a deliberately small internal render
A low-resolution 3D game can benefit from DLSS because geometry, lighting, and motion are continuous rather than fixed sprite pixels. Quality is the least aggressive common Super Resolution choice and therefore the sensible first test. If the GPU remains saturated, Balanced can recover headroom while retaining more detail than Performance.
Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
Examine the parts that reveal reconstruction errors quickly: thin fences, wires, foliage, specular highlights, distant geometry, subtitles, and objects crossing the camera. A mode that looks sharp in a still screenshot may break up during movement, so test both a stationary view and a repeatable camera pan.
Understand each DLSS mode before changing it
| Mode | What changes | When to try it | Typical warning sign |
|---|---|---|---|
| Off | The game uses its native internal render and its own scaling or anti-aliasing path | Pixel art, emulator output, or when native performance is already sufficient | Aliasing or a frame-rate shortfall may remain, depending on the game |
| Quality | Uses a relatively high internal resolution before reconstruction | First choice for low-resolution 3D and for image quality at a stable frame rate | Fine detail may still flicker if the title supplies poor motion data |
| Balanced | Reduces the internal resolution further to gain performance | When Quality cannot meet the frame-rate target | Small text, foliage, and thin geometry become less stable |
| Performance | Uses a substantially lower-resolution input | When the GPU is the clear bottleneck and lower image fidelity is acceptable | Softness, ghosting, and reconstruction artifacts become easier to see |
| Ultra Performance | Uses the most aggressive common Super Resolution reduction | Last resort for severe GPU limits or unusually high output resolutions | Blur, shimmering, and lost fine detail can dominate the image |
| DLAA | Runs DLSS anti-aliasing at native resolution rather than upscaling | Native rendering already reaches the target frame rate | Pixel-styled edges may become too smooth |
The labels describe relative trade-offs, not a fixed visual result. The internal resolutions and behavior can vary with the game, DLSS implementation, output resolution, and version.
Prepare a fair comparison
Changing several visual options at once makes it impossible to identify the cause of a problem. Establish a repeatable baseline before selecting a mode.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Set the display mode and output resolution first. Use the resolution at which you actually play. A setting that appears acceptable at 4K can look noticeably worse when the final image is only 1080p or lower.
- Record a repeatable scene. Choose an area containing text, foliage, thin geometry, and a moving camera. A saved game, built-in benchmark, or identical camera route is more useful than a random screenshot.
- Disable film grain, chromatic aberration, and depth of field temporarily. These effects can hide whether softness or color fringing comes from the scaler. Restore them later if you want the intended presentation.
- Keep anti-aliasing consistent. If the game offers a separate anti-aliasing control, note its value. Switching both DLSS and anti-aliasing at once changes two image-processing stages.
- Check GPU utilization and frame pacing. DLSS helps most when the GPU, rather than the CPU, is limiting performance. A lower mode cannot solve a CPU-bound frame rate.
- Capture still and moving views. Inspect a paused frame for sharpness, then pan slowly and quickly to reveal ghosting, shimmer, and history instability.
How to tune DLSS step by step
For a pixel-art or 2D game
- Open the game’s video, graphics, or display settings and turn DLSS Super Resolution off.
- Set the internal or base resolution to the game’s native resolution if that option is exposed.
- Choose Nearest Neighbor, Integer Scale, or the equivalent pixel-perfect option. Names vary by game and emulator.
- Disable extra sharpening while evaluating the result. Sharpening cannot restore a lost pixel grid and may create halos.
- Check HUD text, diagonal sprite outlines, and a horizontally scrolling background. If their pixels remain evenly sized and colors stay discrete, the scaling path is behaving as intended.
- If the game lacks pixel-perfect scaling, compare a lower output resolution with the display’s own scaling against a software nearest-neighbor option. Choose the path that preserves even pixel blocks, accepting borders when necessary.
For a low-resolution 3D game
- Select DLSS Quality and restart the scene or benchmark so shaders and temporal history settle.
- Move the camera through foliage, thin structures, reflective surfaces, and areas with readable text.
- If the frame rate meets your target and the image is stable, keep Quality. There is no benefit in moving to a lower mode merely because it exists.
- If the GPU is still the limiter, test Balanced using the same camera route. Compare frame pacing as well as the average frame rate.
- Try Performance only when Balanced cannot meet the target or when a higher output resolution leaves insufficient GPU headroom.
- Reserve Ultra Performance for cases where the alternatives are an unacceptable frame rate or a lower native output. Inspect the result at normal viewing distance, not only while zoomed into a screenshot.
When native rendering is fast enough
- Turn Super Resolution off and render at the display’s native resolution.
- Enable DLAA if the game exposes it and you want DLSS anti-aliasing.
- Compare DLAA with the game’s ordinary anti-aliasing on moving edges and on any pixel-styled interface.
- Keep the option that matches the intended art direction; native-resolution anti-aliasing can be technically clean while still being aesthetically wrong for deliberately blocky graphics.
Fix a soft or unstable image
First remove masking effects
Film grain, chromatic aberration, and depth of field alter edge contrast and color, so disable them during diagnosis. If the softness disappears, re-enable one effect at a time to identify which one changes the perception. This does not prove that DLSS was at fault; it separates the reconstruction stage from post-processing.
Use sharpening sparingly
Set the game’s sharpening control to zero or a very low value, then add only enough to restore edge contrast. Running both game-level sharpening and a driver-level sharpening filter can produce bright outlines, dark fringes, and noisy flat-color regions. Sharpening cannot recreate a missing source pixel or guarantee integer alignment.
Test around the preset boundary
If the game exposes a render-scale slider, make small changes around the Quality and Balanced positions. NVIDIA notes that presets are tuned for particular scaling ratios and content types, so an adjacent custom scale may look better in one title than the named preset. Compare both still frames and camera motion; temporal errors often appear only after movement.
Check motion-related artifacts
- Ghosts behind a moving character usually indicate a history or motion-vector problem rather than insufficient sharpening.
- Shimmer on thin geometry may improve at a higher internal-resolution mode or with the game’s anti-aliasing integration changed.
- Flashing UI or subtitles can result from an interface being composited through the reconstruction path. Look for a separate UI-resolution or HUD-scale option.
- Ringing around high-contrast pixels is a reason to reduce sharpening and compare DLSS with native or integer scaling.
Integer scaling and NVIDIA Image Scaling
For 2D output, nearest-neighbor or integer scaling is the most direct way to preserve the source grid. If the game or emulator does not provide it, your GPU driver or monitor may offer lower-resolution scaling controls.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →NVIDIA Image Scaling is a spatial upscaling option in the NVIDIA Control Panel. Its controls can upscale a lower-than-native output, add selectable resolutions below native, and expose a sharpening control. Unlike DLSS Super Resolution, it does not use the same temporal reconstruction process. It may therefore avoid some temporal artifacts, but it cannot recover detail that was never rendered and may look less refined in a 3D scene.
Rank #3
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
Use the simplest path that satisfies the art style: integer scaling for sprites and tiles; a spatial scaler when you need a lower fixed render; DLSS when a 3D title benefits from temporal reconstruction and the game’s implementation is stable.
Match the setting to output resolution
Output resolution changes how visible every compromise is. At a high output resolution, Performance may retain enough apparent detail for a comfortable image because the final frame has many pixels. At 1080p or below, the same reconstruction errors occupy a larger portion of each object and small text has less room to survive.
Evaluate the final displayed image, not only the internal-resolution label. A mode that is acceptable on a 4K monitor viewed from a normal distance may look soft on a 1080p panel. Conversely, lowering the monitor’s output resolution can be a better emergency measure than using Ultra Performance if the latter makes the scene unstable.
Free tools Windows power users keep installed
One-click scans. No signup required.
GPU, game, and version requirements
DLSS is an NVIDIA RTX feature implemented by supported games. The game must expose the relevant mode, and the installed driver and DLSS implementation must be compatible with that title. An RTX-capable GPU alone does not add DLSS to a game that lacks integration.
Because developers can update the game’s DLSS library, motion-vector handling, presets, and post-processing, record the game version and DLSS version when comparing results. A change after an update may come from the implementation rather than from your selected Quality, Balanced, or Performance label.
Decision framework when two modes look close
When Quality and Balanced appear similar in a still image, use four tests in this order:
- Pixel-edge fidelity: for pixel art, confirm that the source grid remains intact; for 3D, inspect thin geometry and text.
- Temporal stability: pan the camera and watch for shimmer, trails, and changing detail.
- Frame-rate headroom: check whether the GPU has enough margin for demanding scenes, not only the current location.
- Pipeline compatibility: verify that UI, anti-aliasing, transparency, and post-processing still behave correctly.
If both modes pass the visual tests, choose the higher internal-resolution mode for additional image-quality margin. If neither passes, compare native rendering, a lower output resolution, or a spatial/integer scaler instead of forcing a more aggressive DLSS mode.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Common mistakes to avoid
- Using DLSS automatically for every low-resolution game: “low resolution” can describe a pixel-art source that needs grid preservation or a 3D render that can benefit from reconstruction.
- Judging from a paused screenshot alone: temporal artifacts are often visible only while the camera or object moves.
- Adding maximum sharpening to compensate for blur: this commonly creates halos without restoring detail.
- Changing output resolution, anti-aliasing, and DLSS simultaneously: isolate one variable at a time.
- Ignoring CPU limits: a lower internal resolution cannot materially improve a frame rate limited by the processor, simulation, or draw-call workload.
- Assuming preset names are identical across games: implementation, scaling ratio, and content tuning differ by title and version.
A practical final checklist
- Is the game true 2D pixel art, emulator output, or low-resolution 3D?
- For 2D, is DLSS off and is nearest-neighbor or integer scaling enabled?
- For 3D, did you test Quality before Balanced?
- Are Performance and Ultra Performance being used only for a demonstrated GPU constraint?
- Did you compare a moving camera as well as a still image?
- Are film grain, chromatic aberration, depth of field, and sharpening controlled during diagnosis?
- Is the final output resolution the one at which you actually play?
- Does the chosen mode preserve text, thin geometry, UI elements, and the game’s intended art direction?
The best setting is the one that meets the frame-rate target without changing the visual language of the game. For discrete pixel art, that usually means native rendering with integer or nearest-neighbor scaling. For low-resolution 3D, it usually means starting at Quality and moving down only when measured GPU limits justify the image-quality trade.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
