Screenshot on Windows 11: every method, and which one to use
Snipping Tool, Win+Shift+S, PrtScn, Win+PrtScn, Game Bar and PowerShell capture — what each one does to the clipboard, the file and the screen.
- Build
- 26300.9457
- Edition
- Pro (26H2)
- Architecture
- x64
- Support
- Documentation (E1)
- Evidence
- E1Official documentation
- Verified
- 2026-10-29
- Page type
- Task
The short answer
Section titled “The short answer”Five ways, and they are not interchangeable:
| Shortcut | Goes to | Saved automatically | Best for |
|---|---|---|---|
Win + Shift + S |
clipboard (+ Snipping Tool editor) | no | the everyday case |
PrtScn |
configured in Settings | depends | keyboards with the key |
Win + PrtScn |
Pictures\Screenshots |
yes | full screen to a file |
Alt + PrtScn |
clipboard | no | the active window only |
Win + G → capture |
Videos\Captures |
yes | games, video |
If nothing happens when you press PrtScn, the key is either remapped or Snipping Tool’s “use PrtScn” toggle is on — both are settings, not a broken keyboard.
Win + Shift + S: the one to learn
Section titled “Win + Shift + S: the one to learn”It opens the snipping overlay and dims the screen:
| Mode | Shortcut inside the overlay |
|---|---|
| Rectangle | default |
| Window | W |
| Full screen | F |
| Freeform | D |
The result lands on the clipboard and, in current builds, opens in Snipping Tool where you can annotate, crop, or save. Paste into any app with Ctrl + V.
# is the Snipping Tool installed?Get-AppxPackage Microsoft.ScreenSketch | Select-Object Name,Version,Status# where do auto-saved screenshots go?(Get-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders').'{B7BEDE81-DF94-4682-A7D8-57A7170B3C24}'That GUID is My Pictures; screenshots from Win + PrtScn land in its Screenshots subfolder.
Why PrtScn “does nothing”
Section titled “Why PrtScn “does nothing””Three causes, in order:
- Snipping Tool has claimed the key. Snipping Tool → Settings → Use the Print screen key to open Snipping Tool — when on,
PrtScnbehaves likeWin + Shift + S. - The key is remapped by the OEM or by PowerToys Keyboard Manager.
- A laptop requires
Fn— tryFn + PrtScn.
Registry-wise, the Snipping Tool toggle lives under HKCU\Control Panel\Keyboard (PrintScreenKeyForSnippingEnabled). Setting it to 0 restores the classic behaviour.
Screenshots of things that refuse to be captured
Section titled “Screenshots of things that refuse to be captured”Some windows come out black or empty:
| Content | Why |
|---|---|
| DRM video (Netflix, some Blu-ray players) | protected output |
| UAC / secure desktop | different desktop |
| Some games in exclusive fullscreen | bypasses DWM composition |
| Windows Sandbox window | isolated session |
Workarounds: run the game in borderless windowed, or capture on the host rather than inside a VM/sandbox. For DRM content there is no legitimate workaround — that is the point of the protection.
Long pages and scrolling windows
Section titled “Long pages and scrolling windows”Win + PrtScn captures only what is on screen. For a full scrolling page:
- Browser: DevTools (
F12) →Ctrl + Shift + P→ Capture full size screenshot. - Snipping Tool: Delay (3/5/10 s) to open menus before the capture fires.
- Whole document: print to PDF instead of stitching images.
Automating capture
Section titled “Automating capture”There is no built-in CLI for screenshots, but two reliable paths:
# full screen to a file, no UI, via .NETAdd-Type -AssemblyName System.Windows.Forms,System.Drawing$b = [System.Windows.Forms.SystemInformation]::VirtualScreen$bmp = New-Object System.Drawing.Bitmap $b.Width, $b.Height$g = [System.Drawing.Graphics]::FromImage($bmp)$g.CopyFromScreen($b.Location, [System.Drawing.Point]::Empty, $b.Size)$bmp.Save("$env:USERPROFILE\Pictures\shot.png", [System.Drawing.Imaging.ImageFormat]::Png)For repeated captures (documentation, bug reports), PowerToys does not ship a capture module — but Windows’ own Snipping Tool supports a Win+Shift+S repeat, and the Game Bar handles video.
Related
Section titled “Related”Lab boundary
Section titled “Lab boundary”E1. Shortcuts and clipboard behaviour are documented by Microsoft. The lab VMs run over a console session with no GPU overlay, so DRM/exclusive-fullscreen capture failures are described from documentation, not reproduced.