Add a second monitor and the Snipping Tool starts behaving like a different application. The capture lands on the wrong screen. The image comes out stretched or squashed. The grey selection overlay only covers part of one display and ignores another entirely. The cursor you’re dragging doesn’t line up with the rectangle being drawn. None of this happens on a single screen, and all of it has a common root that almost nobody names plainly.

So let’s name it. The overwhelming majority of multi-monitor Snipping Tool problems are caused by mixed display scaling — running your monitors at different scaling percentages. This is not a coincidence and it is not bad luck. It is a specific, well-documented weakness in how Windows maps screen coordinates across displays with different DPI settings, and once you understand it, the “bugs” sort cleanly into three piles: things that are genuinely broken, things that are a setting you can change, and things that are working as designed even though they’re annoying. Knowing which pile you’re in tells you whether to fix it or live with it.

Why mixed scaling breaks captures

Windows lets each monitor run its own scaling level — 150% on a sharp laptop panel, 100% on an older external, say — so text stays a sensible size on each. That’s a genuinely useful feature. The problem is that the screen-clip overlay has to translate your mouse position into pixel coordinates that span every display at once, and when those displays use different DPI, the maths goes wrong.

Concretely, this is per-monitor DPI awareness failing to do its job. The Desktop Window Manager struggles to reconcile the coordinate systems, so the region you select drifts away from where your cursor actually is, or the captured pixels get rescaled into a stretched, distorted image. In the worst version, the overlay treats the smallest effective resolution as the ceiling for what it can cover, so a portion of your larger or higher-scaled monitor simply can’t be selected — the grey dimming stops partway across, or a whole monitor never dims at all.

The diagnostic giveaway is consistency: if unplugging your second monitor makes the problem vanish entirely, or if setting both monitors to the same scaling percentage fixes it, you’ve confirmed it’s a scaling-coordinate issue and not the app being broken. That’s actually good news, because scaling is something you control.

Microsoft did fix part of this — in January 2025

Here’s the part worth being precise about, because vague “keep Windows updated” advice helps nobody. Microsoft shipped a specific fix in the KB5050094 update on 28 January 2025 that addressed distortion in Snipping Tool screenshots when capturing across multiple monitors with different display scaling settings.

If you’re on a current build, that fix is already in place, and the distortion class of problem should be materially better than it was in 2023–2024. So if you’re still seeing distortion now, two things follow. First, make sure you’ve actually installed cumulative updates since January 2025 — on neglected or managed machines that’s not a given. Second, recognise that KB5050094 fixed some scaling distortion, not every multi-monitor quirk; the wrong-monitor and coordinate-offset behaviours are related but were not all swept up in that one patch. This is the kind of “fixed, partially” history that’s easy to lose track of, which is exactly why we maintain a running regression timeline of confirmed image and capture bugs by build and KB number — so you can check whether your specific symptom has a documented fix rather than guessing.

The fixes, in the order worth trying them

These are settings changes, not magic. They work because they remove the coordinate-translation problem at its source.

Match the scaling across your monitors. The cleanest fix is to set every connected display to the same scaling percentage. Open Settings > System > Display, select each monitor in turn, and set Scale to the same value — 100% is the safest common denominator. The cost is honest: text on your high-DPI panel may look smaller than you’d like. That’s the trade-off, and for many people a perfectly working screenshot tool is worth slightly smaller text.

If you can’t match scaling, make the higher-scaled monitor your primary. Windows tends to base its coordinate calculations on the primary display. Setting your highest-scaling monitor as primary — Settings > System > Display, select it, tick Make this my main display — resolves a good share of cases where matching scaling isn’t practical.

Don’t use full-screen capture mode. Rectangular and window snips behave far more reliably across mixed displays than the full-screen mode, which is the one most prone to grabbing the wrong region or clipping a monitor. If you mostly need full-screen grabs, capture a generous rectangle instead.

Repair the app. If captures are distorted regardless of scaling, the app package may be stale. Run Repair (and, failing that, Reset) from Settings > Apps > Installed apps > Snipping Tool > Advanced options. This is the same path covered in the main not-working guide, and it’s worth a try once you’ve ruled out scaling.

Update your graphics driver. Your GPU driver controls how each display is rendered and composited, and a stale or buggy driver can produce capture artefacts that look exactly like a scaling problem — torn images, wrong colours, regions that won’t capture. This matters most on machines with switchable graphics (an integrated chip plus a discrete GPU) where the displays may be driven by different adapters. Pull the current driver directly from the GPU manufacturer — Intel, AMD, or NVIDIA — rather than relying on whatever Windows Update last installed, which often lags well behind. If matching scaling didn’t fully resolve distortion, a driver update is the next most productive move.

The wrong-monitor problem

A distinct annoyance: you trigger a capture and the overlay appears on the wrong screen, or your snip captures a display you didn’t mean to. This is usually a primary-display and monitor-arrangement issue rather than pure scaling.

If your monitors are physically arranged differently from how Windows thinks they’re arranged — the layout diagram in Display settings doesn’t match your desk — the coordinate mapping will be off and captures can land on the wrong screen. Drag the monitor boxes in that diagram to match your actual physical setup, including vertical alignment if one screen sits higher than the other. Misalignment as small as a few hundred pixels can throw off where the overlay thinks each screen begins. Setting the correct primary display, as above, also helps here.

There’s a workflow angle too, and it’s the most reliable fix of all once you accept it: capture per monitor rather than across the seam. If you select a region that lives entirely on one display, the cross-monitor coordinate maths never has to run, and the offset and wrong-screen problems mostly evaporate. Reserve full-desktop captures for the rare times you actually need both screens in one image, and you’ll sidestep the bulk of multi-monitor trouble without changing a single setting.

HDR and ultrawide: the genuine edge cases

Two setups produce problems that aren’t really about scaling at all.

HDR in mixed mode — one monitor running HDR, another running standard dynamic range — can produce black or blank screenshots, or captures with badly wrong colour. The capture pipeline doesn’t always tone-map the HDR display correctly when it has to coexist with an SDR one. If your snips come out black or colour-shifted and you run HDR, test by temporarily turning HDR off on the affected display (Settings > System > Display > HDR) and capturing again. If that fixes it, you’ve found your cause, and the choice is between HDR and clean screenshots until the capture pipeline handles the mix better.

Ultrawide and very high-resolution panels mostly behave once scaling is consistent, but they expose the same coordinate-ceiling problem more dramatically because the resolution gap between an ultrawide and a laptop panel can be enormous. The fix is the same — uniform scaling — but the symptom is more obvious, with large bands of the ultrawide impossible to select.

What’s a bug, what’s a setting, what’s working as designed

To close the loop, here’s the honest sort:

  • Genuine bug: the pre-2025 distortion that KB5050094 addressed, and the HDR mixed-mode black-capture behaviour. These are the capture pipeline doing something wrong, and they get fixed (or not) by Microsoft, not by you.
  • A setting you can change: the wrong-monitor captures (arrangement and primary display) and most coordinate-offset issues (matching scaling). These look like bugs but are configuration, and they’re entirely in your hands.
  • Working as designed, just badly: mixed per-monitor DPI is an intentional Windows feature, and the Snipping Tool’s struggle with it is a consequence of that design rather than a defect in the tool itself. Microsoft built a system that lets you mix scaling and a capture tool that doesn’t love it, and you’re caught in the gap.

That last category is the one worth internalising. You will not “fix” mixed-DPI capture in the sense of making Windows perfect at it; you’ll either standardise your scaling and move on, or accept the occasional offset as the price of differently-sized text on each screen.

If, after all this, the shortcut itself is the thing misbehaving rather than the multi-monitor handling, that’s a separate fault tree — see the Win+Shift+S diagnostic path.