Leave anti-aliasing on. If the game offers DLAA, FSR Native AA or XeSS Native AA, those are the native-resolution modes of the vendors’ upscalers; otherwise use the game’s own TAA or SMAA, MSAA where the engine supports it, and FXAA as the light option. Leave NVIDIA’s driver anti-aliasing settings alone unless a game has no anti-aliasing of its own.
At a glance
- Class
- Gaming
Provenance
- Nov 18, 2026Published
TL;DR · Anti-aliasing on or off
- On. Anti-aliasing exists to remove stair-stepped edges. The only advice to turn a method off that I found in the vendor text is NVIDIA's note to switch its driver FXAA off if you see artifacts around text.
- Which kind: DLAA, FSR Native AA or XeSS Native AA if the game has one; otherwise the game's TAA or SMAA, MSAA if the engine offers it, FXAA when you need the cheap option.
- Need frames: step down to the upscaler's Quality mode instead of dropping anti-aliasing altogether.
- NVIDIA driver: leave Antialiasing - Mode on Application-controlled. NVIDIA documents Override for games with no anti-aliasing of their own, and for the HDR case covered below.
- Gamma correction: NVIDIA documents it for OpenGL programs. Leave it alone.
I’m not going to tell you one algorithm wins. The documentation describes each method as fixing a different part of the picture at a different price, and Epic’s engine docs show the renderer limits which methods a project can use. What I can do is tell you what each one is according to the people who built it, which to reach for first, and where the driver-level switches fit. Everything about image quality below is tied to a vendor description or a named publisher’s test. My own bench is a 4K 120 Hz OLED on an RTX 5080, but I ran no image comparison for this page and I’m not going to pretend I did.
What the methods are
MSAA (multisample anti-aliasing). Microsoft’s Direct3D documentation says it reduces geometry aliasing using pixel coverage and depth-stencil tests at multiple sub-sample locations, and in the same breath that it does not reduce surface aliasing. Unity’s documentation agrees: MSAA is better at triangle-edge aliasing than the other techniques but does not fix shader aliasing such as specular or texture aliasing. Epic adds a limit that matters in practice: in Unreal Engine, MSAA is only available on Mobile and Desktop/Console when using the Forward Renderer, and it does not affect aliasing from materials, textures or transparent surfaces.
FXAA (fast approximate anti-aliasing). A post-processing pass. NVIDIA’s white paper calls it a screen-space software approximation that runs as a single pass on a single-sample image, and says it targets aliasing on triangle edges and in shader results. Epic describes FXAA as a spatial-only post-processing technique that is fast to render, but “the final image can lose fidelity when compared to other anti-aliasing techniques.” Unity calls it the least resource-intensive option in its render pipeline. Tom’s Hardware’s 2014 explainer says FXAA and MLAA make a scene look softer than MSAA does. For cost, NVIDIA’s January 2011 paper gives one figure with its conditions: processing a 1920x1200 frame on a GTX 480 takes under 1 ms with FXAA preset 2. That is 2011 hardware.
SMAA (subpixel morphological anti-aliasing). Also a post-process. Its authors describe an image-based technique with local contrast analysis for edge detection and handling for sharp geometric features and diagonal lines. Unity’s manual says it finds patterns in the borders of an image and blends the pixels along them, and that it gives much sharper results than FXAA.
TAA (temporal anti-aliasing). Unity: it uses frames from a color history buffer to smooth edges over several frames, and because it works over time it “often creates ghosting artifacts in extreme situations,” such as an object moving quickly in front of a contrasting surface. Intel’s XeSS developer guide describes the same mechanism and says TAA implementations use heuristics to reject mismatched history, and that those heuristics often fail and produce noticeable ghosting, over-blurring or flickering. That is Intel describing TAA’s weakness in order to sell its alternative, so read it as a description of the mechanism rather than a verdict. Unity also lists a hard rule: you can’t use MSAA with TAA.
The upscaler family: DLSS, FSR, XeSS, and their native-resolution modes. These are temporal methods that also anti-alias. Intel’s guide describes XeSS Super Resolution as a temporal super sampling and anti-aliasing technology that replaces the TAA stage in the renderer. NVIDIA describes DLAA as an anti-aliasing technique that uses the same Super Resolution technology developed for DLSS, constructing the image at native resolution. NVIDIA’s programming guide defines it the same way: DLAA is when input and output render sizes are the same, a scaling ratio of 1.0. AMD’s FSR Upscaling page (the upscaler formerly called FidelityFX Super Resolution 4) lists a Native AA mode at 1.0x per dimension and says it provides image quality superior to native rendering with a modest performance cost. Intel’s guide lists a Native Anti-Aliasing preset at 1.0x, described as anti-aliasing for maximum visual quality.
What each upscaler mode renders at
| Mode | Scale (per dimension) | Source |
|---|---|---|
| DLAA | 1.0 | NVIDIA programming guide |
| DLSS Quality | 1.5 | NVIDIA programming guide |
| DLSS Balanced | 1.724 | NVIDIA programming guide |
| DLSS Performance | 2.0 | NVIDIA programming guide |
| FSR Native AA / Quality / Performance | 1.0 / 1.5 / 2.0 | AMD GPUOpen |
| XeSS Native AA / Quality / Performance (XeSS 1.3 and later) | 1.0 / 1.7 / 2.3 | Intel XeSS-SR guide |
The scale is how much the render resolution is divided by on each axis, so a 1.5 ratio at 3840x2160 renders internally at 2560x1440 (2160 divided by 1.5). Notice that “Quality” is not the same ratio on every vendor’s menu. Intel’s own guide says it raised the scaling for existing presets in XeSS 1.3.
I won’t quote a frame-rate cost for DLAA because NVIDIA’s DLSS page gives no figure for it. AMD’s wording for Native AA is “a modest performance cost.” Epic gives numbers for its own Temporal Super Resolution under stated conditions: it says upscaling from 1080p to 4K gets image quality near 4K while reducing GPU frame time by half, and its own captions for the comparison frames read 57.50 ms at native 4K and 33.37 ms at 1080p upscaled (it does not name the GPU, and those two figures are about a 42 percent cut, not half). Unreal’s TSR is Epic’s own engine feature, not DLSS.
Hardware support, per each vendor: NVIDIA lists DLAA on RTX 20, 30, 40 and 50 series. AMD lists FSR Upscaling 4.1.2 on Radeon RX 9000, 7000 and 6000 series, with analytical fallback paths (FSR 2.3.4 and 3.1.6) on Radeon RX 500 series and above or equivalent GPUs from other vendors. Intel’s repository says XeSS Super Resolution boosts frame rates on all GPUs with Shader Model 6.4 (DP4a) support.
Which to pick, and at what resolution
The documents that bear on resolution are these three, and none of them is a rule:
- Tom’s Hardware’s 2014 explainer says higher resolutions reduce the need for heavy anti-aliasing: aliasing is still present and evident in moving scenes as shimmering, but much less noticeable than at lower resolutions, and the cost of AA also rises with resolution.
- Intel’s XeSS guide gives recommended output resolutions per preset: Native Anti-Aliasing through Balanced at 1080p and above, Performance and Ultra Performance at 1440p and above.
- Epic says its Temporal Super Resolution approaches native 4K quality with input resolutions as low as 1080p.
From those, here is my pick order, and it is a judgment, not a measurement:
- The game has DLAA, FSR Native AA or XeSS Native AA and you have frames to spare: use it. It is the vendor’s anti-aliasing at native resolution with no upscaling.
- You are short of frames: move to that same upscaler’s Quality mode rather than turning anti-aliasing off. At 4K that renders at 1440p internally on DLSS or FSR.
- No upscaler, and the game has TAA or SMAA: use whichever looks better to you in motion. TAA’s documented weakness is ghosting; SMAA is described as sharper than FXAA.
- The game offers MSAA: Microsoft says it reduces geometry aliasing, and Tom’s Hardware says it carries a very high cost in video memory and fill rate. Microsoft and Unity both say it does not fix surface or shader aliasing.
- You are at the edge of your frame budget: FXAA, and accept the softness Epic and Tom’s Hardware describe.
If you are choosing between 4x and 8x MSAA, see the FAQ: the vendors say more samples cost more and look better, and none of them quantify the gap.
Frame generation is a separate switch from anti-aliasing, and so is VSync; I cover each on its own page. The DX12 vs DX11 guide matters here only because a game’s render path decides which anti-aliasing options it ships with, and I can’t tell you that per title from vendor documentation. To see how much pixel density your own screen has, the PPI calculator does the arithmetic.
NVIDIA’s driver-level anti-aliasing settings
NVIDIA’s May 26, 2026 driver announcement says the classic Control Panel is retiring for Game Ready and Studio drivers, and says that in the NVIDIA app, Graphics > Program Settings replaces the Control Panel’s 3D Settings > Manage 3D Settings screen. On the bench machine the NVIDIA app is 11.0.9.585, and its string table carries these names: Antialiasing - Mode, Antialiasing - Setting, Antialiasing - FXAA, Antialiasing - Gamma Correction, Antialiasing - Transparency and Multi-Frame Sampled AA (MFAA). All but MFAA also appear in the classic help page I read. I did not open the app to see which show up for which game, so check Program Settings for the game you care about.
Antialiasing - Mode. The app’s values read Application-controlled, Enhance the application setting, Override any application setting and Off. NVIDIA’s help says Application-controlled is the preferred setting for applications with built-in controls. Enhance requires you to set the game’s own anti-aliasing to some level, such as 2x, and then applies NVIDIA’s chosen level regardless. Override is for applications with no anti-aliasing controls of their own, or ones whose built-in anti-aliasing doesn’t work with HDR rendering. NVIDIA’s tips page spells out the HDR case: pick Override, then enable HDR in the game and turn the in-game anti-aliasing off.
Does forcing it work? NVIDIA’s reference doesn’t list which graphics APIs honor Override or Enhance. The one named test I found is Tom’s Hardware’s April 2011 piece, on GeForce and Radeon cards of that generation: across nine games and 14 game-and-render-path scenarios, GeForce Override worked in two of the 14, and Enhance worked in 11 of 14 for adding coverage-sampling modes. In DirectX 10 and 11 titles, it reported that Enhance only took effect if the multisample count matched the one set in the game. That is 2011 drivers and 2011 games. I have not repeated it. Treat it as a reason to test a forced setting in the game you care about, not as a statement about current drivers.
Antialiasing - FXAA. NVIDIA’s app text describes it as a shader-based post-processing technique that can be applied to any program, including those without other forms of hardware-based anti-aliasing. The same text warns that enabling it globally “may affect all programs rendered on the GPU, including video players and Windows desktop,” and suggests turning it off if you notice artifacts or dithering around edges of objects, particularly text. That is the reason I’d set it per game, never globally.
Antialiasing - Gamma correction. The question behind the “on or off” searches. NVIDIA’s classic help says it “allows you to enable or disable gamma correction antialiasing to improve the color and quality of 3D images in OpenGL programs.” The NVIDIA app’s text says “Select On to improve the quality and color of 3D images” and doesn’t mention OpenGL. Neither says what it does in a DirectX or Vulkan game, and neither says what turning it off costs you. I’d leave it at whatever it is and not chase it.
Antialiasing - Transparency. NVIDIA: it minimizes visible aliasing on the edges of images with transparent textures; multisampling provides superior performance and supersampling superior quality. AMD’s equivalent, in the Adrenalin guide I checked (updated March 3, 2025, written against 23.9.1), is Adaptive Anti-Aliasing, which it says covers transparent textures where plain MSAA cannot, such as fences.
DSR. The app describes Dynamic Super Resolution as rendering at a high resolution and downscaling with filtering, usable with other anti-aliasing settings, aimed at games without in-game anti-aliasing settings or where in-game anti-aliasing is insufficient. Its Smoothness slider text: lower is sharper but more aliased, higher is smoother but blurrier.
On Radeon, the Adrenalin guide lists the equivalent three modes (Use, Enhance, Override Application Settings), methods Multisampling, Adaptive and Sparse Grid Supersampling, and a Morphological option. AMD says Morphological Anti-Aliasing can add a subtle blur in some situations and works only with Enhance or Override and in exclusive full screen mode.
Edge cases
- HDR plus anti-aliasing: only the case NVIDIA documents above. Anything else about HDR and a given game is outside what I read.
- A game with an upscaler but no DLAA option: NVIDIA’s March 2025 app update post says the “DLSS Override - Super Resolution” setting can enable DLAA in games lacking native support when Super Resolution is on in the game. On my bench’s app build the setting is named “DLSS Override - Super Resolution Mode” and its Mode list includes DLAA. The app’s own text says the setting is supported for select DLSS games and points you to NVIDIA Overlay > Statistics > DLSS to check override status, so check that rather than assuming.
- Blur you attribute to anti-aliasing: a softer image can also come from the display or from motion blur. The motion blur guide covers that switch.
Frequently asked questions
What does anti-aliasing mean?
What does antialiasing FXAA do?
Is FXAA or MSAA 4x better?
What should my anti-aliasing be on?
Is anti-aliasing 4 or 8 better?
Is anti-aliasing gamma correction better on or off?
Sources and corrections
- Last updated
- Methodology
- See our methodology for research and review standards. It draws on 17 cited sources, listed below, each checked against the original page on 2026-11-17. First-hand reads on the bench machine, all read-only, on 2026-11-17. Windows 11 Home build 26200 (the registry’s ProductName value still reads ‘Windows 10 Home’; DisplayVersion 25H2, UBR 9974, from Get-ItemProperty on HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion). nvidia-smi –query-gpu=name,driver_version returned ‘NVIDIA GeForce RTX 5080, 621.24’. reg query HKLM\SOFTWARE\NVIDIA Corporation\Global\NVApp returned Version 11.0.9.585. Get-AppxPackage NVIDIAControlPanel returned NVIDIACorp.NVIDIAControlPanel 8.1.969.0, so the classic Control Panel is also installed here; I did not open it. I did not open the NVIDIA app either. What I did read is the app’s own English string table, C:\Program Files\NVIDIA Corporation\NVIDIA App\www\assets\i18n\en_US.json, which holds entries named Antialiasing - Mode, Antialiasing - Setting, Antialiasing - FXAA, Antialiasing - Gamma Correction, Antialiasing - Transparency, Multi-Frame Sampled AA (MFAA), DSR - Factors and DSR Smoothness, and a DLSS Override - Super Resolution Mode setting whose Mode list includes DLAA. Those strings tell me the names and NVIDIA’s wording; they do not tell me which of them appear for a given game or in what order on screen. I ran no benchmark and compared no screenshots, so every statement about image quality or cost on this page belongs to a vendor or a publisher named where it appears. Older sources are dated in the text: NVIDIA’s FXAA paper (version 1.0, January 2011) and Tom’s Hardware’s driver test (April 2011) describe GeForce hardware and games of those years.
- Sources
- NVIDIA Control Panel Help: Manage 3D Settings (reference), Antialiasing entries accessed 2026-11-17
- NVIDIA Control Panel Help: Tips for Setting Antialiasing accessed 2026-11-17
- NVIDIA: 007 First Light GeForce Game Ready Driver (Control Panel retirement; Program Settings replaces Manage 3D Settings) accessed 2026-11-17
- NVIDIA: DLSS technology page (Super Resolution, DLAA, supported GPUs) accessed 2026-11-17
- NVIDIA DLSS Super Resolution Programming Guide 310.6.0 (execution modes, scaling ratios, DLAA) accessed 2026-11-17
- NVIDIA: NVIDIA App Update Adds Project G-Assist, DLSS Super Resolution Custom Scaling & New Control Panel Features (March 25, 2025) accessed 2026-11-17
- NVIDIA: FXAA white paper, Timothy Lottes (version 1.0, January 2011) accessed 2026-11-17
- AMD GPUOpen: AMD FSR Upscaling (quality modes, supported GPUs) accessed 2026-11-17
- AMD Support DH3-012: Customize Graphics Settings with AMD Software: Adrenalin Edition accessed 2026-11-17
- Intel XeSS SDK repository README accessed 2026-11-17
- Intel XeSS-SR Developer Guide (presets, scaling, recommended resolution, TAA) accessed 2026-11-17
- Microsoft Learn: Rasterization Rules (multisample anti-aliasing) accessed 2026-11-17
- Epic Games: Anti-Aliasing and Upscaling in Unreal Engine accessed 2026-11-17
- Unity: Add anti-aliasing in the Universal Render Pipeline (Unity 6.0 manual) accessed 2026-11-17
- SMAA: Enhanced Subpixel Morphological Antialiasing (Jimenez et al., Eurographics 2012) accessed 2026-11-17
- Tom's Hardware: The Myths Of Graphics Card Performance: Debunked, Part 2 (November 11, 2014) accessed 2026-11-17
- Tom's Hardware: Anti-Aliasing Analysis, Part 1: Settings And Surprises (April 13, 2011) accessed 2026-11-17
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.