How to Drag Several Files as One Stack

Designers and producers often want four screenshots, a logo, and a PDF to travel together. File Explorer already has a version of that: select several items, copy or drag once, and the destination receives the whole set. A stack in a clipboard shelf is a later, optional grouping on top of that. Windows history will not build either one. Microsoft documents history as text, HTML, and bitmap, 25 items, 4 MB each.

This guide separates Explorer’s one-shot file list from a reusable stack, when grouping helps a mood-board or asset pack, and when a stack becomes a mess.

Explorer already groups a selection

Microsoft Learn: CF_HDROP transfers the locations of a group of existing files. The character array is a series of fully qualified paths, each null-terminated, with an extra null at the end. Ten selected files plus Ctrl+C is one clipboard operation and one list.

In Explorer:

1. Click the first file.
2. Ctrl+click additional files, or Shift+click a range.
3. Ctrl+C, or drag the selection to another folder or a drop target.
4. Paste or drop once. The destination receives every path that still exists.

That is already “several files as one payload.” It is not several history cards. Win+V stays empty. The next Ctrl+C of a sentence replaces the whole list. Unpinned history clearing on restart is irrelevant; the list never entered history.

The everyday how-to is How to Copy Multiple Files and Paste Them Somewhere Else. The format is How Windows File Drop Lists Actually Work.

A folder copy is a different one-item list: the folder path, not an expanded child list. See Copying a Folder to the Clipboard: What Gets Stored.

What a “stack” adds that Explorer does not

A stack, in the sense people search for, is a named or visual group that survives the next copy. Explorer’s HDROP does not. Built-in history does not. A file-aware manager has to invent the extra object:

• Keep several paths (or several copied bitmaps) under one card.
• Drag the card out once so the destination sees one HDROP with every member.
• Optionally ungroup later so one logo can leave without discarding the PDF.

That is a product decision. Microsoft does not document a “stack” clipboard format. Inventing a private OLE API name would be dishonest. What *is* documented is how a source should offer existing files: put CF_HDROP on the data object, and let the target call DragQueryFile. A well-behaved drag-out of a stack is just that list again.

Microsoft Learn also notes CFSTR_FILENAME as a single-file path kept for Windows 3.1 compatibility and superseded by CF_HDROP. A stack that only published the first name would look like a broken multi-select. That failure is Multi-File Copy From Explorer: Why Tools Miss Files.

When grouping helps

Grouping earns its keep in a few repeatable jobs:

The pattern is collect now, drop once. Switching windows between every file is the cost a stack removes. Using the Clipboard as a Temporary File Staging Area is the wider playbook.

A stack is the wrong default when the files are unrelated, when one of them is a secret, or when the destination can only accept one attachment at a time. Some web compose boxes take the first file and ignore the rest. Test the target with two tiny files before trusting a twelve-item pack.

How to do the job with only Windows

No extra app is required for a same-session pack.

Same destination folder

1. Select the files in Explorer.
2. Ctrl+C.
3. Open the destination folder.
4. Ctrl+V.

Different apps that accept file drops

1. Arrange Explorer and the destination so both are visible.
2. Select the files.
3. Drag onto the destination’s drop area.
4. If the cursor shows a “no” glyph, that app wants a picker or a bitmap, not a file list.

Need the pack after other copies

Windows will not remember the list. Options that stay inside the OS:

• Copy the files into a temporary staging folder (Desktop\pack-thursday) and treat that folder as the stack.
• Zip the set, then copy or drag the zip.
• Pin nothing in Win+V; pins cannot hold HDROP.

A staging folder is dull and reliable. It survives restart because it is disk, not clipboard. How to Keep File Copies After a Restart.

When a stack becomes a mess

Common ways a pack goes wrong:

• Stale paths. One screenshot was deleted. The stack still claims six files. Paste copies five and errors on the sixth, or the whole drop fails, depending on the target. Visible broken-path handling matters: Broken Paths: When a Saved File Clip Points at Nothing.
• Mixed meanings. A URL, a bitmap snip, and a zip are not the same kind of object. Merging them into one HDROP only works if everything is a real file. Merging Two Clipboard Items Into a Collection.
• Network and ZIP sources. A file still inside a compressed-folder view, or on a disconnected SMB share, is a path that will rot. Extract or copy locally first.
• Too large to reason about. Fifty RAW files in one card hide mistakes. Explorer multi-select of fifty files is fine for a one-shot copy. A reusable stack of fifty is usually a folder.
• Secrets. A stack that quietly includes an exports folder with a .env or a payroll CSV is worse than a missed logo.

If one file needs to leave the pack, ungroup rather than rebuilding: Ungrouping a File Bundle Back Into Separate Items.

Drag-out versus paste

Dragging a stack and pasting a stack should offer the same HDROP, but destinations differ:

• Explorer wants files. Drop and paste both work if the paths exist.
• Outlook desktop often accepts a file drop as attachments.
• Gmail in a browser may accept a drop on the compose window; some states only accept the picker.
• Photoshop may open files, place them, or ignore a multi-file HDROP depending on where the drop lands. Pixels are a different payload: How to Copy an Image File So Photoshop Gets Pixels.

Some apps accept Ctrl+V of an image but reject a file drag, or the reverse. That is Why Some Apps Accept Paste but Reject Drag.

Internal reorder inside a shelf (card A above card B) is not a Windows file drop. Internal Drag vs External Drag in Clipboard UIs.

History limits still apply to the pictures you *did* copy as pixels

If the “stack” is actually six Win+Shift+S snips, those are bitmaps. History will keep them only if each is 4 MB or smaller, only until 25 unpinned items push them out, and only until restart unless pinned. A file stack of PNGs on disk does not have those caps. Mixing the two models — expecting Win+V to hold six files *and* six huge screenshots — is how the feature looks broken when it is working as documented.

Optional shelf, not a requirement

If the daily pain is staging a visual pack at the screen edge and dragging it into chat without recopying, a local shelf that groups file cards is a reasonable extra. Edge-Drop is one such tool: hover the edge, stack files, drag the stack out as a native file list. Ditto-style search history is a different job. Explorer plus a staging folder is enough when the pack is used once.

Do not install anything to fix Win+V “not showing the files.” History is not allowed to show them.

Related reading

• Ungrouping a File Bundle Back Into Separate Items
• Merging Two Clipboard Items Into a Collection
• Why You Cannot Drag Old Clipboard Files Into Explorer
• How to Get a Screenshot Into Photoshop Without Recopying

Sources

• Shell Clipboard Formats (Microsoft Learn) — CF_HDROP as a group of existing file paths; CFSTR_FILENAME is single-file and superseded.
• Handling Shell Data Transfer Scenarios (Microsoft Learn) — count paths with DragQueryFile(iFile = 0xFFFFFFFF), then read each index.
• Using the clipboard (Microsoft Support) — history is text, HTML, bitmap; 25 items; 4 MB; restart wipe except pins.
• File Explorer in Windows (Microsoft Support) — Explorer copy, cut, and paste of files.
• Standard Clipboard Formats (Microsoft Learn) — CF_HDROP definition.

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