← Back to Blog

Troubleshooting | Published Aug 21, 2026 | Updated Nov 21, 2026 | 6 min read

Why Copying a Large Image Spikes CPU on Windows

By Mohit Sehrawat

Why Copying a Large Image Spikes CPU on Windows — Edge Drop Guide

A short CPU spike when you copy a large image is usually normal. Images usually sit on the Windows clipboard as uncompressed bitmaps (a 4K screenshot is about 32 MB of raw pixels), and any program that watches the clipboard may read, convert or compress that data the moment it arrives. If the spike lasts several seconds, freezes an app or happens on every copy, Task Manager will show you which process is responsible.

Why a big image is expensive to copy

A bitmap on the clipboard holds every pixel. At 4 bytes per pixel, the raw size grows quickly with resolution:

Image sizeRaw bitmap size (4 bytes per pixel)
1920 × 1080 (Full HD)about 7.9 MB
2560 × 1440 (QHD)about 14.1 MB
3840 × 2160 (4K)about 31.6 MB
5120 × 2880 (5K)about 56.3 MB

Three things can turn that data into CPU work:

  • Format conversion. Windows converts between the bitmap formats CF_DIB, CF_DIBV5 and CF_BITMAP when a program asks for one that isn't on the clipboard. Each conversion is a pass over every pixel.
  • Delayed rendering. An app can announce a format without producing it, then render it only when another program asks for it. Microsoft notes that if rendering takes a long time, the source app can become visibly unresponsive while it works. So the spike, or a brief freeze, can appear in the app you copied *from*, not in a clipboard tool.
  • Clipboard watchers. Clipboard managers react as soon as the clipboard changes, not when you paste. Many then read the image, compress it for storage and build a thumbnail. Two or more watchers each do that work separately.

Windows clipboard history (Win+V) has its own limit: items over 4 MB aren't kept, which is why a huge screenshot never appears in Win+V.

How to find which app is using the CPU

  1. Press Ctrl+Shift+Esc to open Task Manager.
  2. On the Processes page, select the CPU column heading to sort by CPU use.
  3. Copy the same large image again and watch which process rises to the top.
  4. If the process belongs to an app with several processes (Electron and browser-based apps work this way), switch to the Details page to see the individual .exe names.
  5. For a cumulative figure, right-click a column heading on Details, choose Select columns, and add CPU time. Note it before and after a copy.

To confirm a clipboard tool is the cause, quit it completely from its system tray icon (closing its window often leaves it running), copy the image again and compare. Repeat for each tool. If the spike remains with every clipboard tool closed, the source app is doing the work. For a repeatable way to measure a single app's CPU and memory, see how to measure a clipboard app's idle RAM and CPU.

Causes and fixes

What spikes in Task ManagerLikely causeWhat to do
The app you copied fromRendering the image into a clipboard format on requestUsually unavoidable for very large images; copy the saved file instead (below)
A clipboard managerReading, compressing and thumbnailing each imagePause capture while you copy large images, if the tool offers it, or check its settings for image options
Two clipboard tools at onceBoth process every copyKeep one; see two clipboard managers fighting each other
An unfamiliar process on every copyA program you don't recognise is watching the clipboardCheck what it is before ignoring it

Copy the file instead of the pixels

If the image is already saved, select the file in File Explorer and press Ctrl+C. The clipboard then holds a reference to the file rather than tens of megabytes of pixels, so there's nothing to convert or compress. Chat apps, email and upload dialogs accept a pasted file. Copying an image versus copying the file explains when each one pastes the way you expect.

Large images in Edge Drop

Edge Drop, the screen-edge clipboard shelf made by the team behind this site, stores every captured image as a PNG and shows small thumbnails on its cards. Copying a very large bitmap therefore costs one compression pass in Edge Drop's own process. It has no setting to skip images or cap their size, but you can turn on Incognito mode (Settings > Behaviour, or Incognito (pause capture) in the tray menu) before copying a batch of large images. Either one stops Edge Drop reading the clipboard at once, and nothing copied while it's on is captured afterwards. Files copied in Explorer are stored only as path references, so copying the file avoids the image work entirely. How to use Incognito mode in Edge Drop has the steps.

FAQ

Does the spike happen even if I never paste?

Yes. Clipboard tools react when the clipboard changes, so the work happens at copy time.

Is a CPU spike on copy a sign of malware?

A brief spike in a clipboard tool or the source app is normal. A process you don't recognise that reacts to every copy deserves a closer look; clipboard hijacking explains what to check.

Does a clipboard manager use more memory after copying big images?

Usually, because each image is stored in history. How much RAM a clipboard manager should use covers what's normal.

Related reading

Sources

Mohit Sehrawat
Written by Mohit Sehrawat · Author & Testing Contributor

Mohit Sehrawat helps test Edge Drop, trying features on Windows and reporting bugs. A B.Tech Computer Science Engineering student focused on software testing and product quality, Mohit writes the troubleshooting and privacy guides.

GitHub · LinkedIn

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

Free · Lightweight · Privacy First
Find us on CodeHype