How to Paste a Snip Into Figma Without Quality Loss

Figma is happy to accept a pasted bitmap. It is also happy to display a lower-resolution stand-in until the high-resolution image is in view. Combined with Windows display scaling, a snip can look “ruined” when the pixels are still intact.

This guide separates capture, clipboard, import, and Figma’s own image loading.

Capture at 100% UI scale when pixels matter

Win+Shift+S copies device pixels of the selected region. If Windows is set to 150% scale, a “390-point” phone frame on screen is not 390 pixels. The bitmap is larger. When Figma places that image into a 390-wide frame, it downscales. That can look soft if the frame is then exported at 1x.

For UI references that will be measured:

1. Set the source window to a known scale (browser 100%, Windows scale noted).
2. Capture with Win+Shift+S or save a PNG via Snipping Tool auto-save.
3. In Figma, check the image’s pixel size in the right sidebar after paste.
4. Place it at 100% of those pixels, or scale by a clean factor (50%, 200%), not 73%.

Community reports of “paste is half size” almost always track OS or browser zoom, not a Figma bug. Figma’s help on image loading explains a different blur: images larger than 512×512 have a low-resolution stand-in until the high-resolution version is in the viewport.

If a pasted snip looks muddy, zoom the canvas so the image fills the view and wait. If it sharpens, the file was fine. If it stays muddy, the clipboard already held a soft bitmap (chat download, video frame, or a scaled window).

Paste versus file import

Microsoft’s history still applies on the way in: 25 items, 4 MB, text/HTML/bitmap, restart wipe. A 4K snip may paste from the live clipboard and never appear in Win+V. Do not recapture because history is empty — check Paint or Figma paste first.

Confirm Snipping Tool auto-save so the PNG exists even after the next copy. Win+Shift+S Not Saving What You Think It Saves.

Desktop app versus browser

Figma desktop and Figma in the browser do not share a clipboard implementation.

• Desktop reads the Windows clipboard more like a native app. Bitmap paste is usually reliable.
• Browser needs clipboard permission. A blocked permission looks like “Figma cannot paste images.” Grant clipboard access for figma.com, or switch to desktop.
• Some enterprise browsers strip image clipboard formats and leave HTML or a URL. Figma then pastes nothing useful, or pastes a link.

If desktop paste works and browser paste fails, it is not the snip. Use desktop for image-heavy work, or import the file.

A later article in this cluster covers the broader desktop/web split: Figma Desktop vs Figma Web: Paste Behavior Differs.

Steps that preserve quality

1. Capture. Prefer a file for anything that will be annotated or compared.
2. In Figma desktop, create a frame for the reference (or paste on the canvas).
3. Ctrl+V for a small snip. For a large or final reference, drag the PNG.
4. With the image selected, confirm pixel dimensions. Do not stretch a 400-pixel-wide snip across a 1440-wide frame and call it a quality bug.
5. Lock the layer. Label it ref/ so it is not exported by accident.
6. For exports of *new* UI drawn in Figma, use Figma’s 1x/2x export settings. Do not export the reference snip as if it were production art.

Figma stores images in the file. Once placed, the original clipboard can be overwritten safely. That is the opposite of Photoshop-only-paste-from-history.

Color and sharpness

Screenshots of HDR or wide-gamut displays can look duller in Figma’s working space. That is a color-management issue, not compression. A dedicated article exists later in the cluster. For SDR office work, sRGB snips are usually fine.

Sharpening a screenshot in Figma is the wrong fix. Recapture at 100% zoom or import the PNG.

Color picking from the placed image is a separate job. Figma’s eyedropper samples the canvas, including any mix-blend and overlay. For a hex from the *original* pixels, pick before filters, or use PowerToys on the source window. Color-Picking From a Copied Screenshot.

When paste is the wrong interface

• Transparent UI chrome that must stay alpha-clean: prefer a PNG file export from the design tool, not a snip. Snips of the screen flatten onto whatever was behind the window.
• SVG icons: copy as SVG from the source, or import the SVG file. A snip is pixels. SVG vs PNG on the Clipboard.
• Legal or brand assets: use the official file from the DAM, not a screenshot of the DAM preview.

Worked example: iPhone frame at 390

1. Set the device preview or browser to 390 CSS pixels at 100% browser zoom.
2. Note Windows scale (Settings > System > Display). At 150%, the snip will be ~585 pixels wide.
3. Capture the device chrome-free region.
4. Paste into Figma. Read the width.
5. Place it in a 390 frame only if the width is 390 or 780 (2x). If it is 585, either recapture at 100% OS scale or set the image to 390 and accept interpolation — or keep it at 585 and do not pretend it is a 1x iPhone asset.

The last option is honest for a reference. It is wrong for a marketing mock that will be exported as if it were production UI.

Multiple displays with different scales

A laptop at 150% plus an external monitor at 100% produces snips of different pixel densities. Figma will show them at their pixel sizes. Aligning them as if they were the same physical phone is a math error, not a paste error. Capture both from the same display.

FigJam versus Figma Design

FigJam is more forgiving of mixed-resolution pastes (sticky notes and traces). Figma Design files that ship to developers should import official exports, not snips, except in a clearly labeled ref/ page.

Optional shelf

If many PNG references must land on a Figma desktop canvas in one sitting, a local drag shelf can reduce Explorer trips. Edge-Drop is an optional hover shelf. The browser editor may ignore file drags from unusual sources; desktop Figma is the realistic target. The quality path remains a named PNG.

FAQ

Should images be set to Fill or Fit after paste? Neither fixes missing pixels. If the bitmap is 400 px wide, no fill mode invents 1200 px of detail. Import a 2x export instead.

Does FigJam compress more than Figma Design? Treat both as capable of stand-in previews. Zoom to load high-res. Export from the source file when shipping.

Can a shelf drop into Figma web? Often no. Use desktop Figma or the upload/import control.

Handoff to developers

A Figma frame full of snips is a reference page, not a component library. Label it. Developers should read auto-layout components, not a photograph of a button. If the snip is the only spec, export a clean PNG into the ticket and write the measurements in text.

Windows history will not be available to the developer on another PC. Files and Figma cloud will.

That limit is unpacked in Scrolling Capture Is Not a Clipboard Problem.

Related reading

• Color-Picking From a Copied Screenshot
• Building a Mood Board From Copied Images
• How to Get a Screenshot Into Photoshop Without Recopying
• How to Paste Without Formatting on Windows

Sources

• Image loading and performance (Figma Help) — high-res versus stand-in images; viewport loading.
• Use Snipping Tool to capture screenshots (Microsoft Support) — overlay and auto-save PNG.
• Using the clipboard (Microsoft Support) — 25 / 4 MB / bitmap history.
• Import files into Figma (Figma Help) — file import as the durable alternative to paste.
• Keyboard shortcuts in Windows (Microsoft Support) — Win+Shift+S capture.

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