The Best DuckStation Settings for PS1 Emulation in 2026
I remember opening DuckStation's settings menu for the first time and just staring at it, asking myself... what in the world is all this?
Tabs inside tabs, options referencing other options, and settings with names that sound like they belong in a GPU engineering handbook. It's a lot, probably too much, but that's the power of DuckStation!
The thing is, most of it genuinely does not matter for normal play. A huge chunk of those settings are debugging tools, developer options, and one-off compatibility fixes for specific games that maybe one percent of people will ever encounter. You do not need to understand all of it, you just need to know which things are safe to ignore, which things are worth trying, and which things will break your game if you so much as look at them wrong (or accidently flick them on!)
If you are new to DuckStation and want to get into a game in the next five minutes, set these and do not touch anything else. Everything else in this guide can wait.
Internal Resolution: 2x for most hardware, 1x as fallback if things slow down
Threaded Rendering: On
Multi-Sampling (MSAA): Off — it breaks games constantly
PGXP Depth Buffer: Off — DuckStation calls it "low compatibility"
Texture Cache + Replacements: Off unless you know exactly what you are doing
PGXP Geometry Correction: On if 3D looks wobbly, off otherwise
Everything else: Default. Just play.
The Three Areas You Actually Need
DuckStation was built by and for people who already know what a GPU pipeline is. The settings menu reflects that. Most of what you are looking at is developer tooling, per-game accuracy options, and debugging features that exist for the one person in a thousand who needs them. The general-audience stuff is in there too, it is just mixed in with everything else rather than separated out, which is why opening it cold feels like being handed a full server rack when you asked for a power strip.
The practical map is three areas. The Graphics page is the big one, where all the actual drawing happens. The On-Screen Display page handles the messages and counters that float over the game. And Post-Processing is where you stack filters over the finished image, like CRT scanlines or a decorative bezel around the screen.
That is the whole map. Everything else lives inside one of those three rooms, and most of it you will never need.
The Rendering Settings
Settings → Graphics → Rendering
These are the settings that matter the most. They control how the game gets drawn, how sharp it looks, and whether any of the PS1's infamous visual quirks get cleaned up or left alone. If you are only reading one section, make it this one. With a few changes you can make Mega Man Legends look brand new!
Software mode draws every pixel by hand on your CPU. It is slow, but it works in practically every game you could throw at it. Hardware mode uses your GPU, runs much faster, and unlocks all the nice visual upgrades like higher resolution and texture filtering. In practice, Hardware mode on a modern machine means Vulkan, which is what DuckStation defaults to and generally the right call. D3D11 is there as a fallback if Vulkan gives you trouble on older Windows hardware. Automatic picks correctly for most setups, so leave it here and go play something. The one exception worth knowing: if Automatic selects Hardware and a game immediately looks broken or refuses to load, try switching to Software manually. Some older GPU configurations do not behave with Hardware mode and Software will get you in.
The PS1 drew at a small resolution that looked fine on a fuzzy CRT but looks noticeably blocky on a modern monitor. Bumping this to 2x or 3x tells DuckStation to draw those 3D shapes at a larger size first, so edges get sharper and everything looks cleaner. If you have a modern PC or a mid-range Android device, 2x is a reasonable starting point rather than 1x, because 1x on a 1080p screen looks rougher than most people expect. 1x is there as a fallback if things slow down, not as the intended experience. If a game does start stuttering after you raise this, bring it back down one step.
Nearest is the real PS1 look — blocky, authentic, slightly rough on a modern monitor. Smooth options blur the textures a little so they do not look as chunky, which works better at higher resolutions but loses some of the original character. Neither answer is wrong. If you are not sure, try Nearest first and switch if it bothers you.
PS1 games were built for old 4:3 televisions, so the characters and levels were designed with that boxy shape in mind. Auto keeps the correct ratio for whatever game you are running. If your game looks like everyone got hit with a cartoon steamroller and appears weirdly squished or stretched, this is the first thing to check.
This is one of DuckStation's best features and one of its most temperamental ones. PS1 3D was notoriously jittery, polygons wobbling, textures warping as the camera moved, the whole thing with this liquid quality that was charming at the time and slightly maddening now. PGXP Geometry Correction is what fixes that, and when it works it works beautifully. The catch is that DuckStation warns it may not be compatible with all games. Try it per game, and if a title misbehaves with it on, turn it back off for that one specifically.
When two surfaces share nearly the same position in 3D space, they fight each other and flicker, which is called Z-fighting. The Depth Buffer tries to solve it using extra precision data from PGXP. It sounds great. DuckStation officially labels it "low compatibility," which is the software equivalent of a factory warning label. It breaks more games than it helps. Leave it off unless you have a specific flickering problem in a specific game and you are actively trying to fix it.
FMVs were made for 4:3. If you are running a wider aspect ratio, cutscenes will look stretched. This snaps them back automatically while gameplay stays at your preferred setting. If your cutscenes look wrong and gameplay looks fine, this is the one switch to flip.
Advanced Settings
Settings → Graphics → Advanced
Most people can scroll past this tab entirely. It is mostly for troubleshooting very specific problems, tuning performance in unusual setups, or making a streaming or capture situation work. The big exception is Multi-Sampling, which sits here looking extremely tempting and is also the single most common cause of "why does my game look broken" posts in every DuckStation community.
This is the classic "sounds so good on paper" trap. Anti-aliasing smooths rough edges on 3D geometry, and that is a genuinely nice thing to have in most emulators. The problem is DuckStation's own tooltip says it often introduces rendering errors, and it is not exaggerating. People enable this, their game immediately has broken effects or missing geometry, they go to forums asking what happened, and the answer is always this setting. Turn it off and the game goes back to normal. Just leave it disabled.
DuckStation calls this a big speed improvement and confirms it is safe. It is already on by default and there is almost no reason to turn it off. The one real exception is Software mode on very underpowered hardware, where disabling it can occasionally improve accuracy at the cost of speed. If you are running Hardware mode, which is almost everyone, just leave it on and do not think about it again.
More frames in the queue means smoother video but slightly more input lag. Fewer means snappier controls but potentially choppier output. The defaults split that trade-off reasonably. Honestly, most people playing PS1 games are not going to feel the difference either way, and if you are not having a specific stuttering or timing problem, this is one of the safer things to ignore completely.
If you are trying to capture gameplay with OBS or similar and the game is not showing up correctly, enabling this can fix it. DuckStation says it is usually slower than the default method, so you do not want it running all the time. Only enable it if you have an actual capture problem and the more obvious fixes have not worked.
PGXP Settings
Settings → Graphics → PGXP
PGXP fixes the PS1's geometry jitter, and the Rendering section already covers how to turn it on. This tab is what happens after you do. Most of these settings are only active once PGXP Geometry Correction is enabled, and the defaults for all of them are sensible. The one to watch is CPU Mode, which is the only setting here that can meaningfully hurt performance.
If you only turn on one PGXP setting, make it Geometry Correction. Everything on this tab follows from that.
The PS1 cut a corner with texture math to save processing power, which is part of why surfaces look like they are shifting and sliding as the camera moves. This corrects it. It is on by default when PGXP is active and there is no good reason to turn it off.
When PGXP repositions geometry more precisely, small gaps and holes can appear where the original code expected things to line up a certain way and they no longer do. Culling Correction patches those gaps. It is a companion to Geometry Correction more than its own thing — on by default with PGXP, leave it on.
Normal PGXP only applies its improvements to geometry going through the GPU pipeline. CPU Mode extends that to everything, which sounds more thorough but comes with a direct warning from DuckStation that it carries a "high performance cost." That is their way of saying it can make your game noticeably slower. Only turn this on if a specific game is still wobbling badly with normal PGXP and you are willing to trade speed for the fix.
Texture Replacements
Settings → Graphics → Texture Replacements
This whole tab is for people who want to swap out the original PS1 textures with high-resolution community-made versions. It is a genuinely cool feature when it works, and there are some excellent packs out there for popular games. The important thing to know before you get excited is that DuckStation labels the Texture Cache as "experimental" and says replacements are not compatible with all games, so this is not a feature you can just flip on and expect to work everywhere.
Everything else in this tab needs this to be on first. DuckStation flags it as experimental, which means it works beautifully for some games and causes problems in others. Only enable this if you are following a texture replacement guide for a game you have confirmed is supported.
This is the switch that makes the replacement pack show up when you play. Requires Texture Cache to be on. Always verify your specific game is on the supported list before enabling this, because discovering the answer through broken graphics mid-game is a bad way to find out.
If you are using a pack and textures are stuttering or popping in as you enter new areas, this is the fix. It loads everything upfront during the initial load screen instead of grabbing replacements on the fly during gameplay. Uses more RAM but makes the experience noticeably smoother. Worth it if you are committed to using a pack.
On-Screen Display
Settings → On-Screen Display
This page controls all the little messages and numbers that float on top of the game while you play. None of it affects how the game actually runs. It is purely informational. The defaults are sensible, so most people can leave this tab alone. The main reason to come here is to turn on the FPS counter when something feels slow, check it, then turn it back off.
A healthy PS1 game at full speed will show 60 FPS for NTSC games or 50 FPS for PAL games. If you are seeing numbers in the 20s or 30s, your machine is struggling and you should lower some settings. Turn this on to check, then turn it back off so it is not sitting in your eye line during normal play.
100% means everything is exactly as fast as it should be. Below 100% means the emulator is struggling to keep up. Where this gets interesting is when the two counters disagree: if FPS looks fine but Emulation Speed is above 100%, the game is running faster than it should and audio will pitch up or skip. If FPS is hitting the target but Emulation Speed is low, your machine is compensating by skipping frames you are not seeing. Running both at once gives you a much clearer picture of what is actually going wrong than either one alone.
The "Game Saved" and "Screenshot Taken" pop-ups in the corner. On by default, mostly harmless. If they bother you, turning them off is fine — errors and warnings still show up regardless, so you are not missing anything that matters.
The little icon that appears when you are fast-forwarding, paused, or rewinding. It sounds like nothing until you have spent twenty minutes wondering why everything is happening at double speed and everyone sounds like a chipmunk. Leave it on.
Post-Processing
Settings → Post-Processing
Post-processing applies visual filters after the game has already been fully drawn, like slapping a colored lens over a finished photograph before it goes to your screen. This is where CRT scanline filters live, along with color grading, screen borders, and bezels. Entirely optional and has no effect on how the game runs under the hood.
Each shader you add is another layer of work for your GPU, so stacking a bunch of them on a slower machine can cause problems. Add one at a time, test it, and only keep what you actually like.
The main switch for display-level effects. The most popular use is adding CRT scanlines so games look the way they did on old televisions, and a lot of PS1 games genuinely look more correct that way, because they were designed around that visual style. Shaders stack in a list, more shaders means more GPU work, so keep it reasonable and add things one at a time.
Places an image around the edges of the game window, like the plastic bezel of an old CRT television. Community-made packs exist that recreate specific TV models, which looks genuinely great if you want that full retro setup vibe. Minimal performance cost and entirely cosmetic.
The more technical version of the display chain, applied at an earlier rendering stage. It is for advanced users chasing a specific effect that the display chain cannot deliver on its own. Most people reading this guide will never need it, and if you are unsure whether you need it, you do not need it.
DuckStation Troubleshooting: Common Problems and How to Fix Them
Click a problem to expand the fix.
DuckStation says no BIOS found and will not start a game
Go to Settings → BIOS and point DuckStation at your BIOS file. It will not run without one. The BIOS folder needs to contain a legitimate dump from your own PS1 console — DuckStation will list any valid files it finds there and you select the one you want. If the folder is empty or the path is wrong, that is the entire problem. Fix the path, restart DuckStation, and try again.
My controller is not being recognized
Go to Settings → Controllers and check that your controller is mapped to Port 1. If nothing shows up there at all, DuckStation may not be seeing the device yet — plug the controller in before opening DuckStation, not after, since some USB controllers are only detected on startup. For PS4 and PS5 controllers on Windows, DuckStation has built-in support but you may need to disable Steam Input or any other overlay software that is intercepting the controller before DuckStation can see it.
The audio is crackling, skipping, or pitched wrong
Audio problems are almost always a sign that the emulator is not running at full speed. Go to Settings → On-Screen Display, turn on both Show FPS and Show Emulation Speed, and check the numbers while the problem is happening. If Emulation Speed is above 100%, the game is running too fast and audio is pitching up — check your frame limiter settings. If it is below 100%, your machine is struggling to keep up and you need to lower Internal Resolution or turn off PGXP CPU Mode. If both counters look fine but audio is still crackling, try increasing the audio buffer size under Settings → Audio.
The game looks stretched or squished
Go to Settings → Graphics → Rendering and set Aspect Ratio to Auto. PS1 games were designed for 4:3 televisions and stretching them to widescreen makes everything look wrong. Auto handles it correctly for each game. If cutscenes look stretched but gameplay looks fine, also enable Force 4:3 For FMVs on the same page.
I changed too many things and now nothing works
Go to Settings → General and hit Reset to Default. It is there exactly for this situation. Everything goes back to the original state and you can start fresh. You do not lose your saves or game library, just the settings. From there, use the Safe One config from the Starter Configs section below as your new baseline and only add things back one at a time.
The game looks broken after I turned on PGXP
Start by turning off PGXP Depth Buffer specifically. DuckStation rates it as low compatibility and it is the most common PGXP-related cause of broken visuals. Keep Geometry Correction on if it was helping with the wobble before this started, but get Depth Buffer off first and see if that clears it up. If the game is still misbehaving, disable all PGXP for that title and accept the wobbly polygons for now.
I turned on Multi-Sampling and now things look broken
This is not a bug and you cannot configure your way around it for that game. DuckStation's own tooltip says MSAA often introduces rendering errors, and it genuinely means it. Turn it back off and everything returns to normal. Some games just cannot handle it.
The game slowed down after I made it look nicer
Lower Internal Resolution back to 1x first, because higher resolutions require significantly more GPU power on every frame. If you have PGXP CPU Mode on, turn that off since DuckStation flags it as having a high performance cost. Also check how many Post-Processing shaders are stacked up, because each one adds GPU work on top of everything else.
Textures are stuttering or not loading with a replacement pack
Enable Preload Texture Replacements so the whole pack loads into RAM at startup instead of being fetched on the fly during gameplay. If you are seeing actual rendering glitches beyond the stuttering, the more likely cause is the Texture Cache not being compatible with that game, and turning it off entirely is the cleanest fix until you can confirm support.
OBS or capture software cannot see the game on Windows
Go to Settings → Graphics → Advanced and enable Use Blit Swap Chain. DuckStation notes it is usually slower than the default, but it is the correct fix for streaming and capture compatibility issues on Windows. This option only appears on Windows, so you will not see it on other platforms.
I just want to check if the game is running at full speed
Go to Settings → On-Screen Display and enable Show FPS and Show Emulation Speed. Full speed is 100% and either 60 FPS for NTSC or 50 FPS for PAL. Once you have confirmed everything looks good, turn both back off.
DuckStation Best Settings: Three Starter Configs
Pick whichever one matches where you are at. These are not gospel, they are just sensible starting points built around what DuckStation's own documentation and warnings actually recommend.
Renderer on Automatic, Internal Resolution at 1x, Multi-Sampling Disabled, PGXP Depth Buffer off, Threaded Rendering on, everything else at default. This is the "I just want to play the game and not think about any of this" preset. Nothing fancy, nothing risky, and if anything breaks you will know it was something you did after reading this and not one of these settings.
Raise Internal Resolution to 2x or 3x depending on how your hardware handles it. Set Texture Filtering to taste, Nearest if you want the authentic pixel look, a smooth option if you prefer cleaner surfaces. Turn on PGXP Geometry Correction if the wobbly 3D is bothering you, and keep Perspective Correct Textures and Culling Correction on alongside it since they are there to catch the problems PGXP can introduce. PGXP Depth Buffer stays off. Multi-Sampling stays off. This is most of the visual benefit with almost none of the risk.
Internal Resolution back to 1x. PGXP CPU Mode off. Threaded Rendering on. All Post-Processing shaders gone. Strip it all back until the game runs smoothly and then, if you want, add things back in one at a time. It is always easier to build up from working than to debug down from broken.
The Short Version
Automatic renderer. Threaded Rendering on. Everything experimental off.
Turn on PGXP Geometry Correction if 3D looks wobbly. Raise Internal Resolution if your machine can handle it. Leave Multi-Sampling and PGXP Depth Buffer alone.
The rest of the guide is there for when something breaks or you want to push things further. But a lot of people open DuckStation, change nothing, and have a perfectly good time. The defaults are not bad. You do not have to earn it.
Based on DuckStation's Qt source code and official tooltips as of March 2026. DuckStation ships rolling releases and settings can shift between builds. If something looks different on your version, that is most likely why. When anything seems off, Reset to Default is your friend.
No comments:
Post a Comment