Best Enshrouded 1.0 Settings for FPS and Performance

Start here: choose a preset for your hardware, measure the same scene, then change one setting category at a time. For low FPS, begin with the starting profiles; for stutter, use the troubleshooting checklist. If everyone in a shared world lags together, investigate the server or network separately.

Enshrouded 1.0 is out. The preset → measure → change one category workflow still applies. Exact 1.0 benchmarks are being collected; the starting profiles below are test points, not measured frame-rate promises.

Current PC system requirements

Steam-listed requirements — re-check the Steam store page for the 1.0 listing.

These retained Steam-listed values have not been revalidated as 1.0 requirements here.

Recommended starting profiles

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

1. Choose the target first. Cap to a frame rate the system can sustain instead of oscillating between a high maximum and visible drops.
2. Use the available quality upscaler. DLSS, FSR, or the supported alternative can reduce GPU load while preserving a clearer image than lowering every setting.
3. Reduce shadow quality. Shadows commonly affect both GPU time and scene complexity.
4. Reduce global illumination or indirect-lighting quality. The current renderer uses dynamic global illumination, and Keen specifically optimized it in Update 8.
5. Reduce vegetation and distance-related detail. This is especially useful in dense Revelwood areas and when looking across large terrain.
6. Reduce effects and volumetric quality. Test inside the Shroud and during combat, not only at an empty base.
7. 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:

1. Restart the game after a driver or major graphics change.
2. Load the same local or dedicated world.
3. Begin at the same Ancient Spire or base position and use the same weather and time if possible.
4. Turn toward a dense base, forest, water feature, or long view that normally causes drops.
5. Record average FPS, the lowest repeated drop, VRAM use, GPU use, and CPU use.
6. 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. Retest after updating: 1.0 changed rendering and shader preparation, so older measurements are not 1.0 benchmarks.

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.

After updating to 1.0

1. Record your resolution, preset, upscaler, frame cap and observed FPS in the updated game.
2. Preserve pre-update backups and copy saves and configuration before further changes.
3. Read the 1.0 release notes and recheck the Steam requirements.
4. Let shader preparation finish on the first launch.
5. Retest the same benchmark route before changing settings.
6. Reset only the graphics preset if old settings behave incorrectly.
7. Compare repeatable 1.0 measurements with your old results; do not treat trailer footage as a benchmark.

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.

Official sources

• Current Steam system requirements
• Official system requirements article
• Official Steam Deck guidance
• Forging the Path performance changes
• Enshrouded 1.0 release announcement

Related pages

• 1.0 release notes
• Compare server hosting