Your Manor Lords settings menu isn’t lying to you, but it also isn’t telling you the whole story. Drop your shadows to Medium and you’ll pick up a few frames. Grow your town past 200-300 population and you can lose 50+ FPS no matter what you touch in that menu — because the real bottleneck by then isn’t your GPU, it’s your CPU trying to path hundreds of villagers through a live simulation. This guide covers both problems: the graphics settings that genuinely move the needle, and the population-driven stutter that settings alone can’t fix. Verified on version 0.8.090–0.8.104 (Update 8, main branch since August 27, 2026).
Quick Start: Do This First
Before touching individual sliders, run through this five-step baseline — it fixes most FPS complaints in under five minutes:
- Set Display Mode to Fullscreen (not Windowed or Borderless) — Manor Lords hands off more scheduling to the GPU this way.
- Turn Anti-Aliasing to DLSS or FSR on Quality instead of TAA — this is the single biggest FPS swing in the settings menu, confirmed across every source in this guide.
- Set VSync Off and Max Framerate to Unlimited, then cap frames at the driver level instead (see the VSync section below for why).
- Update your GPU driver — both Nvidia and AMD have shipped Manor Lords-specific game-ready drivers since launch.
- If you’re past 150-200 population and still stuttering, skip ahead to “When Settings Alone Aren’t Enough” — you’re hitting a simulation bottleneck, not a graphics one.
If you haven’t touched your Windows power plan, background apps, or driver settings at all yet, start with our general guide to optimizing a PC for better FPS — the steps here assume that baseline is already in place.
Why Manor Lords Stutters More Than Your Hardware Suggests It Should
Manor Lords is CPU-bound, not GPU-bound, once a settlement grows — every villager, ox, and cart is an individual agent pathfinding through a live road and terrain network. Steam Community reports document the pattern clearly: one player on an RX 7900 XTX and i5-13600K — hardware that should never choke on a city-builder — watched FPS fall from 90-144 at the start of a save to roughly 40 at 200 population, then below 5 FPS with regular freezes past that point [3]. That’s not a settings problem; it’s a scaling problem, and no amount of lowering Shadow Quality touches it. If you want a deeper breakdown of what CPU-bound actually means for frame rate, see our CPU bottleneck explainer.
Developer Slavic Magic has been chipping away at this all year. An early memory leak that made the drop-off worse was patched out in 2026. The March 2026 beta (v0.8.065) began what the developer’s own patch notes call “a pathfinding refactor that’s still ongoing,” fixing workers who got stuck on obstacles and a bug where bandit-squad detection alone could cause stutters [5][6]. That refactor culminated in July 2026’s Update 7, which overhauled the pathfinding system end to end — adding island detection to block impossible routes and delivering, per the developer, “faster AI calculations, lower memory usage, reduced interface stuttering, and more efficient animation and harvest calculations” [7]. One trade-off: max game speed is now capped at 8x, down from unlimited, because the more precise simulation costs more to run at extreme speeds.
Update 8 (v0.8.090-0.8.104, main branch since August 27, 2026) layered in further pathfinding and save/load fixes alongside its new Wide Valley map and livestock systems [8]. Based on the combined scope of the memory-leak fix, the pathfinding refactor, and Update 7’s AI/memory work, a settlement that used to chug into the teens by 300 population should hold noticeably steadier frame times on the current build than it did at launch — better, not solved. If you played at launch and gave up on a big settlement, it’s worth another look now.
Best Manor Lords Graphics Settings
These are the settings worth changing, ranked by how much FPS they actually buy you versus how much visual quality you give up. Values are drawn from testing across multiple independent benchmarks on RTX 3090 and RTX 3070 rigs [1][2].
| Setting | Recommended | Priority | Why |
|---|---|---|---|
| Anti-Aliasing | DLSS/FSR Quality | Highest | Biggest single FPS gain of any setting; TAA costs the most for the least visual benefit |
| Shadow Quality | Medium-High | High | Ultra shadows cost several FPS for a difference you won’t notice at normal camera height |
| View Distance | Medium | High | Renders less terrain and fewer distant objects at once — a real FPS cost at Ultra for a modest visual trade at Medium |
| Grass Density & Distance | Medium | Medium | Noticeable FPS cost on Ultra with minimal visual payoff beyond Medium |
| Volumetric Clouds | Off (or On if you screenshot skies) | Low | Cheap to disable, purely cosmetic |
| Shader Quality | High | Low | Small FPS cost at High vs. Ultra; keep it high, it’s not where your budget goes |
| Postprocess Quality | Medium-High | Low | Minimal FPS difference across the whole range per independent testing |
| Terrain Texture Resolution | High | Low | VRAM cost more than FPS cost — safe to leave high on any GPU with 6GB+ |
The takeaway: upscaling (DLSS/FSR) and Shadow/View Distance are where your FPS budget actually goes. Everything below Medium priority in that table is a rounding error next to those three.
The VSync Contradiction (And What to Actually Use)
Independent testing disagrees with itself here: PC Guide’s benchmarking recommends VSync Off with an uncapped frame rate for maximum FPS headroom [1], while PCGamesN’s own settings guide recommends VSync On with a 120 FPS cap, and hit a stable 120 FPS at 1080p and 1440p doing it [2]. Both are right for different setups — the contradiction is really a monitor question, not a settings question:
- You have G-Sync or FreeSync: VSync Off, uncapped framerate, let the monitor’s variable refresh handle tearing. This is the setup PC Guide tested on.
- You don’t have adaptive sync and see screen tearing: VSync On with a frame cap at your monitor’s refresh rate (PCGamesN’s approach) trades a small amount of input latency for a tear-free image — reasonable for a slow-paced city builder where latency barely matters.
- You’re chasing max raw FPS for a low-end GPU: VSync Off, uncapped — a capped frame rate only helps once you’re already hitting your target consistently.
Not sure which camp you’re in generally, not just for this game? Our VSync on-or-off breakdown covers the underlying logic in more detail.
Settings by Player Type
Manor Lords’ official minimum spec is a GTX 1050 / RX 460 with 8GB RAM; recommended is a GTX 1060 / RX 580 with 12GB [4]. What “best settings” means changes a lot depending on which side of that line you’re on:
| Player type | Priority | What to do |
|---|---|---|
| Budget/low-end PC (near minimum spec) | Playability over polish | FSR Performance (not Quality), everything else Low-Medium, View Distance Medium. Expect population growth to hit you earlier than higher-end rigs — plan smaller settlements. |
| Mainstream 1080p/1440p PC (RTX 3060-4070 class) | Balance | Use the graphics table above as-is. You’ll comfortably hold 60+ FPS until population-driven stutter, not your settings, becomes the limiter. |
| High-end / large-settlement optimizer (RTX 4070 Ti+) | Simulation headroom, not visuals | Your GPU has margin to spare; the setting that actually matters to you is Max Game Speed (capped at 8x since Update 7) and keeping your save file lean, since your bottleneck is CPU simulation load, not rendering. |
When Settings Alone Aren’t Enough: The Population Milestone Framework
Because the late-game bottleneck is CPU simulation rather than rendering, think of your settlement in population brackets rather than treating “optimize my settings” as a one-time task:
- Under 150 population: Any reasonable settings combination runs well on recommended-spec hardware. Optimize for looks here.
- 150-400 population: This is where the pathfinding cost starts compounding. Apply the graphics table above, keep View Distance at Medium, and avoid packing too many production buildings into one dense district — shorter average pathing distances measurably reduce agent-count stress.
- 400+ population: You’re now testing the current patch’s actual ceiling, not your PC’s. Lowering settings further buys little; the meaningful levers are staying on the current build (Update 8 or later) and accepting that very large settlements are still a soft cap the developer is actively working against, not a solved problem.
This is the piece most settings guides skip: no combination of sliders turns a CPU-bound simulation bottleneck into a GPU-bound one. Knowing which bracket you’re in tells you whether to keep tweaking settings or just wait on the next patch.
Frequently Asked Questions
Should I lower my resolution instead of individual settings for more FPS?
Only as a last resort. Manor Lords’ upscaling implementation (DLSS/FSR Quality) recovers most of the FPS you’d gain from a lower native resolution while keeping image clarity much closer to native — dropping resolution directly loses more visual quality per FPS gained than upscaling does, based on the benchmark deltas in the settings table above [1][2].
Will a better GPU fix my late-game stutter?
Not by itself, and this is the most common mistake in the community threads on this issue. If your stutter appears specifically as your population crosses 150-200, you’re CPU-bound on simulation and pathfinding, not GPU-bound on rendering [3]. A faster single-core CPU helps meaningfully; a new GPU mostly doesn’t, since the graphics settings table above already accounts for what your GPU controls.
Is it worth reinstalling or restarting a save on the current patch?
If you abandoned a large settlement before July 2026’s Update 7 pathfinding overhaul, it’s worth testing your old save again before starting fresh — the changes to AI calculation speed and memory usage apply to existing saves, not just new ones [7][8]. A fresh start only helps if your specific save file has accumulated corruption, which is a separate (rarer) issue from general population-scaling stutter.
Sources
- PC Guide. Best Settings for Manor Lords — Our Test Results and Recommendations
- PCGamesN. Best Manor Lords Settings for Max FPS
- Steam Community. Significant FPS Drop After 200 Population — Manor Lords Gameplay Discussions. Valve
- Steam. Manor Lords System Requirements. Valve
- xpgained. Manor Lords Beta 0.8.065 Patch Notes (17th March 2026)
- PatchBot. Manor Lords Patch Notes Feed (mirrors official Slavic Magic / Hooded Horse announcements)
- Simulation Daily. Manor Lords Update 7 Overhauls Pathfinding, AI & Squad Controls
- Simulation Daily. Manor Lords Update 8 Adds New Map, Livestock, Construction Mechanics, & More
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.