Baldur's Gate 3 Best Settings for Performance and Visuals on PC

Baldur's Gate 3 looks gorgeous on a beefy PC, and it'll gladly chew through every bit of GPU and CPU power you hand it. For long stretches it runs smooth as silk. Then you wander into Act 3, or boot up split-screen with a buddy, and your frame rate falls off a cliff.

The graphics menu is stuffed with toggles and sliders, which is great news. You can claw back a ton of frames without turning the world into a blurry mess. Some options move the needle a lot, others barely budge it, and knowing which is which saves you the most frames for the least visual cost.

Graphics Presets and FPS Impact

Baldur's Gate 3 ships with four presets: Ultra, High, Medium, and Low. You can grab one off the top of the graphics menu and call it a day, but the presets are kind of blunt tools. A custom setup lands you way better results for the same frame budget.

Start at High, not Ultra

Here's the thing about Ultra. The jump from High to Ultra burns a real chunk of your frame rate for a payoff you have to squint to see. Textures get a touch crisper, shadows soften a hair, and that's about it. Most players on a mid-range card are better off parking at High and spending their frames elsewhere.

The flip side is to avoid Medium and Low if you can help it. Drop all the way down and the game starts looking rough fast. Faces lose detail, the lighting goes flat, textures turn muddy. Digital Trends found the Medium and Low presets gut the image quality, so reach for them only when nothing else keeps you above your target.

A good rule of thumb from the community: load in at High, and step down to Medium only if you can't hold a steady 60. (Some folks chasing 144 push higher first, then dial back. Either way works.)

The settings that eat the most frames

Not every toggle costs the same. A handful do the heavy lifting, and the rest barely move the number.

• Shadow Quality is a big one. Dropping it from Ultra to Medium saves a fair amount of GPU work, and shadows at Medium still look plenty good. Usually the first place to trim.
• Cloud Quality and Fog Quality follow the same pattern. Medium clouds, Low fog is a sweet spot. Fog is barely visible most of the time, so cutting it costs you almost nothing to look at.
• Model Quality sets how detailed characters and objects look up close and far away. Medium is the safe pick. Bump it to High if you have frames to spare.
• Detail Distance controls how far away shadows and reflections stay crisp. Low is fine here, since the big shadows stick around either way.
• Instance Distance sets the detail on small clutter like rocks and bushes. High looks nicer, Medium is acceptable, and the frame hit between them is small.

The post-processing quartet

Down at the bottom of the menu sit four switches that barely change how the game looks but save a surprising amount of performance: Depth of Field, God Rays, Bloom, and Subsurface Scattering. Depth of Field in particular is a frame hog.

Turn all four off if you're scraping for frames. They add some cinematic gloss, sure, but the world holds up just fine without them. Digital Trends pegged this group as the single biggest chunk of "free" performance in their testing, with a tuned setup netting close to a 16 percent bump over the Ultra preset for very little visual cost.

That's the whole game with graphics options in a nutshell. Trim the heavy hitters (shadows, clouds, fog), kill the post-processing quartet, keep textures high, and you've basically rebuilt the Ultra look at a lower frame cost.

A couple you can leave alone

Some settings barely move the needle, so don't waste time agonizing over them. Texture Filtering at Anisotropic x16 has almost no performance hit, so leave it cranked. Animation Level of Detail on High versus Low is worth maybe a single frame, per the Steam community, so keep it on High. These are free wins that make the game look better for nothing.

Vulkan API and Driver Considerations

When you launch the game, the little launcher window asks a question a lot of people skip past: DirectX 11 or Vulkan? It defaults to DX11 on Windows, and most folks never think about it again. The choice actually matters, just not in the way you'd guess.

What the testing shows

Here's where it gets a little messy, because the answer changes with your hardware. On Nvidia cards, DirectX 11 tends to post the higher average frame rate. Testing from PC Gamer put DX11 somewhere around 6 to 13 percent faster than Vulkan, and Digital Foundry landed near 8 percent. Digital Trends saw a smaller gap, closer to 2 percent, which is basically noise.

So Nvidia owners usually get a few extra frames out of DX11. The catch is the 1 percent lows, which measure your worst, choppiest moments. Vulkan tends to hold those steadier. Translation: your average number might read a touch lower, but the game feels smoother because the dips aren't as deep. Plenty of people pick the smoother feel over the bigger average.

AMD and Intel go the other way

On AMD and Intel graphics, the picture flips. Vulkan runs about even with DX11, sometimes a hair ahead. If you're not on Nvidia, Vulkan is the safer default and often the faster one too.

When crashes enter the chat

This is where Vulkan earns its keep for a chunk of players. DX11 has a reputation for crashes and a memory-leak-style slowdown where the frame rate crumbles the longer you play. Larian's own forums are full of folks reporting a crash or three an hour on DX11 that vanish the second they switch to Vulkan.

The flip side is real too. A smaller group finds Vulkan flaky and DX11 rock solid. There's no universal winner on stability, which is kind of annoying, but it also makes the fix easy. If you're crashing or stuttering, swap APIs and see what happens. It's the first troubleshooting step for a reason.

Keep your drivers fresh

Whichever API you pick, an up-to-date graphics driver matters more than people think. Nvidia and AMD both push game-specific fixes, and a lot of the early BG3 crash and stutter complaints traced back to old or partly-broken driver installs. Grab the current Game Ready or Adrenalin release before you chase anything fancier.

A clean driver install is worth it if you're still stuck after updating. Tools like DDU wipe the old drivers completely so the new ones don't inherit leftover junk. Overkill for most, but a lifesaver when nothing else works.

Control panel settings worth knowing

Inside the Nvidia Control Panel (or AMD's Adrenalin software), a few tweaks help. Cap your frame rate if your card runs hot, which is common in split-screen. Turn on a larger shader cache, since BG3 builds a big one and a tiny default size can force recompiles. And if you have a G-Sync or FreeSync monitor, make sure variable refresh is actually on, because it pairs beautifully with the in-game vsync options.

Upscaling Options FSR and DLSS

Upscaling is the closest thing to free frames in this whole game. The renderer draws the picture at a lower resolution, then a smart algorithm blows it back up to your monitor's size. Done right, you get most of the visual quality for a lot less work. Baldur's Gate 3 hands you a few flavors to pick from.

DLSS, if your card can run it

If you have an Nvidia RTX card (20-series or newer), DLSS is your best bet. It's the sharpest and most stable of the bunch, and the performance gain is serious. PC Gamer measured about a 55 percent frame-rate boost at 4K with DLSS Quality, and Performance mode pushed that closer to 99 percent.

Quality mode is the sweet spot for most people. It looks very close to native resolution while handing back a healthy chunk of frames. Balanced sits in the middle. Performance mode squeezes out the most speed but starts to soften the image, so reach for it only when you really need the headroom.

There's also DLAA, Nvidia's Deep Learning Anti-Aliasing. Instead of boosting frames, it spends its budget making the picture sharper than native. If your card already flies at your target resolution and you want it to look as crisp as possible, DLAA is a neat trick.

FSR, for everyone else

FSR is AMD's upscaler, and the big plus is that it runs on any GPU. AMD card, Intel card, older GTX, it doesn't matter. The catch is quality. The launch version of the game shipped with FSR 1.0, and honestly it looked pretty rough. Hair, foliage, and detailed cloth got smeared or shimmery.

That got fixed. Patch 4 brought in FSR 2.2, which is a big step up and the one you want to use. Stick to Quality or Ultra Quality mode and it looks decent, more or less native with a little softening. Avoid FSR Performance mode unless you're truly desperate. In PC Gamer's testing it posted a monster frame-rate gain (around 129 percent) but turned fine detail like blood decals into a blocky mess.

So the short version: FSR 2.2 on Quality is a solid fallback, DLSS on Quality is the goal, and FSR Performance is a last resort.

Intel XeSS and the frame-generation question

Intel XeSS joined the party later and works on a broader range of cards than DLSS. If you're on an Intel Arc or an older Nvidia or AMD chip without DLSS, XeSS is another respectable upscaler to try alongside FSR.

What about frame generation, the DLSS 3 feature that invents extra frames between the real ones? Baldur's Gate 3 doesn't support it natively. You can add it with community mods (the PureDark upscaler mod is the famous one), but patches have broken those mods before and they're a moving target. For most people, plain upscaling plus a well-tuned settings list is the safer play.

A note on sharpening

Leave FidelityFX Sharpening on when you're upscaling. Upscaled images tend to look a little soft, and a touch of sharpening brings back the crispness without much cost. It's a one-click fix that makes DLSS and FSR both look better, so there's no reason to skip it.

Split-Screen and Multiplayer Optimization

If there's one part of Baldur's Gate 3 that punishes your hardware, it's split-screen. Two players, two cameras, two chunks of the world rendering at once. Your PC is basically running the game twice, and nothing exposes a weak CPU or a hot-running GPU faster.

Why it's so heavy

Single-player can glide along at 100-plus frames in the early acts. Add a second local player and that number gets cut way down, even on the same machine. The Steam community has reports of split-screen tanking to single digits in bad spots, with freezes and crashes layered on top. Consoles have it rough too. A PS5 split-screen test bottomed out around 21 frames in busy areas.

The root cause is simple. With two viewports, the engine draws everything twice, and your CPU has to simulate the world for both players at once. There's no magic toggle that makes this cheap.

Act 3 is the real boss fight

Remember how Act 3 chews up single-player frame rates? It's worse in split-screen, a lot worse. The city is dense, the crowds are thick, and now you've got two cameras wandering through it. If you and your co-op partner are heading into the Lower City, brace for impact and drop settings before you go, not after.

The settings that help most

The usual suspects apply, just dialed up a notch. Shadows, clouds, and fog can drop to Medium or Low without wrecking the look. The post-processing quartet (Depth of Field, God Rays, Bloom, Subsurface Scattering) should go off, since you're now paying for it twice. Model Quality at Medium is plenty. And if your card is cooking itself, a frame-rate cap in the control panel keeps the heat down, because split-screen pushes thermals hard.

Dynamic Crowds is worth a look here too. It controls whether the city's NPCs mill around with full animations. Turn it off in split-screen and you trade some street life for a steadier frame rate. That trade's usually worth it when you're already struggling.

Stutter and freeze fixes

A counterintuitive fix that comes up over and over: turn on Vsync with Triple Buffering, even on a G-Sync monitor. Plenty of players swear it smooths out the micro-stutters that haunt split-screen. You give up a hair of input responsiveness, which barely matters in a turn-based game.

Beyond that, the basics apply. Update your GPU driver. Verify your game files through Steam or GOG if crashes hit, since a corrupted file can cause the freeze-every-minute problem. Close background apps. And if your machine is overheating, that's not a settings problem, it's a cooling problem, so check your fans and dust.

The honest takeaway on split-screen

There's no preset that makes split-screen buttery on modest hardware, and Larian has shipped fixes but the core load hasn't gone away. Lower your expectations, lower your settings, and consider online co-op instead of local if your rig can't keep up. Online co-op runs the world on each player's own machine, so it sidesteps the whole double-render problem.

Load Time and Shader Cache Fixes

Long loads and the dreaded "compiling shaders" hang are the two things that make people think their PC is broken. Usually it's not. Most of the time it's a one-time cache build, the wrong storage drive, or a stale driver, and the fixes are pretty painless.

The first-load tax is normal

The first time you launch Baldur's Gate 3, it spends a while compiling shaders before you hit the main menu. That's the game pre-building a cache of how to draw things on your specific GPU, and it only really hurts the first time. Let it finish. Interrupting it doesn't save you anything and can leave you with a half-built cache that causes trouble later.

The same thing happens whenever you switch graphics APIs (more on that below) or update your GPU driver. A fresh driver brings a fresh shader cache, so expect a longer load the next time you boot.

An SSD isn't optional, it's the rule

The system requirements list a 150GB SSD for a reason. The game streams assets in constantly as you move, and a spinning hard drive just can't feed it fast enough. On an HDD you'll see textures and geometry pop in, hitching as new data loads, and noticeably longer load screens.

If you're stuck on a hard drive, the in-game Slow HDD Mode is your friend. It parks more of the game data in your system RAM and VRAM to compensate. The trade-off is more pop-in and some performance hit, but it beats constant stuttering. The honest fix is still moving the game to an SSD, which makes all of this go away.

The API swap that fixes stuck loads

This one's a genuine lifesaver. Some players hit a bug where the loading screen before the main menu takes 20 minutes or hangs forever. The fix that comes up again and again on Larian's forums: switch from DirectX to Vulkan (or Vulkan to DX11).

The first load after the swap will be slow because the game rebuilds its shader cache for the new API. After that, loads drop back to normal. If you're stuck on a load screen, try the other renderer before you try anything else.

Bump your shader cache size

Nvidia owners can give the game more room to store its shaders, which stops the recompiling churn. Open the Nvidia Control Panel, head to Manage 3D Settings, find Shader Cache Size, and set it higher. Community guides suggest 10GB or even Unlimited if you have the drive space. A bigger cache cuts down on recompiles, so you sit through fewer long loads.

If things are already broken, you can wipe the cache and start fresh. The in-game graphics menu has a Restart Shaders option that rebuilds it cleanly. On Windows you can also delete the cache folder by hand to force a clean rebuild when a corrupted cache is causing crashes or stalls.

Driver updates, again

It keeps coming back to drivers because it keeps being the fix. A new driver release often sorts out shader compilation hangs and load-screen freezes, especially right after a big game patch. Before you go deep on troubleshooting, update, reboot, and let the game rebuild its shaders once. You'd be surprised how often that's the whole fix.

If your load times suddenly got worse after a patch and nothing else has helped, swapping your graphics API and letting the shader cache rebuild from scratch is the single most reliable trick in the box. It costs you one long load. It usually gives you back everything else.