There is no universal winner between DirectX 11 and DirectX 12. DirectX 12 can lower CPU overhead and spread rendering work across more cores, which helps in CPU-bound games on modern hardware. DirectX 11 is simpler, more mature, and often more stable, which helps in older games and on weaker PCs. Use DirectX 12 first on a modern gaming PC. If a game crashes, stutters, or runs worse, switch it to DirectX 11 and keep whichever version feels smoother.
Introduction
Open the graphics settings of a modern PC game and you will often find a small dropdown: DirectX 11 or DirectX 12. It looks like a simple choice between old and new, and the obvious answer seems to be the newer one. In practice, that dropdown has started arguments in forums for a decade, because the right answer changes from game to game, and sometimes from one PC to the next.
The confusion is understandable. DirectX 12 is newer, lower level, and more powerful on paper. It gives developers more control, cuts driver overhead, and supports ray tracing. Yet plenty of players report that their game runs better on DirectX 11, with fewer stutters, faster loading, and fewer crashes. Both groups are right. The API is only half the story. The other half is how well the game was built to use it.
This guide explains what actually changes between the two versions, how each one treats your CPU, when DirectX 12 helps a bottleneck and when it makes things worse, and how to switch and test on your own PC. No invented benchmarks, no guaranteed FPS numbers, just the mechanics and a clear way to decide for each game you play.
 What Is DirectX, and What Is an API?
DirectX is a set of tools from Microsoft that lets games talk to your hardware on Windows. A game does not speak directly to your graphics card. It speaks to an API, an application programming interface, which is a middle layer that translates the game’s requests into instructions the GPU driver and hardware understand. The graphics part of DirectX is called Direct3D, so when people say DirectX 11 or DirectX 12 in gaming, they usually mean Direct3D 11 and Direct3D 12.
Think of the API as a restaurant kitchen. The game is the customer placing orders. The API is the system that takes those orders, organizes them, and hands them to the cooks. DirectX 11 runs the kitchen with a head chef who manages everything behind the scenes. The customer just orders, and the chef figures out the details. DirectX 12 hands the customer the kitchen keys and says: organize it yourself, your way, and it can run faster, but if you organize it badly, dinner is late.
That trade-off is the whole story of DirectX 11 vs 12. DirectX 11 does more hand-holding. DirectX 12 gives more control. More control means a higher ceiling for a skilled developer, and a lower floor for a careless one.
DirectX 11 arrived in 2009 with Windows 7. DirectX 12 arrived in 2015 with Windows 10. That age gap matters, because DirectX 11 had years to mature, and its drivers are battle-tested across thousands of games. DirectX 12 is the standard for new games now, but it demands more from the people building the game.
How DirectX 11 Handles Your CPU
DirectX 11 keeps most of the hard work inside the driver and the API itself. When a game wants to draw something, it sends the request through a device context, and the driver takes care of the details: managing memory, tracking the state of resources, and submitting work to the GPU. The developer writes less code to get a working renderer, and the driver absorbs the complexity.
That convenience has a cost, and the cost lands on your CPU. The driver work happens largely on one main thread, and in a busy scene the driver can become a bottleneck of its own. If a game is constantly feeding the GPU new work, the single-threaded submission path can keep one CPU core busy while the others sit idle. Your processor might show low overall usage while one core is maxed out, and your frame rate sags anyway. That is the classic DirectX 11 CPU bottleneck: not a weak CPU, but a CPU that cannot use all of its cores for rendering work.
This is also why DirectX 11 feels so reliable. The driver does the same well-tested job in every game, so the behavior is predictable. Games load faster, because there is less shader work to prepare up front. Crashes are rarer, because the driver catches mistakes that would be the game’s fault under DirectX 12. For older games and older hardware, that maturity is worth more than the extra performance DirectX 12 might offer.
How DirectX 12 Is Different
DirectX 12 moves the hard work from the driver to the game. Instead of a single device context that the driver manages, the game records command lists, which are bundles of drawing and resource work, and submits them to command queues. Command lists can be prepared on multiple CPU threads at the same time, and they can be recorded ahead of time and reused. That is the core change, and it is the reason DirectX 12 can scale across modern multi-core processors.
Microsoft describes the change plainly in its Direct3D 12 programming guide: DirectX 12 drops the immediate context model, and apps record and submit command lists that can go to one or more command queues from multiple threads. The same guide notes that this increases efficiency by letting apps pre-compute rendering work for later reuse and by spreading work across threads.
The practical result is lower driver overhead. The CPU spends less time inside the driver and more time on the game itself. In a CPU-bound game, one that throws thousands of draw calls at the graphics card, that saving can be the difference between a smooth frame rate and a stuttering one. In a GPU-bound game, where the graphics card is already the limiting part, the saving changes almost nothing, because the CPU was never the problem.
The price of that control is responsibility. The game now has to manage memory, track resource states, and synchronize the CPU and GPU itself. A mistake that the DirectX 11 driver would have caught becomes a crash, a visual glitch, or a stutter in DirectX 12. That is why two games on the same engine can feel completely different: one team used the control well, the other did not.
DirectX 11 vs DirectX 12 at a Glance
| Feature | DirectX 11 | DirectX 12 |
|---|---|---|
| Release | 2009, with Windows 7 | 2015, with Windows 10 |
| Control level | Higher level, driver manages more | Lower level, game manages more |
| CPU threading | Mostly single-threaded submission | Multi-threaded command lists and queues |
| Driver overhead | Higher, driver does more work | Lower, game does more work |
| Ease for developers | Easier, faster to build | Harder, more code and more testing |
| Ray tracing | No native support | Yes, DirectX Raytracing |
| Variable rate shading | No | Yes |
| Mesh shaders | No | Yes |
| Stability in older games | Usually better | Can be worse if the port is weak |
| Loading and shader stutter | Usually less | Can be more on first runs |
| Best for | Older games, weaker PCs, stability | Modern games, strong CPUs, new features |
CPU Overhead and the Bottleneck Angle
This is where the DirectX choice connects directly to bottlenecks, and it is the part most guides rush past.
Every frame your game draws starts with draw calls, the individual instructions that tell the GPU to draw one object. A simple scene might need hundreds. A dense open world with crowds, traffic, and detailed buildings can need many thousands. Each draw call costs CPU time to prepare and submit.
Under DirectX 11, that submission work funnels through the driver on a limited number of threads. When draw calls pile up, the CPU becomes the bottleneck even if your graphics card has power to spare. You can see it in monitoring tools: GPU usage drops below 90%, one CPU core sits near 100%, and the frame rate stops climbing no matter how far you lower the graphics settings. Lowering resolution does not help, because the problem was never the GPU.
DirectX 12 attacks exactly that problem. By letting the game prepare command lists across many threads, it spreads the submission work and reduces the driver overhead per draw call. On a modern 8-core or 16-thread CPU, that can free up enough processor time to raise the frame rate in a CPU-bound game, or at least to smooth out the worst frame dips. Microsoft documents this directly: the Direct3D 12 graphics overview describes DirectX 12 as faster and more efficient than any previous version, built for fuller use of modern GPU hardware.
But there is a catch that matters for real players. DirectX 12 only helps if the CPU is actually the limiting part. If your graphics card is already running at 99% usage, switching APIs will not make it faster, because the GPU was never waiting on the CPU. And if the game’s DirectX 12 implementation is weak, the extra control can make things worse: shader compilation stutter when new effects appear, random crashes, or worse 1% lows than the DirectX 11 version of the same game.
The honest way to decide is to check which part is limiting you first. Our guide on how to fix a CPU bottleneck explains the fixes that actually work, and if you want to understand the frame dips you feel during play, our guide on what frame time is and why 1% lows matter explains the metric that tells you more than average FPS ever will. If your CPU is the limit and the game has a good DirectX 12 mode, switch. If your GPU is the limit, the API choice is not your problem, and your time is better spent on settings that lighten the GPU load, which our guide on how to increase FPS covers in detail.
Which Games Run Better on DirectX 12
DirectX 12 tends to help most in newer games that throw a lot at the CPU and GPU at once. Large open worlds, dense city scenes, big battles with many characters on screen, and games with ray-traced lighting are the cases where the lower overhead shows up. These are also the games most likely to have a mature DirectX 12 renderer, because their developers built the game for it from the start rather than bolting it on later.
The gains are usually strongest on current mid-range and high-end hardware. A recent Ryzen or Core CPU with a modern Radeon or GeForce card is the combination that benefits most, because it has the cores to spread the work and the GPU to keep up once the CPU stops holding it back. On that kind of system, DirectX 12 often gives the best mix of features and performance.
There is a second group that benefits quietly: simulation and strategy games with heavy CPU simulation. These games were always CPU-limited, and the extra threading headroom from DirectX 12 can help even when the graphics are simple. The gain shows up as a smoother simulation rather than prettier pictures, which is easy to miss if you only watch the FPS counter. Other comparisons of DirectX 11 and 12 reach the same conclusion: the better choice depends on the game and the hardware.
When DirectX 11 Still Wins
DirectX 11 still wins in three situations, and they cover a lot of real gaming.
First, older games. A game built for DirectX 11 in 2016 is not going to run better because you force a DirectX 12 mode onto it. If the game offers both, the DirectX 12 path is often a later addition with less testing, and the DirectX 11 path is the one the developers tuned for years. Use the version the game was designed around.
Second, weaker PCs. On an older quad-core CPU or a low-end graphics card, DirectX 12 has less to work with. There are fewer cores to spread the load across, and the extra memory management work the game takes on can cost more than the driver overhead it saves. DirectX 11 is the safer pick here, and it usually loads faster too.
Third, games with a shaky DirectX 12 implementation. The symptoms are easy to spot: stutter when new effects load for the first time, long shader compilation on launch, random crashes, or frame times that spike even though average FPS looks fine. These are signs that the game’s DirectX 12 renderer is not mature. Switch to DirectX 11 and the problems usually go away. A stable 60 FPS on DirectX 11 beats an unstable 70 FPS on DirectX 12 every time.
Ray Tracing, Mesh Shaders Features Only DirectX 12 Has
Some features simply do not exist on DirectX 11, and this is the clearest reason to use DirectX 12 when your hardware supports them.
Ray tracing is the biggest one. DirectX Raytracing, or DXR, is part of DirectX 12, and it is how games do realistic reflections, shadows, and global illumination. DirectX 11 has no equivalent. If you want ray tracing in a game, you need DirectX 12, a compatible GPU, and the performance headroom to pay for it.
Variable rate shading lets the GPU spend less effort on parts of the screen where detail matters less, like dark corners or fast-moving backgrounds, and more effort where your eye actually looks. Mesh shaders change how geometry is processed, letting games draw far more detailed scenes with less CPU work. Sampler feedback helps the GPU stream textures more efficiently. These are all DirectX 12 features, and they are the reason new engines are built on DirectX 12 rather than DirectX 11.
The newest tier, DirectX 12 Ultimate, bundles ray tracing, variable rate shading, mesh shaders, and sampler feedback together. It needs newer hardware: NVIDIA RTX 20 series or newer, or AMD RX 6000 series or newer. If your card is older than that, you can still use DirectX 12, but the Ultimate features will not be available to you.
None of this means DirectX 12 is automatically better for your game. Features only help if the game uses them and your hardware can run them. A ray tracing toggle on a card that cannot handle it will cost you more frames than the API ever saved.
How to Switch Between DirectX 11 and 12
Switching is easy. The hard part is knowing where the option lives, because every game hides it in a different place.
Most games put the choice in the graphics or display settings menu, labeled as DirectX Version, Rendering API, or Graphics API. Some games offer it in a launcher before the game starts. A few games need a launch option: on Steam, right-click the game, choose Properties, and add -dx11 or -dx12 to the launch options. Other games store the choice in a configuration file or only let you pick it on first launch.
After you switch, restart the game completely. Changing the API without a restart can leave the game in a mixed state, and the first launch on DirectX 12 may take longer than usual while shaders compile. That first-run shader compilation is normal, and it is also the reason some players wrongly conclude that DirectX 12 stutters: they judged it on the first run, when the game was still building its shader cache. Play for ten minutes, let the cache build, and then judge.
If a game only offers DirectX 12, you cannot switch it to DirectX 11. That is increasingly common with new releases, and it is a sign that the developers have committed to the newer API. In that case your job is to make DirectX 12 run well: update your graphics driver, give the shader cache time to build, and lower the settings that cost the most performance.
What About Vulkan?
Vulkan deserves a short mention, because some games offer it as a third choice alongside DirectX 11 and 12. Vulkan is a low-level, cross-platform API built on the same ideas as DirectX 12: explicit control, multi-threaded command submission, and low driver overhead. The difference is that Vulkan works on Windows, Linux, and Android, while DirectX is Windows and Xbox only.
In games that offer all three, Vulkan often performs similarly to DirectX 12, and sometimes a little better on AMD hardware. It is worth trying if the game offers it and DirectX 12 gives you trouble. But Vulkan is not a magic fix either. It has the same dependence on a good implementation, and a weak Vulkan renderer will stutter just like a weak DirectX 12 one. Treat it as another option to test, not as an automatic upgrade.
Common Mistakes
Assuming newer always means faster. DirectX 12 is newer and more capable, but a weak DirectX 12 implementation loses to a mature DirectX 11 one. The version number is not a performance guarantee.
Judging DirectX 12 on the first launch. The first run compiles shaders, which causes stutter and long loads. Judge it after the shader cache is built, not before.
Switching APIs to fix a GPU bottleneck. If your graphics card is at 99% usage, the API is not your problem. Lower the GPU-heavy settings instead. The API choice only matters when the CPU is the limit.
Ignoring 1% lows. Average FPS can look the same on both APIs while one of them stutters badly. Compare the worst frames, not the average. Our guide on why your FPS is so low explains how to read the numbers that actually describe what you feel.
Forcing DirectX 12 on old hardware. On an old quad-core CPU or a graphics card from before 2015, DirectX 12 has little to work with and can run worse than DirectX 11. Match the API to your hardware, not to the calendar.
Blaming the API for a bad port. If a game runs badly on both APIs, the problem is the game, not the API. No setting will save a broken port.
Expert Tips
Test both APIs in the game you actually play. Benchmarks from other games tell you nothing about yours. Use the same scene, the same settings, and an overlay that shows 1% lows. Keep the version with steadier frame times.
Give DirectX 12 a fair test. Play for at least ten minutes after switching so the shader cache builds. A one-minute test measures compilation stutter, not the API.
Use DirectX 12 when you want ray tracing. There is no DirectX 11 path to ray tracing. If the feature matters to you, DirectX 12 is the only choice, and your hardware has to be up to it.
Keep DirectX 11 as your fallback. When a new game launches with a rough DirectX 12 mode, the DirectX 11 option is your safety net. It is there for a reason, and using it is not giving up performance. It is choosing stability.
Update drivers before you compare. A DirectX 12 comparison on old drivers is a comparison of old bugs. Update first, then test.
Check the PCIe link too. If your graphics card is not getting its full bandwidth, no API choice will fix it. Our guide on whether PCIe bandwidth bottlenecks your GPU shows how to check the link speed and what to do if it is wrong.
Frequently Asked Questions
Is DirectX 12 better than DirectX 11 for gaming?
It depends on the game and your hardware. DirectX 12 can be better in CPU-bound games on modern hardware, because it lowers driver overhead and spreads work across more cores. DirectX 11 can be better in older games, on weaker PCs, and in games with a weak DirectX 12 implementation. Test both in the game you play and keep the smoother one.
Does DirectX 12 increase FPS?
Sometimes, and never by a fixed amount. In a CPU-bound game with a good DirectX 12 renderer, it can raise FPS and smooth frame times. In a GPU-bound game, it changes almost nothing, because the graphics card was already the limiting part. No honest guide can promise a specific FPS gain, because the result depends on the game, the hardware, and the quality of the implementation.
Does DirectX 12 reduce CPU bottleneck?
Yes, that is its main strength. By letting games prepare command lists on multiple threads and cutting driver overhead, DirectX 12 reduces the CPU work involved in submitting frames. On a modern multi-core CPU in a draw-call heavy game, that can ease a CPU bottleneck noticeably. It will not fix a CPU that is simply too weak for the game, and our guide on how to fix a CPU bottleneck covers the fixes that do.
Which DirectX version should I use?
Use DirectX 12 first on a modern gaming PC with a recent CPU and GPU, especially if the game was built for it or you want ray tracing. Use DirectX 11 if the game is older, if your PC is weak, or if the DirectX 12 mode crashes or stutters. The best version is the one that runs your game most smoothly, not the newest one.
Can I use DirectX 12 on Windows 10?
Yes. DirectX 12 requires Windows 10 or later, and it works on both Windows 10 and Windows 11. DirectX 11 works on Windows 7 and newer. If you are still on Windows 7 or 8, DirectX 12 is not available to you.
What graphics cards support DirectX 12?
Most graphics cards released since 2015 support DirectX 12, including NVIDIA GTX 900 series and newer and AMD RX 400 series and newer. The newest DirectX 12 Ultimate features need newer hardware: NVIDIA RTX 20 series or newer, or AMD RX 6000 series or newer. Older cards can still run DirectX 12 games, but without the Ultimate features.
Why does DirectX 12 stutter in some games?
The most common cause is shader compilation. DirectX 12 compiles shaders when new effects appear, and that work can pause the game for a moment. The stutter usually fades as the shader cache builds. Other causes are a weak DirectX 12 implementation in the game, or a CPU that is too slow to handle the extra management work the game takes on. If stutter does not fade after several sessions, switch to DirectX 11 and compare.
How do I switch from DirectX 12 to DirectX 11?
Look in the game’s graphics or display settings for a DirectX Version, Rendering API, or Graphics API option. Some games offer it in a launcher. On Steam, you can also right-click the game, open Properties, and add -dx11 to the launch options. Restart the game completely after switching.
Is Vulkan better than DirectX 12?
Sometimes, on some hardware, in some games. Vulkan is a low-level API like DirectX 12, and in games that offer both, performance is often close. Vulkan can be a good alternative if DirectX 12 gives you trouble, especially on AMD hardware. Like DirectX 12, it depends entirely on how well the game implements it.
Key Takeaways
- DirectX 11 is a higher level API where the driver manages more work. DirectX 12 is lower level, giving the game more control and lower driver overhead.
- DirectX 12 can reduce CPU overhead and spread rendering work across more cores, which helps CPU-bound games on modern hardware.
- DirectX 11 is often more stable, loads faster, and runs better in older games and on weaker PCs.
- Ray tracing, variable rate shading, and mesh shaders need DirectX 12. DirectX 11 cannot run them.
- DirectX 12 can stutter on first runs while shaders compile. Judge it after the shader cache is built.
- There is no universal FPS winner. Test both APIs in the game you play, compare 1% lows, and keep the smoother one.
Conclusion
DirectX 11 vs DirectX 12 is not a contest with a single winner. It is a trade-off between control and convenience, and the right answer depends on your game, your hardware, and how well the developers used the tools they were given. DirectX 12 has the higher ceiling: lower CPU overhead, better use of modern multi-core processors, and features like ray tracing that DirectX 11 cannot offer. DirectX 11 has the higher floor: mature drivers, predictable behavior, and stability that a rushed DirectX 12 port cannot match.
For most players on a modern PC, the practical rule is simple. Start with DirectX 12. Give it a fair test with a built shader cache. If the game runs smoothly, enjoy the features and the lower overhead. If it crashes, stutters, or feels worse than you expect, switch to DirectX 11 without guilt. A stable game on the older API is always better than a stuttering game on the newer one.
The API dropdown is one setting among many, and it will never fix a real hardware mismatch. If your games struggle on both APIs, the bottleneck is somewhere else. Work out which part is holding you back with our guide to finding a PC bottleneck, and if a new graphics card is on your mind, our best GPU buying guide explains how to pick one that matches your CPU instead of fighting it.
Leave a Reply