Check & Repair Corrupted Game Files on Steam Deck & Linux

Updated 7 November 2026 · Standard formula, shown below

Corrupted game files can cause crashes, freezes, or missing textures on Steam Deck and Linux. This guide walks you through verifying file integrity through Steam’s built-in tools and command-line alternatives, then repairing or re-downloading broken files. You’ll need your Steam account and the game installed; no special tools are required for the standard method.

What You’ll Need

A Steam Deck or Linux PC with Steam installed
The game already installed (so Steam knows its file manifest)
Internet connection (to download missing/corrupted files)
Optional: access to a terminal (for command-line methods)
Optional: a backup of your game saves (good practice before any repair)

Step-by-Step

Back up your save files (especially for games with cloud saves disabled). Copy save folders from ~/.local/share/Steam/userdata/<SteamID>/<AppID>/ or the game’s own save directory to a safe location.
Open Steam on your Steam Deck (Desktop Mode or Gaming Mode) or Linux desktop.
Go to your Library and find the problematic game.
Right-click the game (or press the Steam button on Deck) and select Properties.
In the Properties window, click the Installed Files tab (on Deck, it may be under Local Files).
Click Verify integrity of game files. Steam will compare your files against its manifest and re-download any that are missing or corrupted.
Wait for the process to finish. It may take several minutes for large games.
Once complete, launch the game to test. If it still fails, try the terminal method below.
Terminal method (Linux desktop only): Open a terminal and run steam to ensure the client is running. Then use steam steam://validate/<AppID> (replace <AppID> with the game’s numeric ID from its store page URL) to trigger verification.
For games installed via Proton (Windows games on Linux), you can also delete the game’s pfx folder (usually in ~/.local/share/Steam/steamapps/compatdata/<AppID>/pfx) to reset the Windows environment, but only after confirming your saves are backed up.

Common Mistakes

Skipping the backup: Verification rarely deletes saves, but a crash during repair can corrupt them.
Using the wrong AppID: The AppID is the number in the store URL, not the game’s name or folder name.
Verifying while the game is running: Steam will refuse or fail if the game process is active.
Assuming ‘verify’ fixes all issues: Some problems come from Proton, shader caches, or mods, not the game files themselves.
Deleting the game folder manually: Always uninstall through Steam, or you’ll leave orphaned files that confuse the client.

Tips

If you have mods installed, disable them before verifying – they can be overwritten or cause false mismatches.
On Steam Deck, use Desktop Mode for easier access to file managers and terminals.
For very large games, ensure you have enough free disk space (Steam needs room for re-downloaded files).
Clear the download cache (Steam > Settings > Downloads > Clear Download Cache) if verification stalls.
If the game uses a launcher (e.g., EA App, Ubisoft Connect), verify files inside that launcher as well – Steam may not see those files.

Troubleshooting

Verification never finishes: Restart Steam and try again. If it persists, clear the download cache and restart.
Game still crashes after verification: Try a different Proton version (Properties > Compatibility > Force a specific version). Also try deleting the shader cache (Steam > Settings > Downloads > Shader Pre-Caching > Clear).
Steam says ‘files failed to validate’: This often means a file is locked by another process. Close the game and any overlays, then re-verify.
Disk read errors: Run fsck on your filesystem (from a live USB if necessary) or check SMART status with smartctl. A failing disk can corrupt files repeatedly.
Permission errors: Ensure your user owns the Steam folder: sudo chown -R $USER:$USER ~/.local/share/Steam (adjust path if Steam is elsewhere).
Game is on an NTFS/exFAT drive: Steam on Linux has issues with these filesystems. Move the game to ext4 or btrfs.

Frequently Asked Questions

Will verifying game files delete my saves?

No, verification only checks and repairs game files, not your save data. Saves are stored separately, but backing up is still wise.

How long does verification take?

It depends on the game size and disk speed. A 50 GB game may take 5–15 minutes; an SSD is faster than an HDD.

Can I verify files from the Steam Deck’s Game Mode?

Yes, right-click the game (or press the Steam button) and select Properties > Installed Files > Verify integrity. It works in both modes.

What if the game is not from Steam?

For non-Steam games (e.g., GOG, Epic), use that platform’s own verify tool or reinstall. For Lutris/Bottles, check their respective repair options.

Does verifying fix all crashes?

No. Crashes can also come from outdated drivers, Proton bugs, or hardware issues. If verification doesn’t help, try a different Proton version or check system logs.

Can I repair files without re-downloading?

No, verification will re-download any missing or corrupted files. That’s the only way to ensure integrity.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.