Quick answer

Pick DX12 when your processor is the limit and the game’s DX12 path is well built — typically 10-20% more frames, because render work spreads across cores. Pick DX11 when a DX12 implementation is poor: frame pacing is steadier and hitching is rarer, which often suits older or thermally limited machines better.

Contents

By LK Wood IV · 2026-06-28 · ~9 min read · St. Louis County, MO

TL;DR · DX12 vs DX11

  • DX12 wins when your CPU is the limit on a modern multi-core PC and the game's DX12 path is well made — typically 10-20% more FPS because it spreads render work across cores.
  • DX11 can win when DX12 is poorly implemented -- steadier frame pacing, fewer hitches, better on older or thermally limited machines.
  • DX12's weakness is shader-compilation stutter when a studio doesn't pre-compile shaders properly.
  • Ray tracing requires DX12. If you want it, you're on DX12.
  • The rule: try both, keep whichever gives better 1% lows -- not the higher average FPS counter.

“DX12 vs DX11, which gives more FPS?” has a frustrating answer: it depends on what is bottlenecking your frame rate, and on how well the studio built the game’s DX12 mode. The good news is that once you understand the one real difference between them, you can predict which will help – and test it yourself in two minutes. This guide gives you both.

The one real difference: how they use your CPU

Everything else follows from this. DirectX is the layer that turns “draw this scene” into instructions for your GPU, and the two versions hand that work to your CPU very differently.

  • DX11 routes most of its render commands through a single main CPU thread. If that one thread maxes out, your frame rate sags – even if the rest of your CPU cores are sitting nearly idle. The driver does a lot of the heavy lifting for you, which keeps things simple and stable, but it is a one-lane road.
  • DX12 spreads those render commands across multiple CPU cores at once. On a modern six-core-or-more processor, that removes the single-thread choke point, which is exactly why it helps when your CPU is the limit. The trade-off: it moves responsibility from the driver to the game, so a lazy or rushed DX12 implementation can perform worse than DX11.
One lane vs many: how each uses your CPU
Relative render load per CPU core (illustrative)
DX11: one core does the workmaxed6 CPU cores — 5 sit nearly idleDX12: work spread across cores6 CPU cores — all share the loadWhen the single DX11 thread maxes out, FPS sags with cores to spare. DX12 removes that choke point.

So which is faster?

The rule, in one line: DX12 has the upside when your CPU is the bottleneck and the game’s DX12 path is well built; otherwise the two are close, and a bad DX12 port can lose to DX11.

  • CPU-bound + modern multi-core CPU + good DX12 port -> DX12 typically gives 10-20% more FPS. This is the scenario DX12 was built for.
  • GPU-bound (you are at high resolution/settings and the graphics card is the limit) -> the API barely matters; both feed the same GPU. Pick on stability.
  • Poorly optimized DX12 mode -> DX11 can be faster and smoother. A messy DX12 implementation can create the very CPU bottleneck DX12 is supposed to remove.

That last point is why you cannot just declare “DX12 is newer, so use DX12.” Newer is only better when the studio did the work. And since the whole question turns on whether your CPU is the limiter, it helps to know that first: test it in the game itself, and use the CPU and GPU benchmark lookup to see where each part sits in its own ranking.

DX12’s real weakness: shader-compilation stutter

If you have heard people complain about “DX12 stutter,” this is it. Because DX12 gives developers direct control of the graphics pipeline, the game is responsible for compiling shaders ahead of time. When a studio does not pre-compile them well, shaders get compiled on the fly during gameplay – and each one is a brief hitch. DX11’s driver handled more of this automatically behind the scenes, which is why some DX11 games feel smoother even when the average FPS is the same.

This is the single biggest reason to actually test both rather than trust the average frame rate: DX12 can show a higher average FPS while feeling worse, because the stutters live in the 1% lows, not the average.

When to use which

SituationPick
Modern 6+ core CPU, CPU-limited, good DX12 portDX12
You want ray tracing / mesh shadersDX12 (required)
The game’s DX12 mode stutters or crashesDX11
Older CPU, or a thermally limited laptopDX11 (often steadier)
GPU-bound at high resolutionEither – pick the steadier one

How to test it yourself (two minutes)

Do not trust a forum verdict for your hardware and your game. Test it:

  1. In the game’s graphics/display settings, find the Graphics API / Renderer / DirectX version dropdown (some games use a -dx11 / -dx12 launch option instead). Switching usually needs a game restart.
  2. Pick a demanding, repeatable scene – a busy area, not an empty menu.
  3. Turn on a frame-time overlay (your GPU software’s overlay, or a tool that shows 1% lows and frame-time, not just average FPS).
  4. Run the same scene on each API and compare the 1% lows and frame-time consistency. Keep whichever is steadier, even if its average FPS is a touch lower. Smooth beats a higher number that hitches.

A note on the CPU that drives this

Because DX12’s whole advantage is spreading work across cores, the API conversation is really a CPU conversation. A strong modern gaming CPU – lots of fast cores and large cache – is what lets DX12 pull ahead, and it is also what carries you in the CPU-bound games where the API matters most. That is a big part of why the $2,500 4K build is built around a Ryzen 7 7800X3D, and why the GPU reviews pair cards with CPUs that can keep them fed. If a specific game stutters under DX12, that is also worth checking against the anti-cheat and launch fixes before blaming the API – sometimes the “DX12 problem” is something else entirely.

DX11 or DX12 in New World, The Division 2 and Warframe

Some games ship both renderers. Three are covered here, using only what each publisher’s official page says as read on October 10, 2026. Patches can change any of it, so check the game’s current settings too.

New World lists DirectX 11 and 12 for both its minimum and recommended PC specs. Its Season of the Divide release notes, dated May 12, 2025, made DX12 the default PC renderer. The DX11 renderer became the Legacy option, available from Steam’s Play menu. Adding -dx11 to the launch commands also selects it. The same notes say DLSS and DLSS Frame Generation are only available on DX12.

Ubisoft’s system requirements for The Division 2 list DirectX 11 or DirectX 12 for the minimum spec (1080p at 30 frames per second). The recommended spec (1080p at 60) lists DirectX 12. So do the 1440p and 4K configurations at 60 frames per second. A Ubisoft weekly update from March 6, 2020, written after the Warlords of New York launch, reported some PC crashes that “may be connected to DX12”. Players were told to update their drivers and try swapping to DX11 in the meantime.

Warframe’s support article on crashes says you can change the graphics API in the launcher settings menu. It says the game supports DirectX 11 or DirectX 12. DirectX 12 is labeled Beta. The article does not say which one runs faster.

A publisher’s default or requirement is not a benchmark for your PC. Run the two-minute test above. Keep the API with the steadier 1% lows.

The bottom line

DX12 is not automatically better than DX11 – it is better at one job: getting more frames out of a modern multi-core CPU when that CPU is the limit and the game was built properly. DX11 is the steadier, simpler path that still wins in messy DX12 ports and on older hardware. Ray tracing forces DX12. For everything else, switch between them in the settings, watch your 1% lows, and keep the one that feels smooth. The right API is the one your specific game and PC actually run best – and now you can prove which that is.

Sources

Frequently asked questions

Is DX12 or DX11 better for FPS?
It depends on what is limiting your frame rate. When your CPU is the bottleneck on a modern multi-core processor and the game’s DX12 path is well made, DX12 usually wins by 10-20% because it spreads render work across cores instead of one. When you are GPU-bound, the two are close. And when a game’s DX12 mode is poorly optimized, DX11 can actually be faster and smoother. There is no universal winner – it is per game.
Why does DX12 stutter more than DX11?
Shader compilation. DX12 hands developers more direct control of the graphics pipeline, which means the game (not the driver) is responsible for compiling shaders ahead of time. When a studio does not pre-compile them well, shaders compile during gameplay and you get hitches – the classic ‘DX12 stutter.’ DX11’s driver handled more of this automatically, which is why some DX11 games feel smoother even at a similar average FPS.
Should I use DX11 or DX12?
Use DX12 if you are on a recent six-core-or-more CPU, the game is CPU-limited, and its DX12 mode is well optimized – and always for ray tracing, which requires DX12. Use DX11 if the game’s DX12 mode stutters or is unstable, or if you are on an older or thermally limited machine where the simpler, driver-managed path runs steadier. The right move is to try both and keep whichever gives better 1% lows.
Does DX12 give ray tracing?
Yes – hardware ray tracing, mesh shaders, and most modern rendering features require DX12 (or Vulkan). DX11 cannot do them. So if a game offers ray tracing, you are using DX12 to get it, and the question becomes whether your GPU has the headroom rather than which API to pick.
How do I switch between DX11 and DX12?
Most games that support both expose it in the graphics or display settings as a ‘Graphics API,’ ‘Renderer,’ or ‘DirectX version’ dropdown, and the change takes effect after a restart of the game. Some use a launch option instead (for example a -dx11 or -dx12 flag). After switching, test the same scene on each and compare frame-time consistency, not just the average FPS counter.

Corrections

Last updated
Methodology
See our methodology for research and review standards.
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.

About the author

Written by Lowell K. Wood IV, who builds and runs TechFuelHQ from St. Louis, Missouri.