Where Are Steam Screenshots Saved? The Full System and Folder Map

By default, Steam saves screenshots inside your Steam userdata folder at C:\Program Files (x86)\Steam\userdata<YourAccountID>\760\remote<AppID>\screenshots. Press F12 during a game and the file lands there first, then gets uploaded to your Steam Cloud library. The exact path shifts if you installed Steam on another drive, and non-Steam games follow different rules. This guide maps every location, explains the AppID system that governs it, and covers the cases where your screenshots are not where you expect.

How Steam's Screenshot Pipeline Works

Steam does not write screenshots straight to your Pictures folder. The Overlay is the gatekeeper. When you press the capture key, the Steam Overlay process takes a frame from the game's rendering surface, compresses it, and writes a temporary file to disk. The Overlay then hands that file to the Steam client, which files it under your account's userdata directory and queues a Cloud sync if the game supports it.

The path is deterministic because of two identifiers baked into it. The folder is a numeric SteamID, not your display name. The folder is the game's unique store number. Steam groups screenshots by AppID so a single game's captures never mix with another's. That design is why copying screenshots between machines works cleanly: the folder tree mirrors the library.

The files themselves are typically uncompressed or lightly compressed PNG or JPG files. Steam's capture preserves the game's native resolution unless you change it. A 4K display produces 3840×2160 files; a 1080p display produces 1920×1080 files. File size scales with resolution and scene complexity, so a dense 4K screenshot can run several megabytes while a flat 1080p menu shot stays under one.

The Cloud layer is separate from the disk layer. The local file exists immediately after capture. The Cloud copy appears only after the client finishes uploading, which depends on game support and your connection. If you delete the local file before the upload completes, the screenshot is gone. This split between local and Cloud storage is the source of most confusion about where Steam screenshots are saved.

The Exact Paths and the AppID System

There are two path templates, one for Windows and one for macOS and Linux. On Windows the userdata folder sits under the Steam install directory. On macOS it sits inside the Steam application support folder. On Linux it sits under the home directory's Steam data folder.

The AppID is the key you need to find a specific game's screenshots. You can read it from the game's store page URL, which ends in a number. You can also find it in the game's properties dialog under the Updates tab. Once you have the AppID, the folder tree is unambiguous.

The 760 folder is a fixed Steam internal identifier, not a game number. It never changes. The screenshots folder is created lazily, meaning it appears only after the first capture for that game. If you have never pressed F12 in a title, its screenshots folder may not exist yet.

Steam's screenshot manager inside the client is the easiest way to reach the folder. Open the View menu, choose Screenshots, select the game, and use the "Show on Disk" option. That button calls the same path the file system uses, so it is an authoritative check. For a deeper walkthrough of the client features, see Steam's Screenshots documentation, which confirms the userdata layout.

Quantified Context: Sizes, Counts, and Limits

Steam does not cap the number of screenshots you can store locally. The limit is disk space and the Cloud quota. Steam Cloud grants a per-account quota that varies by title and is set by the developer, not a universal number. Some games allow hundreds of megabytes of screenshots; others allow none. You can check a game's Cloud allowance in its properties under the General tab.

Resolution drives file size more than anything else. A typical 1080p PNG screenshot runs 1-3 MB. A 4K PNG can run 6-12 MB depending on content. A 100-screenshot library at 4K can therefore consume roughly 0.6-1.2 GB. That matters on a laptop with a small system drive, which is the most common reason people move the folder.

The 760 directory also stores other Steam data, so it grows steadily. Screenshots are a small fraction of it compared with shader caches and compatibility data. Do not delete the 760 folder wholesale to reclaim space. Target only the screenshots subfolders.

Capture rate is throttled by the Overlay, not by a fixed timer. Rapid repeated presses can drop frames if the game is heavy and the Overlay is mid-write. In practice most users capture a handful at a time, so the practical ceiling is disk space rather than throughput.

Edge Cases: Non-Steam Games, Cloud, and Capture Modes

Non-Steam games are the largest source of "missing" screenshots. When you add a non-Steam shortcut, Steam cannot read the game's AppID because there isn't one. The Overlay files those captures under AppID 0. If you look for the game's name in the userdata tree, you will not find it. This is normal behavior, not a bug.

Steam's built-in screenshot tool is not the only capture method. The operating system and GPU drivers have their own hotkeys. Xbox Game Bar on Windows captures to the Videos\Captures folder. NVIDIA's overlay saves to its own gallery directory. AMD's software has a separate capture folder. A screenshot taken by one of these tools will never appear in Steam's userdata tree, which is why the "where are my screenshots" question often has two valid answers depending on which tool fired.

Cloud sync changes what "saved" means. A screenshot can be visible in the Steam client's library while its local file is missing, because the client is showing the Cloud copy. Conversely, a local file can exist while the Cloud copy is still pending. The two states are independent until sync completes. If a game does not support screenshot Cloud sync, the local file is the only copy.

Sandboxed Linux installs are another trap. Flatpak and Snap builds route the Steam data directory through a sandbox, so the path in the file manager differs from the documented path. The reliable way to find it is the client's "Show on Disk" button, which resolves the sandbox path correctly.

Windows also hides the AppData and ProgramData folders by default. If Steam is installed to a nonstandard location, or if the userdata tree is under a hidden directory, the folder may exist but not be visible in Explorer. Enable hidden items before concluding a folder is missing.

Common Misconceptions

The most persistent myth is that Steam saves screenshots to the Pictures library. That is the default for Xbox Game Bar and for most console platforms, not Steam. Steam's own captures live in userdata. The Pictures folder may contain screenshots, but they came from a different tool.

A second myth is that the folder is named after the game. It is named after the AppID. Users searching for "Elden Ring screenshots" in the file system will not find a folder by that name. Search by AppID, or use the client's manager.

A counterintuitive detail: deleting a screenshot in the Steam client can delete the local file and the Cloud copy in one action, depending on the dialog you confirm. There is no built-in trash for screenshots. The client's delete is permanent unless you backed the file up first. Professional users who archive captures copy them out of the userdata tree before cleaning up the library.

A final misconception is that screenshots are stored per-game on the Cloud in a way you can browse. The Cloud is a sync mechanism, not a browsable file share. The local userdata tree is the only place to inspect files directly.

Red-flag warnings:

Deleting the entire 760 folder to free space also removes shader caches and compatibility data, forcing long rebuilds. Moving the Steam install without using Steam's own library-move tool breaks the userdata path and can orphan local screenshots. Relying on Cloud sync alone risks loss when a game does not support screenshot upload. Using a third-party "screenshot cleaner" on the Steam directory can delete files the client still indexes. Taking screenshots with multiple overlays active at once can cause one tool to intercept the hotkey and write to a different folder.

Practical Actions: Finding, Moving, and Backing Up

Follow these steps in order. Each one resolves a different failure mode, so work top to bottom rather than guessing.

Open the Steam client, go to View, then Screenshots. Select the game and click "Show on Disk." This is the authoritative path check and resolves sandbox and hidden-folder issues. If the folder is empty, confirm the capture actually happened in Steam. Check the client's screenshot manager for the image. If it is there but not on disk, the local file was deleted and only the Cloud copy remains. For non-Steam games, look under AppID 0. If you added the game as a shortcut, that bucket is where its captures live. To free space, copy the screenshots you want to keep to an external drive or a dedicated archive folder, then delete only the files inside the game's screenshots folder. Leave the rest of the userdata tree alone. To move the library to another drive, use Steam's Settings, Storage, and the library-move tool. Do not drag the install folder manually; the userdata path is tied to the install root. To reduce future size, capture at native resolution rather than at a higher internal render scale. Downscaling after capture wastes the space you were trying to save.

The threshold that matters most is disk headroom. Keep at least 10 percent of the system drive free. Screenshot accumulation is slow but steady, and a full system drive degrades the client's ability to write temporary capture files. If you routinely capture at 4K, budget roughly 1 GB per 100 screenshots and archive quarterly.

Limitations and What This Guide Cannot Tell You

The userdata layout is stable across recent Steam client versions, but Valve can change internal folder names in major client updates. The 760 identifier has persisted for years, yet it is an internal detail, not a public contract. Verify with the client's "Show on Disk" button after any major update rather than trusting a static path from an old guide.

Cloud quotas are set per game by developers and are not published in one central table. This guide cannot give you a universal megabyte allowance because no such number exists. Check the game's properties dialog for the current allowance, and treat any fixed number you see online as outdated.

This article is general educational information about software file organization, not technical support for a specific machine configuration. Paths vary with install location, operating system version, and sandboxing. For a machine-specific problem, consult Valve's official Steam Support or a qualified local technician.