Windows Clipboard Not Saving Images
Win+V saves text reliably, but images never appear. You copy a screenshot with Snipping Tool, open Win+V, and the screenshot is missing. This is a different problem from "Win+V does not work at all" — the history is recording, just not the images. This guide walks through the diagnostic tree for "history saves text but not images," covering the 4 MB cap, the format whitelist, and the rarely-needed bitmap history toggle.
For related troubleshooting entries, see when the history panel will not open, Win+V Says 'Nothing Here'? How to Fix Clipboard History on Windows 11, and pinned clipboard items disappeared.
Step 1: Confirm the basic mechanism
Copy a short text string ("test 1") from Notepad. Open Win+V. If "test 1" appears, the history is recording text. Now copy a small image — the Snipping Tool's "Rectangle" mode, capturing a small region. Open Win+V. If the image appears, image history is working, and the issue is specific to the image you were trying to copy. If the image does not appear, proceed to Step 2.
Step 2: Check the 4 MB cap
Windows clipboard history caps each item at 4 MB. The cap applies to the item's serialized size. For images, the serialized size is the bitmap size, which depends on the dimensions and the bit depth. A 4K screenshot at 32 bpp is roughly 33 MB as a raw bitmap, which is well above the 4 MB cap; the screenshot will not be recorded, even though the copy succeeded.
The cap is documented behaviour; see Windows clipboard 4 MB cap: what gets dropped and why your huge screenshot never appears in Win+V for the full discussion.
To verify, copy a smaller image — a 200×200 pixel region. If the small image appears in Win+V but the large screenshot does not, the cap is confirmed.
The fix for the cap is to copy smaller images. For screenshots that you need to keep in history, capture a region rather than the full screen. For full-screen captures, save the file directly (Snipping Tool's save button, or ShareX's file output) rather than relying on clipboard history.
Step 3: Check the format
Windows clipboard history records three formats: text, HTML, and bitmap. Files are not first-class history cards — they are HDROP references that the history does not record. If you copy a file (right-click a file in Explorer → Copy), the file does not appear in Win+V.
The same is true for some image formats. If an app places the image on the clipboard as a private format (a PNG stream, a JPEG stream, or an application-specific format) without also placing a bitmap (CF_DIB or CF_DIBV5), Windows history does not record it.
To verify, copy the image via a different path. If you copied from Snipping Tool, try copying from Paint instead (open Paint, paste the image, select all, copy). Paint places a bitmap on the clipboard, which Windows history records. If the Paint-copied image appears in Win+V, the original app was placing a private format.
For the full discussion of formats, see what the Windows clipboard can and cannot store and how to copy an image instead of the file.
Step 4: Check the bitmap history toggle
In some Windows 11 builds, the clipboard history settings include a separate toggle for "Save images to clipboard history." If this toggle is off, text is recorded but images are not. The toggle is not present in all builds; if you do not see it, this step does not apply.
Steps:
- Settings → System → Clipboard.
- Look for a "Save images to clipboard history" or similar toggle.
- If present and off, turn it on.
- Copy an image and check
Win+V.
If the toggle is present and was off, this is the cause. If the toggle is not present, image history is on by default and Step 4 does not apply.
Step 5: Check for an app exclusion
If the image was copied from an app that is on the clipboard history exclusion list, the image will not be recorded, regardless of format or size. The exclusion is per-app, not per-format.
Steps:
- Settings → System → Clipboard → Exclude apps.
- Look for the app you copied from (Snipping Tool, ShareX, Greenshot, Paint, etc.).
- If the app is on the list, remove it.
- Copy an image from the app and check
Win+V.
For the full discussion of exclusions, see what sensitive formats should monitors ignore.
Step 6: Check for a third-party manager conflict
A third-party clipboard manager (Ditto, CopyQ, etc.) can interfere with image recording by consuming the bitmap format before Windows history sees it. The interference is rare but possible, especially with managers that have an "image capture" mode.
Steps:
- Quit any third-party clipboard manager (right-click the tray icon → Exit).
- Open Task Manager → Details tab. Confirm no
ditto.exe,copyq.exe, etc. are running. - Copy an image and check
Win+V.
If the image appears after quitting the third-party manager, the manager was interfering. The fix is to configure the manager to coexist with Win+V or to use only one of the two.
For the related discussion, see win+v vs a clipboard manager: honest split.
Step 7: Restart the Clipboard User Service
The Clipboard User Service (cbdhsvc_*) may be running but stuck in a state where it records text but not images. Restarting the service clears the stuck state.
Steps:
- Open Task Manager → Services tab.
- Find
cbdhsvc_*. - Right-click → Restart.
- Copy an image and check
Win+V.
If the image appears after restarting the service, the service was stuck.
Step 8: Check RDP clipboard redirection
If the machine is in a Remote Desktop session, the clipboard is being relayed by rdpclip.exe. RDP clipboard redirection supports bitmap formats, but it can fail for large bitmaps or for bitmaps in formats that the redirector does not whitelist. The symptom is that text copies through but images do not.
Steps:
- If you are in an RDP session, copy the image on the local machine instead and check
Win+Von the local machine. - If the image appears locally but not in the RDP session, the RDP clipboard redirector is the cause.
For the full RDP clipboard discussion, see remote desktop copy-paste not working and RDP files paste but text does not (or the reverse).
App-specific issues
Some apps do not place images on the clipboard in a format that Windows history records, even when the copy appears to succeed. Common culprits:
- Browser image copies — some browsers place a private format for image copies; the fix is to use "Copy image" rather than "Copy image address."
- Office clipboard interactions — the Office clipboard can interfere with the Windows clipboard; the fix is to disable the Office clipboard.
- Snipping Tool on certain builds — older Snipping Tool builds had a bug where the bitmap was not placed on the clipboard reliably; updating to the latest Windows 11 build fixes it.
If the issue is app-specific and the app cannot be updated, the workaround is to paste the image into Paint first, then copy from Paint, which places a clean bitmap on the clipboard.
Honest positioning
Edge-Drop, the Windows hover-activated clipboard shelf, records images independently of Windows clipboard history. The shelf polls the clipboard at roughly 300 ms and records whatever formats are present, including bitmaps and file references. The shelf is not subject to the 4 MB cap; a 50 MB screenshot is recorded in full, with the heavy payload offloaded to disk and a thumbnail served through the shelf's internal edgelocal:// scheme. The shelf does not compete with Windows history on convenience — Windows history is more accessible via Win+V — but it does compete on size, recording images that Windows history drops. For creators who work with large images regularly, the shelf is one option; for users who only occasionally need image history, the fix is to address whatever is preventing Windows history from recording the image.
A short summary
| Step | Cause | Time |
|---|---|---|
| 1 | Confirm mechanism with small text and small image | 1 minute |
| 2 | 4 MB cap on large images | 1 minute |
| 3 | Format not on the text/HTML/bitmap whitelist | 2 minutes |
| 4 | Bitmap history toggle off (some builds) | 1 minute |
| 5 | App on the exclusion list | 1 minute |
| 6 | Third-party manager conflict | 1 minute |
| 7 | Clipboard User Service stuck | 1 minute |
| 8 | RDP clipboard redirection failure | 5 minutes |
Work through in order. Stop at the first step that resolves the issue.
Related reading
- Remote Desktop Copy-Paste Not Working
- RDP Files Paste but Text Does Not (or the Reverse)
- Win+V Not Working on Windows 11: 9 Fixes
- Best Free Clipboard Manager for Windows
Sources
- Microsoft Support — Using the clipboard on Windows — official Windows clipboard documentation including the 4 MB cap and the text/HTML/bitmap format whitelist
- Microsoft Learn — Clipboard formats — Win32 reference for CF_DIB, CF_DIBV5, and the relationship between bitmap formats
- Microsoft Learn — Clipboard User Service — Microsoft reference for the cbdhsvc service that backs clipboard history
- Microsoft Learn — Remote Desktop clipboard redirection — official documentation of the RDP clipboard redirection channel and its format whitelist
- Microsoft Support — Snipping Tool — official user-facing guide to Snipping Tool, including the formats it places on the clipboard
Mohit Sehrawat is a B.Tech Computer Science Engineering student with a focus on software testing, bug detection, and product quality. He is interested in exploring applications, identifying issues, and improving the overall user experience through thorough testing.
GitHub · LinkedInCopy. Stack. Drop.
Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.
Download for Windows Get from Microsoft Store
How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support
Free · Lightweight · Privacy First