The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
There is no single best Enshrouded preset for every PC. The reliable approach is to establish a repeatable baseline in your own game build, identify whether the scene is GPU-limited, and change one setting at a time while checking both frame stability and image quality.
The currently documented settings guidance covers PC version 0.9.1.2, checked October 10, 2026. Steam had Enshrouded in Early Access at the October 13 research timestamp and listed October 15, 2026 as the planned exit date, so verify the options in your installed post-update build before treating any recommendation as final.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Games Workshop - Warhammer 40,000 - Craftworlds Spiritseer | $29.75 | Buy on Amazon |
What “best settings” means in Enshrouded
Enshrouded workloads vary dramatically between a quiet outdoor clearing, a dense settlement, a large voxel construction, and a fog-heavy area. A setting that helps one view may do little in another, and a change that raises average FPS can still make frame delivery feel worse if it introduces stutter or unstable frame times.
Use “best” to mean the highest image quality that keeps your target frame rate or frame-time consistency in the scenes you actually play. That target depends on your GPU, CPU, memory, display resolution, refresh rate, driver, game build, and whether you play solo or in a hosted co-op world.
#1 Best Overall
- Games Workshop - Warhammer 40,000 - Craftworlds Spiritseer
- Plastic multipart miniatures - assembly required - tools, paints and glue not included
- Games Workshop
The most defensible current guidance is based on version 0.9.1.2, not a universal benchmark. No independent hardware test establishes one preset or a guaranteed percentage improvement for every system. Treat the setting suggestions below as controlled test candidates and keep a change only when the improvement repeats in your own game.
Check your hardware against the published requirements
Steam’s published requirements identify hardware tiers, but they do not promise smooth performance at a particular resolution, preset, or frame rate. An SSD is recommended, and 16 GB of RAM appears at both the minimum and recommended tiers.
| Tier | GPU listed by Steam | Memory | Storage note | What the tier does not guarantee |
|---|---|---|---|---|
| Minimum | NVIDIA GeForce GTX 1060 6GB, AMD Radeon RX 580 6GB, or Intel Arc A380 | 16 GB RAM | SSD recommended | A fixed resolution, preset, FPS, or frame-time target |
| Recommended | NVIDIA GeForce RTX 2070 Super, AMD Radeon RX 6700 XT, or Intel Arc A770 | 16 GB RAM | SSD recommended | A guarantee of smooth play in every scene or multiplayer world |
If your graphics card is below the published recommended tier, test and tune your current hardware first. Buying a card equivalent to the recommended tier is not required, and the published list does not establish a specific performance result for that upgrade.
Establish a repeatable baseline before changing anything
Randomly switching presets makes it impossible to tell which option helped. Build a small repeatable test instead.
- Record the build and system. Note the game version shown by your installation, CPU, GPU, installed RAM, graphics driver, display resolution, refresh rate, and whether you are playing solo or in co-op.
- Choose one representative scene. Use a recognizable route and repeat the same camera movement. A quiet clearing is useful for outdoor rendering; a busy settlement or large build is more useful for testing geometry, shadows, and frame pacing under load.
- Keep the conditions constant. Use the same resolution, graphics options, route, camera direction, activity, and session type for every comparison. Do not compare a quiet clearing with a settlement and attribute the difference to one setting.
- Record frame rate and frame time. Average FPS is useful, but note hitching, one-percent-low behavior if your overlay provides it, and whether camera movement feels consistent. A higher average with severe spikes is not automatically better.
- Capture visual references. Look at foliage edges, distant structures, shadow transitions, reflective surfaces, fog boundaries, and fine geometry. A setting change is worthwhile only when its visual cost is acceptable in the scene you care about.
Find out whether the scene is GPU-limited
Before reducing image quality, perform a simple resolution test in the same scene. Lower the resolution by one available step, repeat the same route and camera movement, and compare frame rate and frame time.
- Consistent improvement after lowering resolution: the tested scene is likely limited by graphics work on the GPU. Restore the original resolution and test the individual options that dominate what you see.
- Little or no change: lowering resolution did not remove the main bottleneck. Restore it and investigate a frame cap, CPU workload, memory pressure, background applications, or multiplayer/server behavior instead of blindly lowering every quality option.
This is a diagnostic clue, not a universal utilization cutoff. A scene can change bottlenecks as you move from open terrain to a settlement, and a multiplayer session can add delay that graphics settings cannot fix.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Which settings to test first
There is no verified universal ranking, but the following matches the visible workload in the scene. Change one item, repeat the baseline route, and keep it only if the result is repeatable.
| What dominates your view | First setting to test | What to inspect after the change | Likely trade-off |
|---|---|---|---|
| Large, complex shadows | Shadow Quality | Shadow stability, contact detail, and frame-time spikes while moving | Softer or less detailed shadows at lower values |
| Heavy indirect or global lighting | Indirect Lighting | Interior and outdoor light bounce, dark areas, and frame pacing | Less convincing bounced light and darker or flatter scenes |
| Water, glass, or other reflective surfaces | Reflections | Reflection clarity and stability near the surface that caused the slowdown | Less detailed or noisier reflections |
| Dense fog or atmospheric effects | Fog Quality | Fog boundaries, volumetric detail, and consistency during movement | Reduced depth and atmospheric detail |
| Grass and small plants fill the screen | Small Foliage | Nearby vegetation density, shimmer, and draw distance | Thinner or shorter-looking small vegetation |
| Distant terrain, structures, or a large build | Distant Objects or Voxel Mesh Quality | Pop-in, distant silhouettes, and detail on voxel buildings | Lower detail or more visible transitions at distance |
These are targeted experiments, not instructions to lower every option. If shadows are not visible in your problem scene, lowering Shadow Quality may produce little benefit while needlessly reducing image quality elsewhere.
Recommended tuning order for a quality-first setup
Start from the visual quality you want, then reduce only the option that corresponds to the measured bottleneck.
- Set your native display resolution. Use the panel’s native resolution for the first comparison so you can judge image quality without an upscaler masking the result.
- Run the baseline route. Record frame rate, frame-time behavior, and the visual details that matter most in your play area.
- Test Shadow Quality or Indirect Lighting. Choose the one that dominates the view. Repeat the route and check both movement smoothness and shadow or lighting detail.
- Test Reflections, Fog Quality, Small Foliage, Distant Objects, or Voxel Mesh Quality only when relevant. Pick the setting matching the visible workload rather than changing several categories together.
- Restore any change that does not repeat. If the gain appears only once, or the visual loss is more distracting than the improvement, return to the previous value.
- Only then test an upscaler. Compare native rendering with one mode exposed by your installed build, using the same scene and target resolution.
Native rendering versus upscaling
Upscaling renders internally at a lower resolution and reconstructs the output for your display. It can improve performance in a GPU-limited scene, but it may also introduce blur, shimmering, ghosting, or unstable fine detail. Judge those artifacts while moving, not only from a still screenshot.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
FSR options
Keen Games’ Update #3 replaced FSR 2 with FSR 3 and also changed other performance behavior. The exact modes exposed by the current installation depend on the game build and hardware, so open the graphics menu and use the labels that are actually present rather than assuming an older guide’s choices remain available.
DLSS options
NVIDIA documented DLSS 2 support for Enshrouded at launch. That does not establish that every current GPU or game build exposes the same mode, nor does it guarantee the same result at every resolution. If DLSS appears in your menu, compare it directly with native rendering in the same scene and inspect foliage, distant edges, and movement for artifacts.
Frame-generation expectations
Do not assume that an upscaler label implies frame generation. Availability is determined by the installed build and GPU. Verify the menu, then test frame-time consistency and input feel rather than judging only the displayed FPS number.
NVIDIA’s 2024 driver announcement claimed that “Enshrouded is available now and GeForce RTX gamers can activate DLSS 2 to accelerate frame rates by 93% on average at 4K, with max settings enabled.” This is a vendor-reported result, not an independent benchmark or a prediction for every GPU, DLSS mode, resolution, or game scene.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchHow to compare upscalers without fooling yourself
- Keep the display resolution, graphics settings, route, camera movement, and game session identical.
- Record a native-rendering run first.
- Enable one upscaler mode that your menu provides and repeat the run.
- Compare average FPS and frame-time stability, then inspect thin foliage, diagonal edges, distant structures, reflective surfaces, and fog.
- Keep the mode only if the performance gain remains stable and its artifacts are acceptable at your normal viewing distance.
Testing one mode at a time matters because changing an upscaler and several quality settings together hides which adjustment caused a gain or a visual defect.
Fix common performance problems by symptom
Low FPS in a visually busy scene
Repeat the resolution test. If lowering resolution helps, test the scene-relevant quality option: shadows or indirect lighting for lighting-heavy views, reflections near reflective surfaces, fog in atmospheric areas, foliage among vegetation, and distant-object or voxel-mesh quality when geometry fills the view. An upscaler can be tested after those individual changes.
Stutter despite an acceptable average FPS
Watch frame time rather than the average alone. Repeat the same route after each single-setting change. A setting that raises the average but creates spikes is a poor trade for a stable experience. A frame cap can be a useful diagnostic or pacing choice when your system cannot hold the display refresh rate consistently, but the supplied evidence does not establish one universal cap value.
Lowering resolution changes almost nothing
Restore native resolution and look beyond GPU quality settings. CPU limits, memory pressure, background tasks, streaming or storage behavior, and multiplayer hosting can dominate a particular scene. The resolution test only identifies whether the tested workload responds to fewer pixels; it cannot diagnose every cause by itself.
Blurry or shimmering image after enabling an upscaler
Compare native rendering and the selected mode while moving through foliage and past distant geometry. If the artifact is distracting at your normal distance, use a higher-quality mode, native rendering, or a different exposed option, accepting the corresponding performance cost. Do not treat a nominal FPS increase as a win if the image is no longer readable.
Smooth local movement but delayed co-op actions
If your character and camera move smoothly while shared actions or world changes arrive late, the symptom points away from a local rendering bottleneck. Investigate connection and hosting conditions before lowering graphics settings. The symptom does not identify one universal network cause, but reducing visual quality will not normally correct a delay that occurs after an action is sent to the shared world.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What changed in recent Enshrouded updates
Older settings articles can be useful for ideas, but update history makes their exact recommendations unreliable. Keen Games’ Update #3 reported improved stability and performance on lower hardware and Steam Deck, updated default Steam Deck settings, replaced FSR 2 with FSR 3, improved global illumination, and fixed freezes on faster graphics cards. Update #8 reported improved vegetation rendering, faster dynamic global illumination, reduced game RAM usage, and better detail on voxel buildings at medium graphics settings.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesThose changes can alter both the cost and appearance of a setting. A recommendation that was sensible before an update may no longer be the best trade-off in the current renderer. Record the build whenever you retest, especially after a major update.
Steam Deck and lower-end systems
Update #3 specifically mentioned lower-hardware and Steam Deck performance work and updated default Steam Deck settings. That is evidence of optimization work, not a universal frame-rate promise. On a lower-power device, prioritize a stable frame time over maximum distant detail, and use the same repeatable route to decide whether a change helps. Verify the options and defaults in the installed build because the renderer and menu may have changed since the documented version.
Why a universal preset is misleading
- Hardware differs: the same preset can be GPU-limited on one PC and CPU-limited on another.
- Resolution differs: a 4K workload has a very different pixel cost from 1080p.
- Scenes differ: foliage, fog, reflections, settlements, and large voxel builds stress different systems.
- Builds differ: updates have changed upscaling, lighting, vegetation, memory use, and defaults.
- Players value different details: one player may tolerate lower foliage density while another will accept lower reflections to preserve vegetation.
For those reasons, a universal “turn these five options to medium” list is less useful than a controlled decision process that identifies your bottleneck.
A practical decision checklist
- Confirm the installed build and note your hardware, driver, resolution, and play mode.
- Choose one repeatable route in the scene that actually causes the problem.
- Run the resolution test to determine whether the scene responds to lower pixel load.
- If it does, select the quality option that matches the dominant visual workload.
- Change exactly one option and repeat the route.
- Record frame rate, frame-time behavior, and the specific visual detail affected.
- Restore changes that do not repeat or that make the image unacceptable.
- Test native rendering against one upscaler mode available in your current menu.
- Separate local rendering smoothness from co-op delay before changing graphics settings for a network symptom.
- Retest after major patches and after the Early Access transition because the documented guidance is pre-1.0.
Version and evidence limits to keep in mind
The documented guide was checked October 10, 2026 against PC version 0.9.1.2. Steam’s October 13 listing still described Enshrouded as Early Access and planned an October 15 exit date; the post-1.0 settings menu and renderer behavior were not established in the available evidence. If your installation is newer, treat every option name and default as something to verify in-game.
Steam’s hardware figures are requirement tiers, not performance guarantees. The official update notes establish changes to rendering and performance, while the DLSS figure is a vendor claim. No first-hand gameplay test or independent benchmark supports a universal FPS gain, so use your own repeatable scene to make the final choice.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
