Copied Image Pastes as a File Path

When a copied image pastes as a file path string, the cause is a mismatch between what the target app asked for and what the source app provided. The user copies an image — a screenshot, a picture from a web page, a graphic from an image editor — and pastes into a target app, expecting the image to appear. Instead, the target inserts a text string like C:\Users\name\Pictures\screenshot.png or a similar path. The clipboard is not broken; it did exactly what the target requested.

This guide covers the diagnostic order for the "image pastes as file path" symptom on Windows 11. For related problems, see copied text pastes as an image for the inverse case, OneDrive / Office clipboard taking over for the Office clipboard interference case, and the broader Win+V not working on Windows 11: 9 fixes and Win+V Says 'Nothing Here'? How to Fix Clipboard History on Windows 11 guides.

Why an image sometimes pastes as a path

When the user copies an image, the source app may write multiple clipboard formats:

• Bitmap (CF_BITMAP or CF_DIB) — the actual image pixels.
• File reference (CF_HDROP) — a Windows data structure listing file paths.
• Plain text — sometimes the file path as a string, for apps that only understand text.

When the source is a file in Explorer (right-click an image file, choose Copy), the clipboard contains an HDROP reference to the file path. There is no bitmap on the clipboard — only the file reference. When the target pastes, it walks the available formats:

• An image editor (Photoshop, Paint) reads the HDROP, opens the file, and pastes the pixels.
• A word processor (Word, Google Docs) reads the HDROP, opens the file, and inserts the image.
• A plain text field (Notepad, a browser's text input) cannot read HDROP, so it falls back to the plain-text representation, which is the file path as a string.

This is why copying an image file from Explorer and pasting into a text field inserts the file path. The text field asked for text, and the only text on the clipboard was the path.

When the source is a screenshot tool (Win+Shift+S, Snipping Tool), the clipboard contains a bitmap, not a file reference. Pasting into a text field then either fails silently (the field cannot accept a bitmap) or inserts nothing. The "image pastes as path" symptom in this case is rare but possible if a clipboard manager has converted the bitmap to a file path on disk and is pasting that path.

Layer 1: confirm what is on the clipboard

Before diagnosing, confirm what the clipboard actually contains. The simplest test:

1. Copy the image (from the source).
2. Paste into Paint (or another image editor).
3. If Paint shows the image, the clipboard has a bitmap.
4. If Paint shows nothing or shows a file path, the clipboard has only a file reference, not a bitmap.

If Paint shows the image, the cause is the target app not picking the bitmap (layers 2 and 3 below). If Paint does not show the image, the cause is the source app not writing a bitmap (layer 4).

For a more detailed clipboard inspection, use a free clipboard viewer like Free Clipboard Viewer or the clipboard inspection tools in Visual Studio. These show every format currently on the clipboard.

Layer 2: use a target that accepts image format

If the clipboard has a bitmap but the target app pastes a file path, the target app is choosing the wrong format. The fix is to use a target that accepts image format.

• For document editing — use Word, OneNote, or Google Docs instead of Notepad or a plain text field. These apps insert images properly.
• For chat apps — Slack, Microsoft Teams, and Discord all accept pasted images. Most browser-based chat web apps (Slack web, Discord web) also accept pasted images.
• For image editing — use Photoshop, Paint, GIMP, or Affinity Photo. These apps always prefer the bitmap format.
• For email — use Outlook or the Gmail compose window. Both accept pasted images and embed them inline.

If the target app is a plain text field (a browser search box, a code editor's text input, a Notepad file), it cannot accept an image by design. The workaround is to paste into an image-accepting app first and then transfer to the text field if needed.

Layer 3: use Paste Special to force image format

Some target apps support multiple paste formats but default to the wrong one. In Microsoft Word:

1. Copy the image from the source.
2. Position the cursor in Word.
3. Press Ctrl+Alt+V (or right-click → Paste Special).
4. Choose Picture (Enhanced Metafile) or Bitmap from the list.
5. Click OK.

If the paste inserts the image, the cause was Word's default format choice. For the inverse case where Word picks an image when text was expected, see copied text pastes as an image.

Layer 4: change the source's copy behaviour

If the source app is a file in Explorer, the clipboard gets only an HDROP file reference, not a bitmap. To get a bitmap onto the clipboard, the source must be the image content, not the file. Options:

• Open the image file in an image editor and copy from there. Paint, Photoshop, and the Windows Photos app all write a bitmap to the clipboard when the user selects the image and copies.
• Use Win+Shift+S to capture a region of the screen. This writes a bitmap to the clipboard directly.
• Right-click an image in a web browser and choose Copy image. Modern browsers write a bitmap to the clipboard.

For more on getting an image onto the clipboard, see how to copy an image instead of the file and how to put a screenshot on the clipboard.

Layer 5: rule out clipboard manager rewriting

Some clipboard managers rewrite the clipboard in transit. A manager might cache the bitmap to a temp file and replace the clipboard with a file reference, expecting the target app to open the file. If the target app does not open the file but instead inserts the path as text, the symptom is exactly "image pastes as path."

To test:

1. Exit any third-party clipboard manager from its tray icon.
2. Copy the image from the source.
3. Paste into the target.

If the paste produces the image after exiting the manager, the manager was rewriting the clipboard. For the wider topic, see when two history tools hook the same copy.

Layer 6: handle Win+V history limitations

Win+V stores bitmap format as a history card, but files are not first-class history cards. When the user copies an image file from Explorer, Win+V does not show the image as a card — it shows a "file copied" indicator or nothing at all, depending on the build. Clicking a file-format history entry to paste into a text field can produce a file path string.

The workaround is to copy the image content (not the file) before pasting from Win+V. For more on Win+V's format handling, see why Win+V will not show the file you just copied and Windows clipboard history does not store files.

Layer 7: save the image to disk and insert it

When none of the above layers resolves the problem, the practical fallback is to save the image to a file and insert it through the target app's "Insert image" or "Open file" dialog. This bypasses the clipboard entirely.

The pattern:

1. Save the image to disk (Snipping Tool → Save, or right-click a web image → Save image as, or paste into Paint → Save).
2. In the target app, use Insert → Picture (Word, Outlook) or File → Open (image editors) to load the file.

This is slower than a paste, but it always works and gives the user control over the file format and location.

For more on this workflow, see how to copy an image file so Photoshop gets pixels and dragging PDFs from history into email.

What does not help

A few commonly suggested fixes do not help when an image pastes as a file path:

• Restarting the Windows clipboard service. The service is fine; the format mismatch is in the source and target apps.
• Clearing Windows clipboard history. Clearing history does not affect the live clipboard's format.
• Disabling Win+V. Win+V is independent of the live clipboard paste.
• Reinstalling the target app. The target is doing what it was designed to do; the cause is the format mismatch.

A short checklist

If only one thing is checked, it should be the Paint paste test (layer 1). If two, add the target-app change (layer 2). If three, add the source-app change (layer 4). Most cases resolve in the first three layers. Layer 7 (save and insert) is the universal fallback when nothing else works.

That limit is unpacked in Clipboard History Search Finds Nothing.

Related reading

• OneDrive / Office Clipboard Taking Over
• After Sleep, the First Copy Is Ignored
• Win+V Not Working on Windows 11: 9 Fixes
• Best Free Clipboard Manager for Windows

Sources

• Microsoft Support — Using the clipboard on Windows — official description of the Win+V feature and the text/HTML/bitmap formats it stores
• Microsoft Learn — Clipboard formats — Win32 documentation covering CF_BITMAP, CF_DIB, CF_HDROP, and other standard clipboard formats
• Microsoft Learn — File clipboard format (CF_HDROP) — Windows shell documentation covering how file copy uses HDROP references
• Microsoft Learn — Clipboard operations — Win32 documentation covering how target apps walk the available clipboard formats and pick one to paste
• Microsoft Learn — Drag and drop and the clipboard — Windows shell documentation covering the relationship between clipboard file references and drag-and-drop operations

Copy. 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