Turn Foliage Quality down in Squad and you will see enemies you couldn’t before. That part isn’t in dispute — players have argued about it since 2018 [7]. What most settings guides get wrong is treating every graphics option the same way, as if Offworld Industries (OWI) just left the whole menu open for anyone to abuse. It didn’t. The Field of View slider has a hard floor at 90 specifically because a lower FOV works like a free zoom [4], and Bloom has been forced on since an early patch specifically to kill a fog-brightness exploit. Foliage never got the same treatment. That difference — what’s locked, what isn’t, and why — is the actual story, and it’s one no other Squad settings guide tells.
Quick Start: The 6 Settings That Actually Move the Needle
Do these first, in this order, before touching anything else in the menu:
- Foliage Quality → Low. Biggest FPS win in the whole menu and the only setting on this list that also changes what you can see [6][8].
- Shadow Quality → Low or Off. Removes dark hiding spots along tree lines and building interiors, second only to Foliage for a free spotting edge [6].
- View Distance Quality → Medium. The heaviest setting in the game and the one most tied to your CPU, not your GPU [8]. Don’t drop it to Low — you’ll start losing vehicles and infantry at genuinely useful spotting ranges.
- Post-Process Quality → Low. Strips bloom intensity, depth of field and screen-space sharpening — a clean FPS win with no spotting downside. Players consistently report it costing the most once a fight has several simultaneous explosions and smoke grenades on screen, which is exactly what a full 100-player push looks like.
- Motion Blur → Off. Stops moving targets from smearing when you track them [6].
- Field of View → 95–100. This is as low as the engine allows you to help yourself — the floor is 90 — so push it toward the wide end for peripheral spotting instead [4][5].
Why Most Squad Settings Guides Are Already Stale
Squad rebuilt itself on Unreal Engine 5.5 in the V9.0 update (September 4, 2025), adopting Nanite, Chaos Physics and a new Global Illumination system that OWI says was built specifically “to ensure greater consistency across all levels” [2]. V10.0 followed two months later (November 12, 2025) with a targeted fix: “improved memory usage on foliage-heavy maps” [3]. That second note matters more than it sounds — foliage rendering is exactly the system every spotting-advantage debate in this article revolves around, and it changed twice in the three months before this guide was written. Any settings guide still recommending DirectX 11 or describing pre-Nanite foliage behavior is describing a game that no longer exists. Verify your own build against V10.x before trusting anything below; OWI ships graphics-relevant patches often enough that a year-old guide is a real liability here, not just a formality.
The Settings OWI Won’t Let You Break
Most competitive shooters let you set everything to zero if your hardware can take it. Squad doesn’t, and it’s worth knowing which floors are load-bearing so you stop hunting for a workaround that doesn’t exist.
Field of View has a hard floor of 90. Players who’ve tried to push it lower through the config files report the game simply won’t launch below that value [4] — because a narrower FOV makes distant targets render larger on screen, functioning as unscoped magnification. In most shooters, a low FOV is a playstyle choice. In Squad, the working community explanation is that OWI locked the slider because a narrower FOV was close enough to unscoped magnification to count as an exploit.
Bloom can’t be fully disabled. According to Squad’s community-compiled patch history, an early update forced Bloom on and replaced the old Gamma slider with a Brightness slider for the same reason: both were being used to wash out or darken atmospheric fog and see further than the map’s lighting was supposed to allow. Treat the exact patch version as unconfirmed — the mechanism is well established in long-running player discussion even if the precise changelog wording isn’t independently verifiable — but the practical result holds today: you can lower Bloom’s intensity in Post-Processing, you can’t remove it.
Neither fix touched Foliage Quality, which is why it’s still the one setting on this page that behaves differently from everything else.
Foliage and Shadows: The Trade Nobody’s Patched Out
Lowering Foliage Quality in Squad is not a straight FPS-for-clarity trade — it’s closer to a free win on both axes, and that’s exactly why it’s controversial. Thinner grass and fewer bushes mean fewer polygons for your GPU to draw, and it means the vegetation that used to hide a prone rifleman in a treeline no longer does [6][7]. Shadow Quality works the same way: dropping it to Low removes the dark patches under trees and inside doorways where players sit still, on top of the FPS it frees up [6]. Some players call this cheating in spirit even though it’s inside the settings menu; others point out it’s the same LOD/render-distance behavior every large-scale Unreal Engine shooter has struggled with, not a Squad-specific hole [7]. Either way, it’s legal, it’s inside the menu OWI shipped, and every other current guide recommends it — so the honest framing isn’t “should you,” it’s “understand that this is the one setting on the list that isn’t just about frames.”
The Full Settings Breakdown
| Setting | Recommended | FPS Impact | Changes Spotting? | Locked by OWI? |
|---|---|---|---|---|
| Foliage Quality | Low | High | Yes — real advantage | No |
| Shadow Quality | Low/Off | Medium–High | Yes — removes dark hiding spots | No |
| View Distance Quality | Medium | High (CPU-leaning) | Costs you long-range spotting if set too low | No, but has a real downside |
| Post-Process Quality | Low | Medium–High on full servers | No meaningful change | Partial — Bloom floor |
| Ambient Occlusion | Off (PvP) / On (screenshots) | Low–Medium | Minor — removes some corner shadow | No |
| Motion Blur | Off | Low | No, but improves tracking | No |
| Texture Quality | Medium | Low (mostly VRAM) | No | No |
| Effects/Particle Quality | Medium | High in firefights (smoke) | No | No |
| Field of View | 95–100 | None | Yes — peripheral spotting | Yes — floor of 90 |
Sourced and cross-checked from current 2026 optimization guides [5][6][8] against OWI’s own V9.0/V10.0 patch notes [2][3] — not recycled from pre-Unreal-Engine-5 recommendations.
Which Settings Actually Matter on a Full 100-Player Server
The setting priority above changes once a server actually fills to 100 players, because the bottleneck shifts. Use this to decide where to spend your next tuning pass:
- If your FPS tanks specifically during big infantry pushes or vehicle columns — not just in general — you’re CPU-bound. Squad leans hard on single-core performance to simulate that many players and vehicles at once [9], and no GPU-side setting fixes that. Lower Effects/Particle Quality (smoke and explosions are the worst offenders [8]) and check you’re not running background overlays eating CPU cycles.
- If your FPS is low everywhere, not just in big fights — you’re GPU-bound. Work through Foliage, Shadows, View Distance and Post-Process in that order; those four give you the most frames per setting dropped [5][6][8].
- If frame times feel inconsistent even when the average FPS looks fine — that’s the frame-pacing behavior V9.0’s Unreal Engine 5 move specifically targeted [2]; make sure you’re actually on a current build before chasing settings fixes for a bug that may already be patched.
What to Prioritize by Player Type
| Player Type | Priority |
|---|---|
| New to Squad, older hardware | Run the Quick Start list as-is. Don’t chase every FPS point yet — learn the maps and squad comms first; the settings will still be here. |
| Budget/older GPU, want stable 60 FPS | Foliage and Shadows first, then View Distance to Low if you’re still short. Accept the spotting-range cost on View Distance — a stable frame rate beats occasional long-range kills you’d otherwise miss anyway. |
| Competitive optimizer chasing every edge | Full Quick Start list plus FOV at 100, then move on to polling rate and DPI and sensitivity — in a game this CPU-bound, your input chain matters as much as your graphics settings once FPS is already stable. |
| Squad Leader / vehicle crew | Keep View Distance at Medium minimum — you’re the one calling contacts and driving at range, and a low View Distance setting costs your whole squad more than it costs a rifleman. |
FOV Interacts With Your Mouse Settings — Get It Right First
FOV sits in Squad’s video settings alongside Foliage and Shadow Quality, not tucked away in Controls, which is easy to miss the first time you go looking for it. That placement matters more than it seems: a wider FOV shrinks how far your mouse has to travel to track a target across the screen, which is a different effect from raw DPI and in-game sensitivity, and a different effect again from your mouse’s polling rate, which governs how often your input chain reports position at all rather than how far it has to move. Set FOV first — it’s free, it costs no FPS, and it changes what the other two settings are even correcting for. Only tune DPI, sensitivity and polling rate once your FOV is locked in.
If this is your first pass at tuning a game’s settings from scratch rather than just copying a list, our full PC game settings optimization guide covers the general framework — driver updates, Windows power plans, and how to read your own FPS counter — that underpins everything in this article.
FAQ
Is lowering Foliage Quality in Squad actually cheating?
Not by the game’s own rules — it’s a setting in the official menu, and OWI has had years to lock it the way it locked FOV and Bloom and hasn’t. But it’s the one setting here that genuinely changes what you can see rather than just how fast the game runs, which is why it still gets argued about in Squad’s Steam forums years after launch [7]. If you’re not comfortable with that gray area, that’s a legitimate reason to leave Foliage on a higher setting — it’s not required to run well.
Why does Squad still stutter on a good GPU?
Because Squad’s big-battle performance is mostly a CPU problem, not a GPU one — 100 simultaneous players, vehicles and networked hit registration lean on single-core throughput that no amount of GPU headroom fixes [9]. If you’re on a strong GPU and still seeing drops specifically when the server is full, that’s the signal to look at your CPU and background processes, not your graphics settings.
Should I drop View Distance to Low for the FPS boost?
Only if you’ve already exhausted Foliage, Shadows and Post-Process first. View Distance is genuinely the heaviest single setting in the menu [8], but unlike Foliage it has a real downside — you’ll start losing vehicles and distant infantry at ranges where seeing them first actually matters in a game built around long sightlines. Medium is the honest floor for anyone who plays a spotting or marksman role.
Foliage Quality to Low. It’s the largest FPS gain on the list, it requires no hardware upgrade, and it’s the one change every current guide agrees on — including this one [5][6][8].
Key Takeaways
- Foliage Quality → Low is the single highest-value change: biggest FPS win and the only setting that meaningfully changes what you can see.
- FOV is floored at 90 and Bloom can’t be fully disabled — OWI already closed those two exploits, so don’t waste time hunting for a config workaround.
- View Distance is the heaviest setting overall, but drop it past Medium and you start losing the long-range spotting Squad is built around.
- On a full 100-player server, the bottleneck during big fights is usually your CPU, not your graphics settings.
- Verify you’re on Squad V10.x before trusting any settings guide, this one included — the September and November 2025 Unreal Engine 5 updates changed foliage rendering twice in three months.
Sources
- [1] Squad on Steam — Offworld Industries, official store page and system requirements
- [2] Squad 9.0 Release Notes — Offworld Industries, official
- [3] Squad 10.0 Patch Notes — Offworld Industries, official
- [4] Squad Steam Community — FOV settings discussion
- [5] Reality Remake Gaming — Squad Best Settings Guide
- [6] SettingsFor.Games — Best Squad Settings & Graphics Configs
- [7] Squad Steam Community — foliage/visibility discussion
- [8] TheFrameCoach — Best Squad Settings for RTX 3060 Laptop (2026)
- [9] Squad Steam Community — CPU vs GPU intensity discussion
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.