How to Show Hidden Files on Steam Deck: Power User Guide

If you bought a Steam Deck expecting a simple handheld console, Valve gave you that. If you flipped it into Desktop Mode expecting a standard PC experience, you probably hit a wall within five minutes trying to find a save file or install a mod.

The entire Linux filesystem on SteamOS relies heavily on hidden files and directories. Without revealing them, crucial directories like .local, .var, and .steam remain invisible, locking you out of Proton prefixes, emulation configurations, shader caches, and game saves.
How to Show Hidden Files on Steam Deck: Power User Guide
Here is the definitive guide to uncovering hidden files across SteamOS, navigating the underlying Arch Linux architecture, and managing your handheld storage without breaking system stability.

The Underlying Mechanism: Why SteamOS Hides Your Files

SteamOS is built on an immutable Arch Linux base running the KDE Plasma desktop environment. In the Unix and Linux world, file visibility is not determined by an arbitrary metadata toggle or a file attribute checkbox like in Windows.

Instead, visibility is governed by a naming convention that dates back to the early days of Unix: the leading dot (.).

  • Any file or folder whose name begins with a period (such as .local or .bashrc) is automatically classified as a "dotfile" and hidden by the operating system.

  • Unix developers originally implemented this convention to keep home directories uncluttered by configuration scripts, caches, and runtime data.

  • Valve utilizes this exact structure to store essential gaming environments, compatibility layers, and application runtimes away from standard user view.

When you run a Windows game on Steam Deck, Proton builds an entire simulated Windows environment—a prefix containing virtual Program Files, users, and System32 directories. That entire structure lives tucked away inside a dotfile directory.

If you cannot see dotfiles, you cannot manually install custom DLLs, swap out save files from non-cloud games, or configure flatpak-based emulator data.

3 Fast Methods to Show Hidden Files in Desktop Mode

Switching to Desktop Mode is your prerequisite step. Press the physical STEAM button on the left side of your Deck, scroll down to Power, and select Switch to Desktop.

Method 1: The Global Keyboard Shortcut (Fastest)

If you have a physical keyboard connected via a USB-C hub or Bluetooth, this is the quickest method available.

  1. Launch the Dolphin file manager from the application launcher or taskbar.

  2. Press Ctrl + H on your keyboard.

  3. Hidden files and directories will appear instantly, rendered with slightly translucent icons to indicate their hidden status.

  4. Press Ctrl + H a second time whenever you want to toggle visibility off.

Method 2: The Dolphin File Manager GUI Menu

For users navigating purely with the Steam Deck trackpads, triggers, and physical controls without an external keyboard attached:

  1. Open Dolphin in Desktop Mode.

  2. Look at the top-right corner of the Dolphin window and click the Hamburger menu (the icon with three horizontal lines).

  3. In the dropdown list, locate the checkbox labeled Show Hidden Files.

  4. Click it once to check the box. Hidden directories will populate immediately across your active view.

Pro Tip: In KDE Dolphin, clicking the hamburger menu every time gets tedious on handheld controls. Click the hamburger icon, select Configure Toolbars..., locate Show Hidden Files in the left panel, and move it to the right panel. This places a dedicated one-click toggle icon right on your main Dolphin navigation bar.

Method 3: The Command Line Interface (Konsole)

For developers, power users, and anyone running setup scripts via SSH or local terminal sessions:

  1. Open Konsole from the SteamOS application menu (under the System category).

  2. To list all files including dotfiles in your current directory, execute:

    Bash
    ls -la
    
  3. To view hidden directories sorted by file size (useful for hunting down bloated shader caches):

    Bash
    ls -lahS
    
  4. If you want to list only the hidden items in a directory:

    Bash
    ls -d .!(|.)
    

Method Comparison: Choosing the Right Approach

MethodTarget Use CaseInput RequirementWorkflow SpeedRisk Factor
Ctrl + H ShortcutQuick toggling during file transfersExternal KeyboardInstant (<1s)Minimal
Dolphin Hamburger MenuPure handheld use with trackpadsBuilt-in Steam Deck ControlsFast (3–5s)Minimal
Dolphin Toolbar PinFrequent modding and configurationBuilt-in Controls / MouseInstant (1-click)Minimal
Konsole (ls -la)Scripting, SSH sessions, bulk diagnosticsVirtual or Physical KeyboardIntermediateLow to Medium
Direct Path NavigationNavigating straight to known prefix IDsClipboard / Address BarFastLow

Critical Hidden Directories Every Deck User Must Know

Once you enable hidden files, the deck home directory (/home/deck/) reveals several system-critical paths. Knowing where specific game data resides saves hours of blind searching.

/home/deck/
├── .local/
│   └── share/
│       └── Steam/
│           └── steamapps/
│               ├── compatdata/       <-- Proton Windows Prefixes (Game Saves, C-Drive)
│               ├── common/           <-- Native Game Install Directories
│               └── shadercache/      <-- Pre-compiled Graphics Shaders
├── .var/
│   └── app/                          <-- Flatpak Application Data (Emulators, Chrome, Discord)
└── .config/                          <-- KDE Desktop & System Configuration Files

1. The Proton Compatibility Directory (compatdata)

  • Path: /home/deck/.local/share/Steam/steamapps/compatdata/

  • Inside this folder, every non-native Windows game installed via Steam has its own numerical AppID folder.

  • Inside any specific AppID folder, navigating to pfx/drive_c/users/steamuser/ brings up the simulated Windows user directory containing AppData, Saved Games, and Documents.

2. Flatpak Sandboxes (.var/app)

  • Path: /home/deck/.var/app/

  • Applications installed through the Discover store (like RetroArch, PCSX2, RPCS3, heroic games launcher, or web browsers) run sandboxed inside Flatpak containers.

  • Their custom configs, bios mappings, and persistent save states live directly within their designated .var/app/[app.identifier] folders.

3. Shader Cache Repository (shadercache)

  • Path: /home/deck/.local/share/Steam/steamapps/shadercache/

  • Houses the pre-compiled DirectX and Vulkan pipelines downloaded by Steam to prevent in-game frame hitching.

  • Useful to inspect when diagnosing SSD storage bloat from games you have previously uninstalled.

Hands-On Workflows: Modding, Saves, and Emulation

Workflow A: Transferring Offline PC Saves to Steam Deck

Many older or non-cloud-enabled games do not sync game progression through Steam Cloud. Manually moving saves requires navigating the virtual Windows directory structure.

  1. Turn on Show Hidden Files in Dolphin.

  2. Look up the targeted game's Steam AppID on steamdb.info (for example, The Witcher 3 is 292030).

  3. Navigate to /home/deck/.local/share/Steam/steamapps/compatdata/292030/pfx/drive_c/users/steamuser/Documents/The Witcher 3/gamesaves/.

  4. Copy your .sav files from your desktop PC directly into this directory using a USB drive, local network share, or KDE Connect.

  5. Launch the game in Gaming Mode; your save files will register immediately.

Workflow B: Installing Custom Mods (Nexus / Manual Drops)

Modding games like Cyberpunk 2077, Fallout: New Vegas, or Elden Ring often demands dropping .dll, .asi, or script files straight into the executable folder.

  1. Reveal hidden files in Dolphin.

  2. If the mod requires configuration files placed inside the user profile, open /home/deck/.local/share/Steam/steamapps/compatdata/[AppID]/pfx/drive_c/users/steamuser/AppData/Roaming/.

  3. Drop the respective mod config files into place.

  4. If an override DLL is needed, open Steam in Desktop Mode, right-click the game, select Properties, and add WINEDLLOVERRIDES="modfilename=n,b" %command% into the Launch Options field.

Pro Tip: If you frequently manage mods across multiple titles, avoid manually drilling down through the nested .local/share/Steam/steamapps/ structure. In Dolphin, navigate to the compatdata directory once, then drag the folder icon into the Places sidebar on the left. This creates a persistent quick-access bookmark that survives reboots.

Real-World Limitations, Hazards, and Edge Cases

Unrestricted access to hidden configuration directories gives you absolute control, but it also exposes key platform vulnerabilities on SteamOS.

1. Accidental Deletion of Proton Environments

Deleting an AppID folder inside compatdata completely destroys the simulated Windows drive_c. If the game did not feature cloud sync, your local saves, graphics presets, and mod engines are permanently lost.

2. Flatpak Isolation Hurdles

Some apps installed from the Discover store cannot browse hidden folders by default due to strict sandbox permissions.

  • If an emulator file picker fails to display your .local or .var folders even after enabling them in Dolphin, the emulator itself lacks filesystem access permissions.

  • Install Flatseal from the Discover store to manage permissions.

  • Open Flatseal, select the target application, scroll to Filesystem, and grant access to All user files (filesystem=host).

3. Read-Only Root Filesystem (steamos-readonly)

While showing hidden files in /home/deck/ allows modifying user configs, modifying system files outside the user scope (like in /etc or /usr) is blocked by SteamOS's read-only root architecture.

  • Avoid disabling steamos-readonly simply to adjust app behavior.

  • Keep all your configuration overrides, scripts, and mod installations contained strictly inside /home/deck/.

  • Any modifications made outside the home partition get wiped whenever Valve pushes a major SteamOS system update.

Troubleshooting Common Issues

"Show Hidden Files" Keeps Turning Off After Reboot

Dolphin preserves its view configuration per directory or globally based on your profile preferences.

  1. Open Dolphin.

  2. Click the top-right hamburger menu and select Configure Dolphin...

  3. Navigate to the View Modes tab on the left.

  4. Ensure your view preferences are applied globally rather than set to remember custom properties per directory.

Cannot Find the AppID for a Non-Steam Game

When you add a non-Steam game executable manually via Desktop Mode, Steam generates a random, massive 10-digit ID instead of a standardized store AppID.

  • To locate it quickly, sort the /home/deck/.local/share/Steam/steamapps/compatdata/ folder by Date Modified.

  • Launch your non-Steam game once in Gaming Mode, exit it, immediately return to Desktop Mode, and inspect the newest folder created in compatdata.

Frequently Asked Questions

Will showing hidden files impact my Steam Deck gaming performance?

No. Revealing dotfiles is strictly a file-manager rendering toggle within the KDE Plasma desktop environment. It does not consume background CPU cycles, alter memory consumption, or affect frame rates in Gaming Mode.

How do I hide the files again?

Use the same toggle mechanism: press Ctrl + H in Dolphin, or uncheck Show Hidden Files in the Dolphin menu. The files will instantly disappear from the view while remaining fully functional on the system.

Can I view hidden files on my MicroSD card?

Yes. MicroSD cards mounted on the Steam Deck are located at /run/media/mmcblk0p1/. Once mounted, toggling hidden files with Ctrl + H will expose any hidden directories on the storage card (including .Trash-1000 or custom config paths).

Why do some folder names turn slightly faded when revealed?

KDE Dolphin visually dims the opacity of dotfile folder icons to distinguish normal directories from system-hidden directories. This visual treatment is normal behavior to help users avoid moving or deleting configuration paths by mistake.

Gaining comfortable access to the Steam Deck filesystem shifts the device from a sandboxed gaming appliance to a full-fledged portable computer. The system architecture Valve designed relies on Linux standards that reward curious users. Once you map out where the critical dotfiles live and how Proton isolates runtimes, customizing saves, tweaking configuration files, and managing emulators becomes just as straightforward as working on a traditional desktop rig.