The Steam Deck is a remarkably capable handheld out of the box, but its real ceiling only appears once you bolt on Decky Loader – the community plugin loader that injects custom features directly into SteamOS Gaming Mode. With Decky installed, the same Quick Access Menu that shows your battery percentage can fetch official Steam artwork, throttle your APU to squeeze out an extra hour of battery, record clips, theme the entire interface, and stream remote games – all without ever leaving the couch. This tutorial walks you through a clean 2026 install of Decky Loader v3.2.4 on a Steam Deck (LCD or OLED), then layers on the 12 most useful plugins, performance tuning, troubleshooting, and a full uninstall path if you ever want to roll back.
Decky Loader is free, open source, and reversible. The entire process below takes roughly 15–20 minutes, requires no soldering or BIOS flashing, and survives most SteamOS updates. By the end you will have a fully working plugin stack, an understanding of the release versus prerelease branches, and a security checklist so you know exactly what root-level access you are granting. This guide targets decky loader on Valve hardware first, with a dedicated section for the decky loader install path on Bazzite-powered handhelds like the ROG Ally and Legion Go.
What Is Decky Loader and Why Install It in 2026?
Decky Loader is a homebrew plugin framework built by the SteamDeckHomebrew community. It hooks into the SteamOS Gaming Mode UI and exposes a new tab inside the Quick Access Menu (QAM) – the menu you reach with the three-dot ... button on the right of the Deck. From that tab you open a Plugin Store, browse community-built plugins, and install them with a single button press. There is no need to enter Desktop Mode again after the initial setup; everything runs natively inside the gaming interface you already use.
The current stable build is Decky Loader v3.2.4, published on May 28, 2026. It is SteamOS-only by design: the loader patches Valve’s own client, so it expects the Arch-based SteamOS environment that ships on the Steam Deck (or a compatible immutable distro like Bazzite). The keyword “decky loader” alone draws roughly 18,100 US searches per month, which tells you how central it has become to the handheld-PC scene – it is effectively the de-facto modding layer for the platform, the same role Playnite plays on desktop and EmuDeck plays for emulation.
Why bother? Stock SteamOS gives you no way to customize artwork for non-Steam games, no per-game TDP profiles inside Gaming Mode, no native clip recorder, and no UI theming. Decky’s plugin ecosystem fills every one of those gaps. PowerTools alone – a downclocking and SMT-control plugin – can meaningfully extend battery life on demanding titles, while SteamGridDB fixes the ugly default tiles you get after importing emulators or launchers. Because each plugin is sandboxed to the Decky framework and the whole loader can be removed in seconds, the risk profile is low compared with flashing custom firmware. If you have already followed our EmuDeck emulation tutorial, Decky is the natural next layer to make those imported games look and run their best.
Prerequisites: What You Need Before Installing Decky Loader
Decky Loader is forgiving about hardware but strict about the underlying OS. Run through this checklist before you touch the terminal. Skipping the sudo-password step is the single most common reason a first install fails, so do not treat the table below as optional reading.
| Requirement | Minimum / Recommended | Notes |
|---|---|---|
| Device | Steam Deck LCD or OLED | Also works on Bazzite handhelds (ROG Ally, Legion Go, Steam Deck) |
| Operating system | SteamOS 3.x (Holo) or Bazzite | Windows is not supported – Decky patches the SteamOS client |
| Decky Loader version | v3.2.4 (stable, May 2026) | Prerelease branch available for early features |
| Free storage | ~50 MB for loader + plugins | Plugins are small; clip recorders need more space |
| Internet | Wi-Fi connection | Required to pull the installer and Plugin Store catalog |
| sudo password | Must be set in Desktop Mode | Fresh Decks ship with a blank password – installer needs one |
| Account access | Your own user (deck) | No second account or developer license needed |
A few clarifications. First, both Steam Deck models – the original LCD and the 2023 OLED – use the same installer; there is no model-specific build, so the steps are identical whether you read our Steam Deck OLED vs LCD comparison and went OLED or kept your launch LCD. Second, Decky requires a sudo password because the installer needs elevated privileges to write into protected SteamOS directories. Brand-new Decks have an empty password, and the installer cannot proceed with a blank credential. We will set one in Step 2. Third, if you plan to use streaming plugins such as MoonDeck, make sure your host PC and our Moonlight streaming setup are working first, because MoonDeck simply automates that existing Moonlight pipeline rather than replacing it.
Step 1: Switch the Steam Deck to Desktop Mode
Decky Loader is installed from Desktop Mode, the full KDE Plasma environment hiding under SteamOS. You only need Desktop Mode once – for the install itself – after which everything happens inside Gaming Mode. To switch over, press the STEAM button to open the main menu, scroll down to Power, and select Switch to Desktop. The screen will briefly go black and reload into the Plasma desktop with a taskbar, a Steam icon, and a Firefox/Konsole launcher.
If this is your first time in Desktop Mode, a couple of quality-of-life tips will save you frustration. The Deck’s trackpads act as mouse input – the right trackpad moves the cursor, and the R2 trigger is a left click. Pressing STEAM + X opens the on-screen keyboard anywhere you need to type, which you will need for the terminal commands coming up. If you have a USB-C dock, a real keyboard and mouse make the whole process dramatically easier, but they are not required.
Desktop Mode is also where you confirm your SteamOS version. Open the application launcher (the bottom-left Steam Deck icon), search for “Konsole,” and run the command below to print your build. Anything on the SteamOS 3.x Holo branch is fully compatible with Decky Loader v3.2.4.
# Confirm you are on a supported SteamOS build
cat /etc/os-release | grep -E 'NAME|VERSION'
# Expected output (values vary by update):
# NAME="SteamOS"
# PRETTY_NAME="SteamOS Holo"
# VERSION_ID=3.x
Common pitfall: Some users try to install Decky from Gaming Mode using a controller-only browser. That path does not exist – the installer is a shell script that must run from a terminal in Desktop Mode. If a “guide” tells you to download an EXE or install Decky on Windows, close it; Decky has no Windows build because it patches the Linux SteamOS client directly.
Step 2: Set a sudo Password in Konsole
The Decky installer requests elevated permissions to write into SteamOS system folders, so the deck user must have a real sudo password. Out of the box that password is blank, and sudo refuses to authenticate with an empty string. Setting one takes 20 seconds. Open Konsole from the application launcher and run:
# Set a sudo password for the deck user
passwd
# You will be prompted:
# New password: (type it – nothing shows on screen, that is normal)
# Retype new password: (type it again)
# passwd: password updated successfully
Choose something you will remember – you will need it any time a plugin or update asks for elevated access. The cursor will not move and no asterisks will appear while you type the password; that blank behavior is a security feature of Linux terminals, not a frozen input. Type carefully and press Enter.
If you ever forget this password later, you can reset it the same way from Desktop Mode. Note that a major SteamOS update occasionally resets the deck account password to blank again, which will make Decky updates fail until you re-run passwd. Keep that in mind for the troubleshooting section. The official installer can temporarily set the password to Decky! during install and then clear it, but setting your own password manually first is cleaner and avoids surprises.
Common pitfall: Setting the password and then immediately running the installer in the same session is fine, but if you set it, reboot, and the password “does not work,” you almost certainly mistyped it during the blind entry. Re-run passwd to set a fresh one. There is no lockout penalty for doing this repeatedly.
Step 3: Download and Run the Decky Loader Installer
With a sudo password in place, you can install Decky in one of two ways: the graphical installer (a desktop file you double-click) or the terminal one-liner. The terminal method is faster and more reliable because it always pulls the latest stable release directly from GitHub. In the same Konsole window, run:
# Install the latest STABLE release of Decky Loader
curl -L https://github.com/SteamDeckHomebrew/decky-installer/releases/latest/download/install_release.sh | sh
The script downloads the loader, asks for your sudo password (enter the one you just created), and writes the Decky service into your home directory under ~/homebrew. You will see progress lines as it fetches the release, sets up the systemd service, and registers the plugin loader with the Steam client. A successful run ends with a confirmation that Decky Loader has been installed and that you should return to Gaming Mode. Expected output looks like this:
[*] Installing Decky Loader (release branch)...
[*] Downloading latest release from GitHub...
[*] Creating ~/homebrew directory structure...
[*] Installing systemd service plugin_loader.service...
[*] Enabling and starting service...
[+] Decky Loader installed successfully.
[+] Return to Gaming Mode and open the Quick Access Menu.
If you prefer the GUI installer, open Firefox in Desktop Mode, go to the decky-installer releases page, download the desktop installer file, and double-click it – it presents the same release/prerelease choice as a dialog. Both paths produce an identical result. The terminal command is preferred because it never gets stuck on a stale cached download and it is trivially scriptable if you ever reflash your Deck.
Common pitfall: If the command returns “curl: command not found” you typed it into the wrong window – make sure you are in Konsole, not the Steam in-app browser. If it returns a permissions or sudo error, your password is blank or wrong; revisit Step 2. If the download stalls, your Wi-Fi dropped – reconnect and re-run the exact same command, which is fully idempotent.
Step 4: Choose Release vs Prerelease Branch
Decky ships in two channels and understanding the difference prevents a lot of confusion. The release (stable) branch is what the command in Step 3 installs by default, and it is what 95% of users should run. It is tested, predictable, and the version the Plugin Store is validated against – currently v3.2.4. The prerelease branch carries newer, less-tested features and bug fixes that have not yet graduated to stable. You only want prerelease if a stable bug is actively blocking you or you want to test upcoming functionality.
To install the prerelease channel instead, use the parallel installer script:
# Install the PRERELEASE (testing) branch – advanced users only
curl -L https://github.com/SteamDeckHomebrew/decky-installer/releases/latest/download/install_prerelease.sh | sh
You can switch between branches at any time from inside Decky’s settings later – there is a developer settings panel with a “Branch” dropdown and a “Reinstall” button. Switching from prerelease back to stable is the standard fix when a testing build misbehaves after a SteamOS update. The official guidance from the project is consistent: try stable first, and only drop to prerelease if stable cannot solve a problem after a clean reinstall.
| Branch | Stability | Best for | Install script |
|---|---|---|---|
| Release (stable) | High – tested | Everyone, daily driving | install_release.sh |
| Prerelease (testing) | Lower – bleeding edge | Bug fixes, new features, contributors | install_prerelease.sh |
Recommendation: Start on stable. If you hit a SteamOS-update breakage that reinstalling stable does not fix, try prerelease, then switch back to stable once a new stable release lands. Do not run prerelease just because the number is higher – the Plugin Store occasionally lags prerelease API changes, which can leave plugins temporarily broken.
Step 5: Return to Gaming Mode and Open the Quick Access Menu
The install is done in Desktop Mode, but Decky lives in Gaming Mode. Double-click the Return to Gaming Mode icon on the desktop. SteamOS will reload the gaming interface. Once you are back, press the … (three dots) button on the right side of the Deck to open the Quick Access Menu. If the install succeeded, you will see a new plug-shaped icon added to the row of QAM tabs at the top – that is Decky Loader.
Tap the plug icon to open the Decky panel. On a fresh install it shows an empty plugin list with a small store (shopping bag) icon and a gear/settings icon in the top-right corner of the Decky header. This empty state is correct – you have not installed any plugins yet. If you do not see the plug icon at all, do not panic; the most common cause is that the Steam client needs one more restart. Hold the STEAM button, choose Power, and select “Restart Steam” or reboot the device, then check the QAM again.
It is worth orienting yourself in the QAM before going further because every plugin you install surfaces here. The QAM is the same menu that controls performance overlays, brightness, and notifications. Decky simply adds its own tab into that existing strip, which is why plugins feel native rather than bolted-on. Compared with juggling separate desktop apps, this single-button access is the entire appeal – the same convenience that makes our best cloud gaming services roundup praise instant-resume handhelds applies doubly to Decky’s in-line plugin model.
Step 6: Open the Plugin Store and Install Your First Plugin
Inside the Decky panel, tap the store (shopping bag) icon in the top-right. This opens the Plugin Store – a curated catalog of community plugins maintained in the SteamDeckHomebrew plugin database. Each entry shows the plugin name, author, a short description, a download count, and an Install button. Browsing is done entirely with the D-pad and A button; no keyboard required.
For your first install, a great low-risk choice is ProtonDB Badges, which adds a compatibility rating badge to each game’s store and library page by pulling crowd-sourced data from ProtonDB. Find it in the list, press Install, and watch the bottom of the panel for a progress indicator. When it finishes, back out of the store and the plugin appears in your main Decky panel list. Open any game page and you will see its Proton compatibility tier rendered inline.
The Plugin Store handles dependencies, versioning, and updates automatically. When a plugin has an update available, a small badge appears in the store, and you update it with one press. There is no manual file copying involved – this is the entire point of using a loader rather than installing mods by hand. The catalog includes a search field at the top; press it and the on-screen keyboard appears so you can type a plugin name directly instead of scrolling.
# Decky's files live entirely in your home folder.
# You can inspect installed plugins from Konsole if curious:
ls ~/homebrew/plugins/
# Example output after installing a few plugins:
# CSS-Loader PowerTools ProtonDB-Badges SteamGridDB
Common pitfall: If the Plugin Store shows “Failed to load” or an empty catalog, it is almost always a network or DNS hiccup, not a broken install. Confirm Wi-Fi is connected, then reopen the store. If it persists, the troubleshooting section below covers forcing a store refresh and checking the plugin_loader service status.
Step 7: Install CSS Loader and SteamGridDB
These two plugins deliver the most immediately visible payoff, so install them next. CSS Loader is a theming engine that lets you apply community-made CSS themes to the SteamOS interface – everything from subtle accent-color tweaks to full visual overhauls of the home screen, library, and QAM. After installing CSS Loader from the store, open its panel, tap “Manage Themes,” and browse the built-in theme browser. Toggling a theme on applies it instantly with no restart.
SteamGridDB is arguably the single most useful Decky plugin for anyone who imports non-Steam games – emulator shortcuts, EmuDeck entries, Epic and GOG titles added through a launcher, or anything you added manually. By default these show up with blank or generic tiles. SteamGridDB connects to the community artwork database of the same name and lets you pick official-quality grid images, heroes, logos, and icons for every shortcut, directly from Gaming Mode. The transformation from a wall of grey placeholders to a polished, cover-art library is dramatic.
To use it, open any game’s page, press the … button while the title is highlighted, choose “Change artwork via SteamGridDB,” and browse candidates. The plugin downloads your selection and applies it to the Steam library cache. If you followed our Playnite setup guide on a desktop, SteamGridDB is the handheld equivalent for getting clean artwork on every entry. An optional API key (free from the SteamGridDB site) raises rate limits and unlocks higher-resolution assets, but the plugin works fine without one for casual use.
# Optional: add a SteamGridDB API key for higher rate limits.
# 1. Create a free account at steamgriddb.com
# 2. Generate an API key in your account preferences
# 3. Paste it into the SteamGridDB plugin settings inside Decky
# No terminal command is needed – entry is done in the plugin UI.
Common pitfall: Applied artwork sometimes does not refresh until you back out of the game page and return, or restart Steam. If a tile still looks wrong, give the cache a moment or restart the client. Do not re-download repeatedly – the image is usually already applied, just not yet repainted.
Step 8: Tune Performance with PowerTools
PowerTools is the power-user’s plugin: it exposes low-level controls over the Deck’s APU that are normally hidden, including CPU thread count (SMT on/off), per-core enable/disable, CPU frequency limits, GPU clock pinning, and power governor selection. Used carefully, it lets you cap a lightweight 2D game’s CPU to sip battery, or pin GPU clocks high for a demanding title to stabilize frame pacing. It complements – rather than replaces – the built-in TDP and refresh-rate sliders Valve already provides in the QAM performance tab.
Install PowerTools from the store, then open its panel from the Decky list. The key controls are grouped into CPU, GPU, and Battery sections. A practical starting recipe for older or 2D games is to disable SMT (halving thread count from 8 to 4) and set a modest CPU frequency cap, which can cut APU power draw noticeably without hurting performance on titles that are not CPU-bound. For demanding 3D games, leave SMT on and instead pin the GPU minimum clock to reduce stutter.
The most powerful feature is per-game profiles. PowerTools can remember a distinct CPU/GPU configuration for each game and apply it automatically when that game launches, so you never have to re-tune manually. Enable “Use per-game profile” inside the plugin and your settings are saved against the running title. This pairs naturally with Valve’s own per-game TDP profiles for a complete, automatic power strategy.
| Scenario | SMT | CPU cap | GPU strategy | Goal |
|---|---|---|---|---|
| Light 2D / indie | Off (4 threads) | Low | Default | Max battery life |
| Emulation (up to 6th gen) | On | Medium | Default | Balance |
| Demanding 3D AAA | On (8 threads) | None | Pin GPU minimum | Stable frame pacing |
| Cloud / streaming | Off | Low | Default | Minimal local load |
Common pitfall: Aggressive CPU caps can make a game stutter or fail to hit its target frame rate if it is actually CPU-bound. If performance drops after applying a PowerTools profile, raise the CPU cap or re-enable SMT. Because profiles are saved per game, a bad setting will keep reapplying every launch until you fix or delete that profile – so adjust the profile, do not just toggle it off once.
Step 9: Enable Developer Mode and Verify Plugins
Decky has a developer mode that unlocks extra panels useful for testing plugins, viewing logs, and switching branches. You do not need it for everyday use, but enabling it once is worth doing because it gives you a window into what the loader is actually doing – invaluable when something misbehaves. Open the Decky panel, tap the gear/settings icon, scroll to the General tab, and toggle Developer mode on. A new “Developer” section appears in settings.
Inside the Developer section you will find a log viewer, a “Reload” button to restart the frontend without rebooting, and the branch selector mentioned in Step 4. The log viewer is the fastest way to diagnose a plugin that crashes or fails to load – errors appear here with plugin names attached. You can also confirm the loader service itself is healthy from Konsole in Desktop Mode:
# Check that the Decky plugin loader service is running
systemctl status plugin_loader
# Healthy output includes a line like:
# Active: active (running) since ...
# If it shows "inactive" or "failed", restart it:
sudo systemctl restart plugin_loader
With developer mode on and the service confirmed active, run a quick verification pass: open the Plugin Store, install one more lightweight plugin such as HLTB for Deck (which shows HowLongToBeat completion-time estimates on game pages), and confirm it appears and functions. If a freshly installed plugin shows up in the list and works, your loader is fully healthy and you can install the rest of your stack with confidence.
Common pitfall: Leaving developer mode on permanently is harmless but it adds clutter and slightly more frontend overhead. If you are not actively debugging, toggle it back off for a marginally cleaner UI. It can be re-enabled in seconds whenever you need the logs.
Step 10: Update and Maintain Decky Loader
Decky keeps itself and its plugins current with minimal effort, but you should know where the controls live. The loader checks for its own updates and surfaces them in the Decky settings panel – when a new version like a v3.2.x point release lands, a notification appears and you update it with one button press, no terminal needed. Individual plugins update from the Plugin Store, which shows an update badge on any plugin with a newer version available.
The one maintenance event you must understand is SteamOS system updates. Because SteamOS uses an immutable, atomic update model that can replace large parts of the system, a major OS update will occasionally remove Decky entirely – the plug icon simply vanishes from the QAM after the update reboots. This is expected behavior, not a bug, and the fix is trivial: re-run the installer. Your plugins and their settings live in ~/homebrew, which survives the OS update, so reinstalling the loader restores everything instantly.
# If Decky disappears after a SteamOS update, restore it in one line.
# (Run from Konsole in Desktop Mode.)
curl -L https://github.com/SteamDeckHomebrew/decky-installer/releases/latest/download/install_release.sh | sh
# Your ~/homebrew/plugins and settings are untouched by the OS update,
# so all plugins return exactly as you left them.
Because the SteamOS update can also reset your deck password to blank, you may need to re-run passwd before the reinstall command will authenticate. If you put your Deck on the SteamOS Beta or Preview channel for early features, expect this disappear-and-reinstall cycle more often, since those channels update more frequently. Sticking to the Stable SteamOS channel keeps Decky stable for longer stretches.
Common pitfall: Do not assume a vanished Decky means your plugins are lost – they are not. People frequently reinstall plugins one by one after an OS update when simply re-running the installer would have brought the entire stack back automatically. Re-run the installer first; only troubleshoot individual plugins if something is still missing afterward.
12 Best Decky Loader Plugins in 2026
Once the loader is healthy, the plugins are where Decky earns its place. The table below ranks twelve of the most useful, popular plugins available in the Plugin Store as of mid-2026, grouped loosely by what they do. Install only what you need – every active plugin adds a small amount of overhead, and a lean stack of four or five well-chosen plugins beats a bloated list you never open.
| Plugin | Category | What it does |
|---|---|---|
| SteamGridDB | Artwork | Fetch official-quality grids, heroes, logos and icons for any shortcut |
| CSS Loader | Theming | Apply community CSS themes to the entire SteamOS interface |
| PowerTools | Performance | Low-level CPU/GPU/SMT control with per-game profiles |
| ProtonDB Badges | Compatibility | Show crowd-sourced Proton compatibility tiers on game pages |
| Decky Recorder | Capture | Record gameplay clips directly inside Gaming Mode |
| MoonDeck | Streaming | Automate Moonlight remote-play sessions from your library |
| HLTB for Deck | Info | Display HowLongToBeat completion estimates on game pages |
| Vibrant Deck | Display | Adjust color saturation/vibrancy of the screen |
| Animation Changer | Cosmetic | Replace the boot and suspend animations |
| AutoFlatpak | Maintenance | Automatically update Flatpak apps in the background |
| Bluetooth | Connectivity | Quick Bluetooth device management from the QAM |
| TabMaster | Organization | Create custom, filtered library tabs and collections |
A few combinations stand out. For anyone running emulators, SteamGridDB + TabMaster turns a messy library of imported ROMs into a clean, cover-arted, filterable collection – pair it with our EmuDeck tutorial for the full handheld retro setup. For battery-focused players, PowerTools + Vibrant Deck lets you both cap power draw and dial in the OLED’s color punch. For streamers and remote players, MoonDeck + Decky Recorder bring host-PC games and clip capture into Gaming Mode without ever opening a desktop app.
Common pitfall: Streaming and recording plugins are the most resource-intensive and the most likely to need their own configuration (codecs, host pairing, storage paths). If you install MoonDeck and it does nothing, that is expected until you have a working Moonlight host – set that up first using our streaming guide, then let MoonDeck automate it.
Installing Decky Loader on Bazzite (ROG Ally, Legion Go)
Decky is not strictly Steam-Deck-exclusive – it runs on any SteamOS-like environment, and the most popular way to get that on non-Valve handhelds is Bazzite, a Fedora-based immutable gaming distro that ships a SteamOS-style Gaming Mode. If you have an ROG Ally, ROG Ally X, or Legion Go and you have installed Bazzite, you can run the exact same Decky installer. The “decky loader bazzite” search term alone draws hundreds of monthly queries, reflecting how common this combination has become as Windows handhelds adopt Linux for better battery and a console-like UI.
The install path is nearly identical. From Bazzite’s desktop, open a terminal, ensure a sudo password is set (Bazzite usually configures one during setup, unlike a stock Deck), and run the same release installer. Bazzite is designed to be Decky-aware, so the loader generally survives Bazzite’s update model more gracefully than it does raw SteamOS updates, and many Bazzite images can even reinstall Decky automatically after an update.
# On a Bazzite handheld (ROG Ally, Legion Go, etc.), the command is identical:
curl -L https://github.com/SteamDeckHomebrew/decky-installer/releases/latest/download/install_release.sh | sh
# Bazzite ships ujust helpers too; some images expose:
ujust setup-decky # convenience wrapper, where available
Plugin compatibility is broad but not universal. Hardware-specific plugins like PowerTools expose controls tuned for the Steam Deck’s APU; on a different chip some toggles may have no effect or behave differently. Display and artwork plugins (SteamGridDB, CSS Loader, ProtonDB Badges, TabMaster) are hardware-agnostic and work identically everywhere. If you are weighing which handheld to build this stack on, our Legion Go vs Steam Deck comparison breaks down where each device’s strengths land for a Decky-modded setup.
Common pitfall: Trying to install Decky on a Windows handheld with no Linux layer will fail every time – there is no Windows build. The “decky loader windows” searches almost always end with users discovering they must first install Bazzite or SteamOS. Decky patches the Linux SteamOS client; without that client, there is nothing for it to load into.
Decky Loader Troubleshooting: 9 Common Problems
Most Decky problems trace back to four root causes: a missing sudo password, a dropped network connection, a SteamOS update that removed the loader, or a plugin/branch mismatch. The table maps the symptoms you will actually see to their fixes, in rough order of how often they occur.
| Symptom | Likely cause | Fix |
|---|---|---|
| Plug icon missing from QAM after install | Steam client needs a restart | Restart Steam or reboot, then reopen the QAM |
| Decky vanished after a system update | SteamOS atomic update removed it | Re-run the install_release.sh command; plugins persist |
| Installer fails with sudo/permission error | Blank or wrong sudo password | Run passwd in Konsole, set a password, retry |
| Plugin Store empty or “Failed to load” | Network/DNS hiccup | Confirm Wi-Fi, reopen store; check plugin_loader service |
| A plugin crashes or won’t open | Branch/API mismatch or bad install | Reinstall the plugin; switch to stable branch |
| Artwork won’t refresh after SteamGridDB | Library cache not repainted | Back out of game page or restart Steam |
| PowerTools profile causes stutter | CPU cap too aggressive for the game | Raise CPU cap / re-enable SMT in that game’s profile |
| Password “stopped working” after update | Update reset deck password to blank | Re-run passwd to set a new one |
| MoonDeck does nothing | No working Moonlight host paired | Set up a Moonlight host first, then configure MoonDeck |
When the Plugin Store fails to load, the fastest deeper diagnostic is to check the loader service from Konsole with systemctl status plugin_loader, as shown in Step 9. An “inactive” or “failed” state means the service did not start – a sudo systemctl restart plugin_loader usually revives it, and if it does not, a clean reinstall via the installer script will. For plugin-specific crashes, turn on developer mode and read the log viewer; the error almost always names the offending plugin, which you then reinstall or remove.
A subtle one worth calling out: if you switched to the prerelease branch and plugins suddenly break after an update, the Plugin Store may not yet support a changed prerelease API. Switching back to stable from the Decky settings branch selector is the standard cure. Conversely, if a specific new plugin requires features only present in prerelease, you may need to move forward instead. Match your branch to what your plugins expect.
Advanced Tips: Get More Out of Decky
Once your stack is stable, a handful of power-user techniques make Decky meaningfully better. First, lean on per-game PowerTools profiles plus Valve’s per-game TDP together: set a conservative TDP in Valve’s performance tab and a matching SMT/clock profile in PowerTools, both saved per game, and your Deck will automatically apply the right power envelope for every title with zero manual intervention. This is the closest thing to a “set it and forget it” battery strategy on the platform.
Second, use TabMaster to build curated library tabs that filter by installed status, store source, or custom tags – combine it with SteamGridDB artwork and your imported emulator and launcher games become indistinguishable from native Steam titles. Third, get a free SteamGridDB API key so artwork fetches faster and at higher resolution; it takes two minutes and removes the rate-limit stalls you hit during a big library makeover.
Fourth, keep a tiny text note of your Decky setup. Because a SteamOS update can wipe the loader, recording your plugin list and key settings means a post-update restore is a five-minute job rather than a memory exercise. You can even snapshot the plugin directory listing for reference:
# Snapshot your current plugin list to a file before a big SteamOS update
ls ~/homebrew/plugins/ > ~/decky-plugins-backup.txt
cat ~/decky-plugins-backup.txt
# After an update + reinstall, compare to confirm everything returned:
# diff <(ls ~/homebrew/plugins/) ~/decky-plugins-backup.txt
Finally, if you stream a lot, treat Decky as the glue between your handheld and your gaming PC: MoonDeck for remote play, plus the host setup from our Moonlight streaming tutorial, turns the Deck into a thin client for your desktop’s full library – a powerful complement to native and cloud play alike.
How to Uninstall Decky Loader Cleanly
Decky is fully reversible, which is a big part of why it is low-risk to try. There are two ways to remove it. The simplest is from inside Decky itself: open the settings (gear) panel, scroll to the bottom, and look for the Uninstall Decky Loader option, which removes the loader and disables its service. The second method is from Desktop Mode using the installer, which includes an uninstall path, or by manually removing the homebrew directory and the service.
# Manual clean removal from Konsole (Desktop Mode):
# 1. Stop and disable the loader service
sudo systemctl stop plugin_loader
sudo systemctl disable plugin_loader
# 2. Remove the service file and the homebrew directory
sudo rm -f /etc/systemd/system/plugin_loader.service
rm -rf ~/homebrew
# 3. Reload systemd so it forgets the removed service
sudo systemctl daemon-reload
# Reboot, and Decky – including all plugins – is gone with no trace.
After removal, reboot into Gaming Mode and confirm the plug icon is gone from the QAM. SteamOS returns to its stock behavior with no leftover artifacts – the only things in your home folder were under ~/homebrew, which you deleted. If you used CSS Loader themes, the interface reverts to default automatically since the theming engine that applied them is no longer loaded. If you only want to remove a single plugin rather than the whole loader, you do not need any of this: just open the plugin in the Decky list and use its uninstall button in the Plugin Store.
Common pitfall: Deleting ~/homebrew without first stopping and disabling the service can leave a dangling service entry that logs errors on boot. Always stop, disable, remove, and daemon-reload in that order. The in-app uninstall handles this sequencing for you, so prefer it unless you specifically need the manual path.
Security Considerations and Risks
Decky Loader is open source and widely used, but it is still third-party software that runs with elevated privileges, so it is worth understanding the trust model. The installer requests your sudo password because it writes a systemd service and patches the Steam client – that is root-level access, granted to a script you are piping from GitHub. The mitigations are reasonable: the project is open source and auditable, the install command pulls from the official SteamDeckHomebrew releases, and the loader runs as a normal service rather than modifying firmware. Nothing here is irreversible at the hardware level.
The more nuanced risk is the Plugin Store. Plugins are community-contributed code that runs within the Decky framework, and while the store is curated, you should still exercise the same judgment you would installing any extension: prefer popular, well-maintained plugins with high download counts and active development. The twelve plugins in our table above are all established, widely-used projects. Avoid obscure plugins with no reviews or downloads, especially anything requesting unusual permissions.
Practical hardening: keep Decky on the stable branch unless you have a reason not to, only install plugins you will actually use, and remove ones you abandon. Because the entire stack lives in ~/homebrew and can be wiped in seconds, your worst-case recovery – a clean reinstall of SteamOS or a deletion of the homebrew folder – is fast and complete. This reversibility is exactly why Decky is considered safe enough for mainstream Steam Deck users despite the elevated install. As always, install the loader only from the official GitHub source linked below, never from a re-hosted mirror or a “modified” installer promising extra features.
Frequently Asked Questions
Is Decky Loader safe to install on a Steam Deck?
Yes, for the vast majority of users. Decky Loader is open source, installs from the official SteamDeckHomebrew GitHub, runs as a removable service, and does not touch firmware. The main caution is the Plugin Store – stick to popular, well-reviewed plugins. The entire loader can be uninstalled in seconds, leaving no trace, which is why it is widely considered low-risk.
Will Decky Loader void my Steam Deck warranty?
Decky is software-only and fully reversible – it does not modify hardware or firmware, and it lives entirely in your home folder. It is not the same as opening the device or flashing a BIOS. That said, it is unofficial homebrew, so Valve does not support it; if you ever need warranty service, uninstalling it first is sensible.
Why did Decky Loader disappear after a SteamOS update?
This is normal. SteamOS uses an immutable, atomic update model that can replace large parts of the system, occasionally removing the loader. Your plugins and settings survive in ~/homebrew. Just re-run the install_release.sh command from Desktop Mode and everything returns exactly as you left it – often you may also need to re-run passwd if the update cleared your sudo password.
Can I install Decky Loader on Windows or on an ROG Ally?
There is no Windows build – Decky patches the Linux SteamOS client. To run it on an ROG Ally or Legion Go, install Bazzite (a SteamOS-style Linux distro) first, then run the same installer. Display and artwork plugins work identically on any device; hardware-specific plugins like PowerTools may behave differently on a non-Deck APU.
What are the best Decky Loader plugins to start with?
SteamGridDB (artwork), CSS Loader (theming), PowerTools (performance), and ProtonDB Badges (compatibility) form an excellent starter stack that covers the four things stock SteamOS cannot do. Add Decky Recorder for clips and MoonDeck for streaming if those fit your workflow. Keep the stack lean – four or five well-chosen plugins beat a dozen you never open.
Does Decky Loader hurt battery life or performance?
The loader itself has negligible overhead. Individual plugins vary – lightweight info plugins are free, while recording and streaming plugins use real resources when active. Ironically, PowerTools can improve battery life by capping CPU power on undemanding games. Run only the plugins you need and the net impact on performance is minimal.
What’s the difference between the stable and prerelease branches?
Stable (release) is the tested, recommended branch – currently v3.2.4 – and what nearly everyone should use. Prerelease carries newer, less-tested features and is for users who hit a stable bug or want bleeding-edge functionality. You can switch between them in Decky’s settings; if prerelease breaks your plugins, switching back to stable is the standard fix.
Do I need a sudo password to install Decky?
Yes. The installer needs elevated privileges and a fresh Steam Deck ships with a blank password that sudo rejects. Set one with passwd in Konsole (Desktop Mode) before running the installer. If a SteamOS update later resets it to blank, you will need to set it again before updating Decky.
How do I completely uninstall Decky Loader?
The easiest way is the “Uninstall Decky Loader” option in Decky’s settings panel. To do it manually, stop and disable the plugin_loader service, remove its service file, delete ~/homebrew, and run systemctl daemon-reload. Reboot and SteamOS returns to stock with no leftovers. Removing a single plugin only requires its uninstall button in the store.
Is Decky Loader free?
Completely. Decky Loader and the plugins in the official store are free and open source, maintained by the SteamDeckHomebrew community. There is no subscription, license, or paywall – the only “cost” is the few minutes it takes to install and the small storage footprint of the loader and your chosen plugins.
Related Coverage
- EmuDeck Tutorial: Steam Deck Emulation in 12 Steps [2026] – pair Decky’s SteamGridDB with a full emulator setup
- Moonlight Game Streaming Setup: 12 Steps, 4K HDR [2026] – the host setup MoonDeck automates
- Playnite Setup 2026: Unify 8 Game Stores in 13 Steps – the desktop equivalent of a unified, themed library
- Steam Deck OLED vs LCD 2026: 90Hz, 1000 vs 400 Nits – which Deck to run your Decky stack on
- Legion Go vs Steam Deck 2026: $1,049 vs $549 [Tested] – Bazzite-on-Legion-Go vs native SteamOS for modding
- Best Cloud Gaming 2026: 5 Services, 4K 240fps vs Free – streaming alternatives to local play
- Mobile & Handheld Gaming 2026 – our full handheld and mobile gaming hub
External resources: Decky Loader on GitHub · Official Decky Installer · Plugin Database · SteamGridDB · ProtonDB
Last updated June 16, 2026. Decky Loader v3.2.4 is the current stable release as of May 28, 2026. Always install the loader from the official SteamDeckHomebrew GitHub repositories linked above – never from a re-hosted mirror.
Sofia Lindström
Sofia Lindström is the Editor-in-Chief at Tech Insider, where she leads editorial strategy and oversees coverage across AI, cybersecurity, and enterprise technology. With over a decade in Swedish tech journalism, she previously served as technology editor at Dagens Industri and covered the Nordic startup ecosystem for Breakit. Sofia holds an MSc in Media Technology from KTH Royal Institute of Technology and is a frequent speaker at Web Summit and Slush. She is passionate about making complex technology accessible to business leaders.
View all articles