Best Enshrouded Settings for FPS and 1.0 Performance Guide

Improve Enshrouded FPS with a repeatable settings workflow, current PC requirements, Steam Deck guidance, stutter diagnosis, and a 1.0 launch checklist.

Last updated: 2026-08-21

The best Enshrouded settings depend on whether the GPU, CPU, VRAM, or world simulation is limiting performance. Start from a preset, measure the same scene, and change one category at a time. Copying an unexplained screenshot from different hardware is less reliable than this controlled process.

This guide covers the current v0.9.1.2 build. Keen Games has confirmed more optimization information for 1.0, but final launch requirements and performance targets have not yet been published.

Current PC system requirements

Component	Minimum	Recommended
OS	Windows 10 64-bit	Windows 10 64-bit
CPU	Intel Core i5-6400 or Ryzen 5 1500X	Intel Core i7-8700 or Ryzen 7 2700X
Memory	16 GB RAM	16 GB RAM
GPU	GTX 1060 6 GB, RX 580 6 GB, or Arc A380	RTX 2070 Super 6 GB, RX 6700 XT 6 GB, or Arc A770
Storage	60 GB available	60 GB available; SSD recommended

These are the currently published Steam requirements, not guaranteed 1.0 specifications.

Recommended starting profiles

Hardware position	Starting point	Initial target
Near minimum	Low preset, native 1080p or quality upscaling below it	Stable 30 FPS
Between minimum and recommended	Medium preset with quality upscaling	Stable 45–60 FPS
Recommended GPU	Medium or high preset, then tune shadows and global lighting	Stable 60 FPS
High-resolution display	Quality upscaling before reducing every texture	Stable frame time at the chosen refresh target

Treat these as test points, not promised benchmarks. Large bases, dense vegetation, multiplayer activity, water simulation, and new regions can produce different loads.

Best optimization order

Choose the target first. Cap to a frame rate the system can sustain instead of oscillating between a high maximum and visible drops.
Use the available quality upscaler. DLSS, FSR, or the supported alternative can reduce GPU load while preserving a clearer image than lowering every setting.
Reduce shadow quality. Shadows commonly affect both GPU time and scene complexity.
Reduce global illumination or indirect-lighting quality. The current renderer uses dynamic global illumination, and Keen specifically optimized it in Update 8.
Reduce vegetation and distance-related detail. This is especially useful in dense Revelwood areas and when looking across large terrain.
Reduce effects and volumetric quality. Test inside the Shroud and during combat, not only at an empty base.
Lower resolution or use a more aggressive upscaler mode last. This provides a large GPU saving but costs image clarity.

Keep texture quality within available VRAM. Lowering textures may reduce VRAM pressure and hitching, but it usually does less for raw FPS when the GPU is limited by lighting or resolution.

How to benchmark correctly

Use a repeatable 60-second route:

Restart the game after a driver or major graphics change.
Load the same local or dedicated world.
Begin at the same Ancient Spire or base position and use the same weather and time if possible.
Turn toward a dense base, forest, water feature, or long view that normally causes drops.
Record average FPS, the lowest repeated drop, VRAM use, GPU use, and CPU use.
Change one setting category and repeat.

If GPU utilization stays near its maximum, reduce resolution-dependent and lighting settings. If GPU use falls while FPS remains limited, the CPU, simulation, streaming, or server session may be the constraint.

Stutter and long-frame troubleshooting

Allow the initial shader preparation to finish; first startup can take longer, particularly on Steam Deck.
Install the current stable GPU driver, then restart before testing.
Verify game files through Steam after an interrupted update.
Keep adequate free space and prefer an SSD.
Close overlays, capture tools, or browser workloads one at a time to identify conflicts.
Compare a small local world with the affected world. A large base or busy server can reveal simulation pressure that a graphics preset cannot solve.
Test a wired connection when the problem is rubber-banding or delayed interaction rather than low local FPS.

Do not delete saves or configuration files as a first troubleshooting step. Back them up before any reset.

Steam Deck settings

Keen Games states that Enshrouded currently works on Steam Deck with the recommended default settings. Its support article warns that the first startup may show a black screen for a minute or two while the client and shaders prepare. Wait for that process before forcing a restart.

For steadier battery and frame time, begin with the recommended defaults and a conservative frame cap. Re-evaluate after 1.0 because the final build may change shader behavior, presets, and performance.

Dedicated-server versus client performance

A dedicated server can remove world-hosting work from a player's PC, but it does not make the player's GPU render faster. Diagnose separately:

Low FPS or poor frame time is generally a client rendering or simulation issue.
Rubber-banding, delayed actions, or every player lagging together can indicate server or network pressure.
One player lagging while others remain responsive usually points to that player's connection or client.

Use the server troubleshooting guide for network and process checks.

1.0 launch-day performance checklist

Record the current resolution, preset, upscaler, cap, and observed FPS before updating.
Back up saves and user configuration.
Read the final patch notes and system requirements.
Let shader preparation finish on the first launch.
Retest the same benchmark route before changing settings.
Reset only the graphics preset if old settings behave incorrectly.
Update this guide's recommendations from repeatable results, not trailer footage.

Keen's Update 8 already reduced RAM usage, improved dynamic global illumination performance, improved water simulation in long flows, and reworked map memory use. Those changes support the direction of optimization work, but they do not guarantee a particular frame rate on 1.0.