Decky Loader and plugin operations

Scope

Decky extends the Steam client session and loads separately maintained plugins. It is not part of SteamOS or supported by Valve. This page covers the stable installer and catalog as reviewed on 2026-07-15.

Plugin status

PluginCanonical catalog sourceMain boundaryOperational note
CSS Loader
DeckThemes/SDH-CssLoader
Injects community CSS into Steam UI
Themes may break after client UI updates
PowerTools
gitlab.com/NGnius/PowerTools
Changes CPU/power controls
Validate every per-game change
SteamGridDB
SteamGridDB/decky-steamgriddb
Fetches and writes artwork metadata
Check account/network and cached data
HLTB
morwy/hltb-for-deck
Fetches third-party completion data
Results and matching can change

Trust boundary

Decky installs a loader outside Valve's support boundary and plugins execute in the Steam client context. The installer needs elevated authorization; plugins may use network access, write configuration, call helper services, or change power behavior. Never install a ZIP or URL from an untrusted source.

Do not enter credentials into a plugin unless its documented account flow requires them and you have verified the publisher and destination. Store popularity is not a permission audit.

Supported installation

Switch to Desktop Mode, open the current Decky installation guide, download its released desktop installer, and select the stable channel. Prefer this reviewable workflow over piping a changing remote script directly into a shell. Install plugins only through Decky's built-in Plugins Browser unless you are intentionally testing development code.

Verification

Return to Gaming Mode, confirm Decky's menu opens, record loader/channel versions, then install one plugin. Verify the promised function without changing unrelated settings. For PowerTools, record the original CPU/power values before any adjustment.

Update

Update the loader and each plugin through Decky's own settings. Read current issues before SteamOS or Steam client beta updates. Do not mix stable loader, prerelease plugins, and custom stores while diagnosing a regression.

Uninstall

Remove plugins in Decky settings first. Their created themes, caches, credentials, or configuration may remain. Run the same released Decky installer and choose its uninstall action to remove the loader.

Rollback

Disable or remove the last changed plugin, restore its settings, restart the Steam client, and return the loader to the previous stable channel only through documented controls. If Gaming Mode is unstable, use Desktop Mode and the released installer rather than manually deleting loader paths.

Recommended use

Use Decky when a specific plugin solves a documented need that SteamOS does not cover. Keep the plugin set small, record versions, and remove cosmetic or telemetry integrations first when the Steam client changes.

Frequently asked questions

Does a plugin being listed by Decky mean it is security-audited?
Does a plugin being listed by Decky mean it is security-audited?
No. Catalog presence supplies a distribution path, not a security or future-compatibility guarantee. Review the plugin owner, permissions, data, and issue history.
Why can Decky disappear after a SteamOS update?
Why can Decky disappear after a SteamOS update?
Decky documents that SteamOS or Steam client changes can disrupt its injection path. Recheck current known issues before reinstalling or changing channels.

Sources

Version history

  • 2026-07-15: Phase 6 stable-channel, trust-boundary, and rollback review.