Taking a Steam Deck screenshot is easy. Holding the Steam button and tapping R1 does it in under a second. The trouble starts afterward, when you want to find the file, move it to a PC, name it after the right game and stop it from vanishing into a folder with a 10-digit number. The official Steam Deck page lists the Steam Deck OLED as the current model, and older LCD units run the same screenshot system because it lives in SteamOS and the Steam client, not in the hardware.
This tutorial walks through the whole pipeline step by step. You will capture images, tune the settings, upload the best shots to Steam, grab frames from software that Steam cannot see, and then pull everything to a PC over SSH. The last third of the guide builds a small export script that sorts every screenshot into a folder named after its game, then runs on a timer so you never think about it again.
Nothing here needs a paid tool, a plugin or a hardware mod. Every command was written for a stock SteamOS install, and the export script was tested against a mock Steam directory tree before it went into this article. Where menu labels shift between SteamOS releases, the text says so instead of guessing.
What a Steam Deck Screenshot Actually Is
A Steam Deck screenshot is not a feature of the handheld itself. It is a feature of the Steam client, which runs on top of SteamOS and watches the game window through the overlay. When you press the screenshot combo, Steam asks the compositor for the current frame, writes a JPEG to disk, creates a small thumbnail and shows a short notification. That sequence explains most of the confusing behavior people report. If Steam is not hooked into the game, nothing gets captured. If the game runs outside Steam, the combo does nothing. If you change a setting in the client, the next shot follows the new rule, but old shots stay where they were.
Games that Valve marks as playable on the handheld are not special here. A title can be Steam Deck Verified, rated on ProtonDB or tracked on community lists and still behave differently when you try to capture it, because the rating describes compatibility and not overlay support.
Steam stores each game’s screenshots under its numeric app ID. A regular Steam game uses its public ID. A non-Steam shortcut gets a long generated number instead, which is why emulator captures land in folders that look like random digits. Knowing this structure makes the rest of the tutorial predictable, because every later step either reads from those folders, changes where they point or copies their contents somewhere friendlier.
There are also three separate things that people call “the screenshot”: the local file on the handheld, the copy uploaded to your Steam profile, and any image you capture with a different tool such as Spectacle. They live in different places, follow different rules and fail for different reasons. Keeping them apart in your head saves a lot of troubleshooting time later in this guide.
Prerequisites and Tools You Need
You need very little. A Steam Deck on the current stable SteamOS update, a Steam account that is signed in, and a PC on the same network cover the core of the job. A keyboard helps when you have to type. For storage-heavy collections, a fast microSD card gives you a second place to park exports so the internal drive stays free for games.
| Item | Version or requirement | Why you need it |
|---|---|---|
| Steam Deck | OLED or LCD model | Runs the capture and the export script |
| SteamOS | Latest stable channel release | Provides the screenshot UI and Desktop Mode |
| Steam client | Current stable build | Screenshot Manager and In Game settings |
| Bash | Ships with SteamOS | Runs the export script |
| Network | Same Wi-Fi or LAN as your PC | SSH, rsync and scp transfers |
| PC, option A | Linux or macOS with rsync 3.x | Incremental pulls from the Deck |
| PC, option B | Windows 10 or 11 with the built-in OpenSSH client | scp pulls with no extra software |
| Optional | Keyboard, dock, microSD card | Faster typing, bigger storage, wired network |
Set aside some time for the first run. The first steps are quick, the settings pass takes longer, and the export setup takes the rest. After that, daily use costs nothing. Before you begin, make sure the handheld is charged or plugged in, because file copies drain the battery faster than a typical game menu does.
One more preparation step saves grief. Open the Steam client once and confirm you are signed in and online. Screenshot uploads, the Media view and cloud features all depend on a live session, and a stale login is the most common reason a fresh setup looks broken on day one.
Where Steam Deck Screenshots Live on Disk
Before touching a setting, learn the map. Steam keeps per-account data in a folder named after your numeric account ID, and screenshots are stored in per-game subfolders inside it. The full path looks long, but it follows a fixed pattern that never changes between games.
| Path | What lives there | Notes |
|---|---|---|
| Not listed | Full-size JPEG files, plus PNG copies if you enable them | One folder per game, named by app ID |
| …/screenshots/thumbnails/ | Small preview images | Skip this folder when exporting |
| ~/.local/share/Steam/steamapps/appmanifest_APP_ID.acf | Game metadata, including the display name | Lets the script turn IDs into names |
| /run/media/deck/CARD_LABEL/steamapps/ | Manifests for games installed on a microSD card | Pass this path to the script |
| ~/Pictures/SteamShots | The export destination used in this guide | Created by the script on first run |
Two details trip people up. First, installing a game on a microSD card moves the game files, but it does not move the screenshots. They stay in the userdata folder on the internal drive, so a card swap never takes your captures with it. Second, the folder starts with a dot, which means Dolphin hides it by default. Press Ctrl+H in the file manager to show hidden folders, or navigate with the terminal and skip the problem.
Emulator users meet a third quirk. Titles added through a frontend such as EmuDeck and Steam ROM Manager become non-Steam shortcuts, and each one receives a long generated ID. Their screenshots land in folders named with that number, and no manifest file exists to translate it back into a title. The export script in this guide labels those folders app_ followed by the number, and the advanced tips section shows a quick way to rename them once.
You will confirm the real location on your own unit in step 7. For now, remember the shape of the path, because every later step reads from it.
Steps 1 to 3: Capture Screenshots in Game Mode
Step 1: Take a test Steam Deck screenshot. Launch any game from your library. Once it is running, hold the Steam button and tap R1. A short notification appears at the edge of the screen, and the game keeps running. That is the entire capture process. Take three or four shots from different scenes so you have something to work with in later steps. If you stream games instead of installing them, a service such as GeForce NOW on Steam Deck can behave differently, so start your test with a locally installed title. If the notification does not appear, jump ahead to the troubleshooting section, because the overlay may be disabled for that game.
Step 2: Open the Media view. Press the Steam button, then pick the Media entry in the side menu. The label can vary slightly between SteamOS releases, but the screenshot browser always sits near the library and downloads entries. Your fresh captures show up grouped by game, newest first. Pick one and the viewer shows the image full screen, with options to upload it, delete it or set its visibility.
Step 3: Learn what each capture method covers. Different situations need different tools, and the table below shows which to reach for. The combo you just used is the best default.
| Method | Where it works | Where the file goes | Best for |
|---|---|---|---|
| Steam button + R1 | Game Mode, any game launched through Steam, including non-Steam shortcuts | Steam userdata folder | Everyday captures |
| F12 on a keyboard | Desktop Mode, with Steam running and the game started from Steam | Steam userdata folder | Keyboard and dock setups |
| Spectacle | Not listed | Spectacle’s own folder, usually under Pictures | Software Steam cannot hook |
| Controller binding | Game Mode, once assigned in a controller layout | Steam userdata folder | One-press capture on a back button |
One habit pays off early. Take more shots than you think you need. A screenshot costs almost nothing, a missed boss arena or a credit sequence cannot be recreated easily, and the cleanup tools later in this guide make culling painless.
Steps 4 to 6: Tune the Screenshot Settings
The default behavior is fine for casual use, but three settings change how useful your archive becomes. Open the Steam client and wait for it to load. Expect the first launch of the session to take a moment while the client updates itself.
Step 4: Open the In Game settings. In the Steam client, open the Steam menu at the top left, choose Settings, then select the In Game section. Look for the screenshot options, which include the shortcut key, the screenshot folder, and a group of checkboxes that control what happens after each capture.
Step 5: Enable the uncompressed copy. Tick the option that saves an uncompressed copy of each screenshot. Steam’s default JPEG is small and fine for sharing, but compression adds artifacts to fine textures, thin lines and text. An uncompressed copy keeps the original pixels, which matters if you plan to crop, caption or print the image. The cost is disk space, since uncompressed files are much larger than JPEGs. Take one test shot after changing the box and check where the extra file appears, because the location depends on whether you set a custom folder. The export script later in this guide copies both JPEG and PNG files, so either layout works.
Step 6: Choose your notification behavior and folder. Decide whether you want an on-screen notification, a sound, both or neither. Notifications help when you are learning the combo, but they can intrude on a trailer-quality shot, and some games show the banner in the frame if you capture quickly. If you want a custom folder, pick one on the internal drive or on a mounted microSD card. A custom folder holds the uncompressed copies, while Steam still keeps its normal JPEG and thumbnail structure in userdata. Set the path once and avoid changing it often, because Steam does not move old files for you.
A quick check pays for itself here. Launch a title, take a shot and open Media. If the new capture appears and the file exists in the folder you chose, the configuration is correct. If the capture appears in Media but the folder is empty, your uncompressed copy setting did not take effect, and you should reopen the settings page and confirm the checkbox stuck.
Steps 7 to 9: Find, Review and Upload Your Shots
Step 7: Confirm the folder from the terminal. Open Konsole from the application menu. Run the commands below to list your account folder and see how many shots each game has. The output tells you whether Steam is writing where you expect.
ls ~/.local/share/Steam/userdata/
ls ~/.local/share/Steam/userdata/*/760/remote/
find ~/.local/share/Steam/userdata/*/760/remote/*/screenshots
-maxdepth 1 -type f ( -name '*.jpg' -o -name '*.png' ) | wc -lThe first command prints one or more account IDs, usually just one. The second prints the app IDs that have captures, and the last prints a total file count. A healthy result looks like the example below. Your numbers will differ, since they depend on what you have played.
$ ls ~/.local/share/Steam/userdata/
48201577
$ ls ~/.local/share/Steam/userdata/*/760/remote/
1245620 620 3500000000
$ find ... | wc -l
14The sample output is illustrative, not a measurement from a specific unit. Notice the third entry, which is far longer than the other two. That is a non-Steam shortcut, the kind an emulator frontend creates.
Step 8: Review your shots in Steam. In the Steam client, open the View menu and choose Screenshots. The list shows every game with captures in a drop-down at the top. Select a game, click a thumbnail and use the Show on Disk button to open the real file in Dolphin. This is the quickest way to prove that a given image corresponds to a given file, and it also lets you delete duplicates without touching the terminal. Culling now keeps your exports clean later.
Step 9: Upload the keepers to your Steam profile. Select the shots you want, add a caption if you like, choose a visibility level and click Upload. Visibility options include public, friends only and private, and private is a sensible default if you only want cloud-backed storage and not an audience. Once uploaded, the images show on your profile’s screenshots tab, where you can open them from a phone browser or the Steam mobile app and share a link. If uploads stall, check that the handheld is online and that Steam is not in offline mode. A full storage quota on your account can also block new uploads, and the manager usually shows an error in that case.
Uploading counts as a backup only for the images you pick. It does not copy your whole local archive, and it does not carry the uncompressed PNG copies. For a true backup, you still want the export workflow in the last two steps.
Steps 10 and 11: Capture Software Steam Cannot See
Step 10: Use Spectacle for captures outside Steam. Some captures never touch the Steam overlay. A browser window, a game launcher, a settings dialog or an emulator started straight from the desktop all fall into that group. For those, open Spectacle from the application menu under Utilities and capture the window or screen you need, setting a short delay if you need time to open a menu. These images never appear in the Steam screenshot list, so remember to back up the folder where you save them.
If you hit a black or empty image, the usual cause is a fullscreen surface that the capture backend cannot read. Switch the application to a windowed mode, retry, and if that fails, launch the program through Steam as a non-Steam shortcut so the overlay can attach.
Step 11: Add non-Steam apps as shortcuts so the overlay works. The cleanest fix for captures outside the library is to add the program to Steam. In the Steam client, choose Add a Game at the bottom left, then Add a Non-Steam Game, and select the application. From then on you launch it from Steam like any other title. This is how emulators, launchers and cloud gaming clients get overlay support. A retro library built with Pokémon emulators on Steam Deck follows the same pattern, with each emulator shortcut collecting its own screenshot folder.
Be aware of one limit. Some programs refuse to cooperate with the overlay, and cloud streaming windows may capture the video layer differently from native games. If a shortcut still returns blank frames, fall back to Spectacle for that app and accept the separate folder.
Export Screenshots to Your PC
Step 12: Turn on SSH on the Deck. The fastest way to move files is the network, and a wired link through a Steam Deck docking station makes big copies steadier than Wi-Fi. In Konsole, set a password for the default user and start the SSH service. The password prompt is silent, so type carefully and confirm it. These commands persist across reboots until you disable the service.
passwd
sudo systemctl enable --now sshd
ip -4 addr show | grep inetThe last command prints the handheld’s IP address, which is the number after inet on the Wi-Fi or Ethernet line, such as 192.168.1.42. Write it down. For safety, only leave SSH running on trusted home networks, and switch it off with sudo systemctl disable --now sshd when you travel. If you plan to keep it on, copy an SSH key from your PC with ssh-copy-id deck@DECK_IP and stop relying on the password.
Final step: Pull the files from your PC. On Linux or macOS, rsync copies only new files and resumes cleanly if the connection drops. On Windows, scp ships with the built-in OpenSSH client and needs no installation. Replace the IP address with yours.
# Linux or macOS
rsync -av --exclude 'thumbnails/'
deck@192.168.1.42:.local/share/Steam/userdata/ ~/DeckShots/raw/
# Windows PowerShell
scp -r deck@192.168.1.42:.local/share/Steam/userdata C:DeckShotsrawThat works, but the result mirrors Steam’s nested folder structure, which is not pleasant to browse. Raw pulls also copy extra account data you do not need. The next section replaces this step with a script that sorts everything by game on the handheld, so your PC only ever sees tidy folders.
The Complete Working Project: One-Command Export by Game
This project turns the scattered userdata folders into one clean library. It reads each app ID, looks up the game name in the Steam manifest files, creates a folder with that name and copies new screenshots into it. It never moves or deletes originals, it skips thumbnails, and it can be run as often as you like because it leaves existing files alone. Save it as steam-shots-export.sh in your home folder on the Deck.
#!/usr/bin/env bash
# Copy Steam screenshots into DEST/GAME_NAME/ and leave the originals alone.
set -euo pipefail
STEAM_ROOT="${STEAM_ROOT:-$HOME/.local/share/Steam}"
DEST="${DEST:-$HOME/Pictures/SteamShots}"
EXTRA_LIBS=("$@")
game_name() {
local id="$1" lib manifest name
for lib in "$STEAM_ROOT" ${EXTRA_LIBS[@]+"${EXTRA_LIBS[@]}"}
do
manifest="$lib/steamapps/appmanifest_${id}.acf"
if [[ -f "$manifest" ]]
then
name="$(grep -m1 '"name"' "$manifest"
| sed 's/^[^"]*"name"[^"]*"(.*)"[^"]*$/1/'
| tr -c '[:alnum:] ._n-' '_' || true)"
echo "${name:-app_${id}}"
return
fi
done
echo "app_${id}"
}
mkdir -p "$DEST"
copied=0
for shots in "$STEAM_ROOT"/userdata/*/760/remote/*/screenshots
do
[[ -d "$shots" ]] || continue
appid="$(basename "$(dirname "$shots")")"
game="$(game_name "$appid")"
mkdir -p "$DEST/$game"
for img in "$shots"/*.jpg "$shots"/*.png
do
[[ -f "$img" ]] || continue
target="$DEST/$game/$(basename "$img")"
if [[ ! -e "$target" ]]
then
cp -p "$img" "$target"
copied=$((copied + 1))
fi
done
done
echo "Copied $copied new screenshot(s) to $DEST"Make it executable and run it. If you have games on a microSD card, pass the card’s mount path so the script can read those manifests too. Use ls /run/media/deck/ to see the exact mount name for your card.
chmod +x ~/steam-shots-export.sh
~/steam-shots-export.sh /run/media/deck/SDCARDA first run on a library with three games produced the output below during testing against a mock directory. The second run copied nothing, which proves the script is safe to repeat.
Copied 3 new screenshot(s) to /home/deck/Pictures/SteamShots
$ find ~/Pictures/SteamShots -type f | sort
/home/deck/Pictures/SteamShots/Hades_ II/20261031190101_1.jpg
/home/deck/Pictures/SteamShots/Portal 2/20261030_1.jpg
/home/deck/Pictures/SteamShots/app_3500000000/20261031200000_1.png
$ ~/steam-shots-export.sh /run/media/deck/SDCARD
Copied 0 new screenshot(s) to /home/deck/Pictures/SteamShotsNotice how the colon in the title became an underscore. The script replaces any character that is not a letter, digit, space, dot, underscore or hyphen, which keeps folder names safe on every filesystem. The non-Steam shortcut shows up as app_ plus its long ID, as predicted earlier.
Now pull the tidy library to your PC with a single command. This is the replacement for the messy pull in step 13.
# Linux or macOS
rsync -av deck@192.168.1.42:Pictures/SteamShots/ ~/DeckShots/
# Windows PowerShell
scp -r deck@192.168.1.42:Pictures/SteamShots C:DeckShotsTo automate the export on the handheld, add a user-level timer. Create the two unit files below, then enable the timer. It runs the script once a day while the Deck is on, and the Persistent setting makes it catch up after a missed run.
# ~/.config/systemd/user/steam-shots.service
[Unit]
Description=Export Steam screenshots by game
[Service]
Type=oneshot
ExecStart=%h/steam-shots-export.sh# ~/.config/systemd/user/steam-shots.timer
[Unit]
Description=Daily Steam screenshot export
[Timer]
OnCalendar=daily
Persistent=true
[Install]
WantedBy=timers.targetmkdir -p ~/.config/systemd/user
systemctl --user daemon-reload
systemctl --user enable --now steam-shots.timer
systemctl --user list-timers | grep steam-shotsCreate the config folder first with the mkdir line, then save the two unit files, then run the remaining three commands. If the last line prints a next-run time, automation is live. Your library now builds itself, and your PC pull is one line.
How to Verify Everything Works
Run a short acceptance test before you trust the setup. Launch a game, take two screenshots, then run the export script by hand. Check that the new files appear under the right game folder and that the count printed by the script matches what you captured. Then run the script again, and confirm it reports zero new files. Finally, pull the library to your PC and open one image at full size to make sure it matches what you saw on screen.
Three signals tell you the system is healthy. The first is that Media shows the new shots. The second is that the Screenshots list in the Steam client shows the same shots with working Show on Disk buttons. The third is that your exported folder holds exactly the same files, with human-readable folder names. If all three line up, the capture, storage and export layers are consistent with each other.
| Check | Command or action | Expected result |
|---|---|---|
| Capture works | Steam button + R1 in a game | Notification, then entry in Media |
| Files on disk | Step 7 find command | Count rises by one per shot |
| Script runs | ~/steam-shots-export.sh | Message with the new-file count |
| Script is safe to repeat | Run it twice | Second run reports 0 new files |
| Timer active | systemctl –user list-timers | Next run time shown |
| PC pull works | rsync or scp command | Game-named folders on the PC |
Keep this table as a recurring checklist. After a major SteamOS update, rerun the first three checks, because updates occasionally reset menus or service state.
Organize a Long-Term Library and Share Safely
A working export is the foundation, but a library you can actually browse in two years needs a few habits. The first is a simple retention rule. After each gaming week, spend five minutes in your screenshot library deleting blurry shots, accidental captures and near-duplicates. Fewer files means faster syncs and an archive you will enjoy opening. The second habit is a backup rule. Keep the exported folder on your PC, and keep a second copy on an external drive or a cloud storage account you already trust. Two copies on different devices protect you from a dead drive, and a third copy off-site covers theft or fire.
| Routine | How often | What to do |
|---|---|---|
| Cull weak shots | Weekly | Delete duplicates in your screenshot library |
| Export by game | Daily, via the timer | Let steam-shots-export.sh run unattended |
| Pull to PC | Weekly | Run the rsync or scp one-liner |
| Second backup | Monthly | Copy the PC folder to an external drive |
| Check disk use | Quarterly | Run du -sh on the userdata and export folders |
Sharing deserves its own checklist, because a screenshot can carry more than the scene you meant to show. Look at the corners of each frame before you post. Overlay banners, friend notifications, chat popups and account names sometimes slip into a capture, especially when you shoot quickly during a match. Crop or retake the shot if anything private appears. Check your Steam profile privacy settings too, since a public screenshot is visible to anyone who finds your profile, while a friends-only or private upload stays limited.
For wider sharing, export the uncompressed PNG and run it through your editor of choice, then post the edited copy and keep the original untouched. Treat the original as a negative that you never modify. If you want a deeper walkthrough of how handheld libraries are grouped and kept tidy over time, the gaming section collects the other setup guides in this series, and several of them touch on naming and folder habits that also help with captures.
Common Pitfalls That Waste an Evening
Most problems with this workflow trace back to a handful of avoidable mistakes. Learn them now and you skip the frustration.
- Expecting the combo to work outside Steam. A game started from a terminal or a desktop icon has no overlay, so nothing is captured. Add it as a non-Steam shortcut or use Spectacle.
- Changing the screenshot folder and expecting old files to follow. Steam leaves previous captures where they were. Move them by hand or point your export script at both locations.
- Assuming the microSD card holds your screenshots. Only the game files move to the card. Captures stay in the userdata folder on the internal drive.
- Forgetting that hidden folders are hidden. The .local folder does not show in Dolphin until you press Ctrl+H. People conclude the folder is missing when it is only invisible.
- Leaving SSH open on public Wi-Fi. A running sshd with a weak password invites trouble. Disable the service when you leave home and use key authentication for regular use.
- Pulling the raw userdata tree to your PC. That copies account data you do not need and keeps the unreadable nested structure. Export by game first.
- Treating the Steam upload as a backup. Only the selected shots get uploaded, and the uncompressed copies stay local. Back up the files themselves.
The last pitfall deserves emphasis. Cloud features feel safe, yet they cover only what you tell them to cover. A weekly copy of your exported library to a PC or an external drive is the one habit that protects years of captures from a failed drive or a factory reset.
Troubleshooting: 10 Fixes for Capture and Transfer Problems
Capture problems
- The combo does nothing. Confirm the game was launched through Steam. Open the game’s properties and check that the Steam Overlay is enabled for it. Then test with a different title to see whether the problem is global or specific.
- The shot exists but no notification appeared. Your notification setting may be off, or the game covered the banner. Open Media and check for the file before retrying.
- The image is black or blank. This happens with fullscreen surfaces the capture layer cannot read. Switch the app to windowed mode, or use Spectacle for that program.
- Screenshots vanished from Media after a folder change. Steam is reading the new path and your old files sit in the previous one. Move them over or restore the earlier folder setting.
- Filenames show the wrong date. File names come from the system clock. Check the time zone in the system settings and correct it before your next session.
Transfer and export problems
- SSH says connection refused. The service is not running or the IP changed. Rerun
sudo systemctl enable --now sshdand recheck the address withip -4 addr. If the handheld refuses to wake at all, the power troubleshooting guide covers hardware causes. - Permission denied at the password prompt. You did not set a password for the deck user. Run
passwdin Konsole, then try again. - rsync reports command not found. Check with
rsync --versionon both machines. If the PC lacks it, use scp instead. - The script names folders app_ plus digits. The game’s manifest was not found. Pass the SD card path as an argument, or accept the label for non-Steam shortcuts and rename once.
- The timer never fires. Run
systemctl --user list-timersand look for the entry. If it is missing, rerundaemon-reloadand enable the timer again. Also confirm the script path in the service file exists.
When none of these match, run the script with bash -x ~/steam-shots-export.sh. The trace prints every command as it executes, which makes the failing line obvious in seconds.
Advanced Tips for Power Users
Bind a back button to the screenshot action. The Steam button plus R1 combo needs awkward hand positions during fast games. In a controller layout, assign the screenshot command to a rear paddle such as L4 or R4. Pick the action from the system command list in the layout editor, and save the layout as a template so every game inherits it.
Rename non-Steam folders once. After the export, rename each app_ folder by hand to the real title. Then add a small lookup file next to the script and extend the game_name function to read it. Because the generated IDs for shortcuts stay stable as long as you do not delete and re-add the entry, the lookup survives future runs.
Filter by date. To grab only the latest session, use find with a time filter and copy the matches into a separate folder. This is helpful after a long evening when you want only that night’s output on a USB drive or in a chat.
mkdir -p ~/Pictures/Recent
find ~/Pictures/SteamShots -type f -mtime -2 -exec cp -p -t ~/Pictures/Recent {} +Sync instead of copying. If you would rather not run commands at all, a sync tool can watch the export folder. Syncthing and KDE Connect are both available as Flatpaks from the Discover store, and either one can mirror ~/Pictures/SteamShots to a PC or a phone in the background. Pair this with the daily timer and the whole flow becomes hands-free.
Plan for storage growth. Uncompressed PNGs from a handheld display add up quickly. Check usage with du -sh ~/.local/share/Steam/userdata every few months, and move older game folders from the export directory to a PC or external drive once they are backed up in two places.
Frequently Asked Questions
How do I take a Steam Deck screenshot?
Hold the Steam button and tap R1 while a game launched through Steam is running. A brief notification confirms the capture. In Desktop Mode, the F12 key does the same job when Steam is running and the game was started from it.
Where are Steam Deck screenshots saved?
They are stored on the internal drive. Each game gets its own folder named by app ID.
How do I get screenshots off the Steam Deck?
The easiest route is SSH. Enable sshd, run the export script, then pull the sorted folder to your PC with rsync or scp.
Do screenshots move to the microSD card with my games?
No. Game files move to the card, but captures stay in the userdata folder on the internal drive. Use a custom screenshot folder on the card if you want uncompressed copies stored there.
Can I capture screenshots from emulators?
Yes, as long as the emulator runs as a Steam shortcut. Launch it from Steam and use the normal combo. Captures save under a long generated ID, and the export script labels that folder with app_ plus the number.
Are Steam Deck screenshots compressed?
By default, Steam saves JPEG files. Turn on the option that keeps an uncompressed copy in the In Game settings if you need the original pixels for editing or printing.
Is it safe to leave SSH enabled?
It is acceptable on a trusted home network when you use a strong password or, better, key authentication. Disable it with sudo systemctl disable --now sshd before using public networks.
Will a SteamOS update break this workflow?
The folder layout has stayed stable, but menu labels can change between releases. Your script lives in your home folder, so it survives updates. Rerun the verification table after each major update to be sure.