Keen Games needed three sentences. On 23 October 2026 the studio posted the entire Steam Deck announcement as: “we got news from Valve that Enshrouded 1.0 was Steam Deck Verified! If you were waiting for a signal to bring Embervale with you in your pocket, this is it.” It closed with “We’ll be back next week with more fixes and improvements.”

That is the news. What it does not do is tell you what Valve tested, what failed to pass, or which of the game’s own settings now decide whether the badge holds up in your hands. Valve publishes that per title, and the report for app 1203620 is more specific than a badge.

This piece covers the Enshrouded build, not the compatibility programme — for the meaning of the four badges themselves, see Steam Deck Verified: What the Badges Mean. The advice below assumes v1.0.1.1, the Hotfix #4 build Keen Games shipped on 3 November 2026 (internal version 1285601). Two builds landed after the badge: Patch #1, published as v1.0.1.0 on 2 November (version 1283531), and Hotfix #4. The badge itself was earned on a build no later than 1.0.0.3, the last hotfix before it.

What this covers: the per-test results behind Enshrouded’s Deck badge, the 1.0 patch work that made a handheld build possible, and the in-game settings that decide what you actually get. Why it matters: the badge certifies a floor — 30fps at 800p on Valve’s default configuration — and a survival game’s late-game base is the case that ceiling was never tested against. Who should care: anyone who bought or is buying Enshrouded for a Deck or another handheld, and PC players deciding whether to carry a world across to one.

The test sheet Valve actually filed

A badge is a summary of five lines of detail, and Valve serves those lines from the same endpoint the store client uses. For Enshrouded the Deck result comes back as category 3 — Verified — with four passing checks and one note.

Steam’s test identifierWhat it certifies, in plain termsResult
DefaultControllerConfigFullyFunctionalThe shipped controller layout reaches every function; nothing needs remapping firstPass
ControllerGlyphsMatchDeckDeviceOn-screen prompts show Deck buttons, not keyboard keysPass
InterfaceTextIsLegibleThe interface reads at handheld size and distancePass
DefaultConfigurationIsPerformantThe default graphics configuration clears Valve’s frame-rate barPass
ExternalControllersNotSupportedPrimaryPlayerAn external controller is not supported for the primary playerNote

Those first four map onto Valve’s published checklist, which is why the results read the way they do. The bar for the fourth is written down: “On Steam Deck, this is 30fps at 800p,” and the third has a number too — “the smallest on-screen font character should never fall below 9 pixels in height at 1280x800,” at a viewing distance of “12 inches/30 cm,” with 12px the recommended target. Verified is a pass at those numbers, not an endorsement above them.

The same endpoint returns a Steam Machine row that also passes, and a separate SteamOS row that returns only “game startup functional” alongside the external-controller note. GamingOnLinux reported on 19 October that “the game was already Steam Machine Verified / SteamOS Compatible, but it seems there was enough fixing up done to also get it now Steam Deck Verified too” — which matches what the report still says.

The one line on the sheet that is not a pass

ExternalControllersNotSupportedPrimaryPlayer is easy to scroll past, and it is the only item on the list that describes a limitation. Valve’s own marketing for the Dock describes exactly that setup: “Dock Deck to your TV and play games on the couch with your favorite wireless controllers.”

Neither Keen Games nor Valve has published an explanation of what the note covers — how the game behaves when a gamepad is the primary input, whether prompts fall back to Deck glyphs, or whether it is a statement about a second player. It is worth reading as a caution rather than a verdict: if you plan to play docked with a controller in your hands, test it in the refund window rather than assuming the badge covers you. The one peripheral-adjacent fix in the notes since launch is narrower — hotfix 1.0.0.1 lists “Fixed crashes caused by specific peripherals attached to the PC” without naming them.

What 1.0 did for handhelds

The badge arrived a week after launch, but the groundwork is in the 1.0.0.0 changelog from 14 October, which includes a line no other patch note in the game’s history carries: “Improved performance on handheld devices, low-end graphics cards and the Steam Deck.”

BuildDateHandheld-relevant entries
1.0.0.015 Oct 2026Handheld/Deck performance work; reduced VFX shader compilation time; video-memory savings; point-light shadows reworked for large builds; CPU-side measures; new save format; HDR support
1.0.0.115 Oct 2026Random-crash fixes; peripheral-related crash fixes
1.0.0.216 Oct 2026Crash on fast travel or glider landing “in a world with a lot of entities”
1.0.0.321 Oct 2026“Improved a stuttering issue in the game when using V-Sync on AMD graphics cards”; light flicker in very large bases
1.0.1.02 Nov 2026New graphical settings for AMD cards; 3D resolution scale reset fix; larger memory budget for player bases; several crash fixes
1.0.1.13 Nov 2026Water-simulation crash; melting-texture fix on voxel walls; log-spam performance issue

Read the 1.0.0.0 technical section as a list of things that were fighting a handheld. “Significantly reduced the VFX shader compilation time at the start of the game after updating the game or the GPUGPU. Graphics Processing Unit — the chip that renders the game's visuals; the main driver of framerate and image quality. driver” addresses the one-off hitch every Deck owner meets after a patch or a Proton update. “Reworked the point light shadows with the goal to support large player constructions with many lights” is the base-building cost. “Added several measures to reduce the performance impact on CPUs” and “Implemented several methods to save video memory without sacrificing graphical quality” are the two budgets a Deck has least of. None of those are unique to Deck players, but each one is worth more to a 15W APU than to a desktop.

The single most useful entry for Deck owners is not in the 1.0.0.0 list at all. Hotfix 1.0.0.3 improved “a stuttering issue in the game when using V-Sync on AMD graphics cards” — and Valve’s spec page lists the Deck’s chip as a “6 nm AMD APU,” so an AMD-specific V-Sync stutter is a Deck-shaped problem. That fix landed two days before the badge did.

The settings that decide your frame rate

Enshrouded ships with the knobs a handheld needs, and the patch notes name enough of them to build a short list. What follows is what the notes say, not a tested preset.

SettingWhat the notes establishWhat to do with it on Deck
3D resolution scale1.0.1.0 fixed the slider showing 100% after a reset even when “the preset for the detected graphics card uses a default that is below 100%”Check the actual number after a reset; a preset below 100% is what the game intends for weaker GPUs
Graphics presets“Updated the list of graphics settings presets for the automatic GPU detection system” (1.0.0.0), plus “new graphical settings for AMD graphics cards” (1.0.1.0)Re-check the preset after a patch; the detection list changes between builds
Text sizeThe UI supports at least 80% and 140% — 1.0.1.0 fixed a Sparkworks slider layout “when the text size was set to 80%”, and 1.0.0.0 fixed menus that broke “when setting the font size to 140%”Valve tested legibility at the default. 80% is below what was tested; if you shrink it, you are outside the badge
HDR“Enshrouded now supports HDR if a compatible monitor or TV has been connected” plus a calibration screen (1.0.0.0)Only relevant on the OLED model, whose panel is HDR-capable; the badge does not change between models
Aim assist“Players can now configure aim snap assist and stick aim assist in the game settings” (1.0.0.0)The one combat setting aimed squarely at stick aiming
Trigger thresholdController actions “now already responds at 50%, not almost 100% as before”, except ranged combat and fishing (1.0.0.0)Fewer half-presses that fail to register
Sprint toggle“Sprint can now be set to toggle in the keyboard & mouse settings” (1.0.1.0)Note the menu it lives in — it is filed under keyboard and mouse, not controller

The numbers worth carrying out of that table are Valve’s, not Keen Games’: the frame-rate bar is 30fps and the text floor is 9 pixels, and neither scale moves with the screen. Valve’s spec page lists the panel as “1280 x 800 x RGB” running “up to 90Hz” on the OLED model, and its Deck Verified page states that tested titles “maintain those ratings for both LCD and OLED models. Nothing changes for Steam Deck OLED!” A 90Hz panel therefore does not mean 90fps was certified, and an HDR-capable panel does not mean the HDR calibration screen was part of the review.

Late game is the case the badge never saw

Verified describes the shipped default configuration, and for a survival game the shipped default configuration is a fresh character in the opening hours. The patch notes since launch describe what happens to the other save.

Hotfix 1.0.0.2 fixed a crash “when fast traveling or landing with a glider in a world with a lot of entities, such as enemies, survivors, mannequins, etc.” Hotfix 1.0.0.3 fixed “light flickering in very large player bases” and several crashes tied to the water simulation, then 1.0.1.1 fixed another water-simulation crash and “incorrect textures on voxel walls.” Patch 1.0.1.0 raised “the memory budget for the total sum of all player bases during the save data migration.”

None of that is Deck-specific, and all of it is Deck-relevant. A world with sixteen players’ worth of structures is the load a handheld has the least headroom for, and it is the load nobody at Valve tests: the checklist has a frame-rate item and a legibility item, and no item for hour sixty of a shared world. If you are carrying an established base onto a Deck, expect the Deck to be the constraint and treat the first long session as a measurement.

Carrying a world between PC and Deck

The store page lists Enshrouded as Windows-only — Valve’s app-details endpoint returns windows: true, mac: false, linux: false — so the Deck runs the Windows build through Proton, as GamingOnLinux’s compatibility line notes. Co-op is “up to 16 players,” and because Deck and desktop are the same Steam platform, the absence of cross-play does not touch it: Keen Games’ 13 October FAQ states “Enshrouded will not be cross-platform at launch” and that there is “no current estimate on how much time it will take us,” which is a console question.

Two logistics matter more than they look. Storage is “60 GB available space” per the store page, against 512GB and 1TB Deck tiers and a microSD slot. Saves are the other. The 1.0.0.0 notes moved save selection into tabs: “players can now select if they want to use a local save game folder or the Steam cloud folder… make sure to select the correct tab if you don’t see the character or world that you expected to see.” A character that appears missing on Deck is the first thing to check. Steam Cloud is listed on the store page, and Valve’s partner guidance asks for exactly that transfer, while recommending the reverse for settings: graphics configuration “should be set and saved on a per-device basis,” with Valve recommending “against syncing game configuration settings, ie., display resolution, between different devices.” Whether Enshrouded honours the second half is not documented anywhere Keen Games publishes, so verify it rather than assume.

Battery is the last number the badge says nothing about. Valve’s spec page for the OLED model lists a “50Whr battery. 3-12 hours of gameplay” — a hardware envelope for lightweight titles, not an Enshrouded figure, and Keen Games has published no runtime estimate.

What to watch next

There is no dated post-1.0 content plan. The 3 November news feed carries a hotfix and a cosmetic drop, and the 1.0.1.0 changelog defers work in its own text: “Another fix for this is planned for the next update,” written about Fell enemies that drop no loot. Keen Games’ promise in the Deck post — “back next week with more fixes and improvements” — was kept, twice over, with Patch #1 and then Hotfix #4.

The thing to watch for a Deck owner is narrower than a roadmap. The badge is a statement about one build running on one runtime, and Keen Games has shipped four patches since 1.0.0.1 — five counting that launch-day hotfix — in the nineteen days to 3 November, each touching rendering, memory or crashes. Both halves of that sentence mean the honest answer to “does Enshrouded run well on a Deck” is a date, not a badge. The badge is the 23 October answer.

Next read