When Figma Components Replace Copied Assets

Early product design is collage: a screenshot of a button, a copied icon, a PNG of last week's nav. That phase is allowed. It becomes expensive the week the primary button exists in fourteen files at three radii. Figma's own help describes the replacement: a main component defines the object; instances stay linked and receive updates; a team library publishes those components and styles to other files. Anyone with can-edit can create a component. Win+V can store a bitmap of that button if it is under 4 MB, among 25 items, until the next restart. Those are not the same maturity level.

This is the point where a component library beats a clipboard. Not because paste is immoral — because instances have a maintenance story and screenshots do not.

What Figma actually documents

From Figma's guide to components:

• Components are reusable elements (buttons, icons, layouts)
• A main component holds the definition
• An instance is a linked copy that receives updates
• Components can stay in one file or be published through a team library
• Can-edit users create and edit; can-view users can use library components from files they can access

Variants (official "Create and use variants"):

• Related components live in a component set
• Windows shortcut to create a component: Ctrl+Alt+K
• Variant properties group states (size, theme, selected)

Copy/paste (official):

• Objects copy between pages and files with Ctrl+C / Ctrl+V
• Copy as PNG defaults to 2×
• Images from the OS clipboard become fills
• Assets over 4096 px are resized
• GIFs copied from most browsers paste static

None of those paste rules produce a maintainable button.

Desktop versus web still changes OS clipboard behavior. Component instances do not care which surface opened the file. Figma Desktop vs Figma Web: Paste Behavior Differs. Adobe XD, Figma, and Sketch on Windows: Clipboard Reality: vectors rarely survive a hop through Windows history. Components never take that hop.

A maturity ladder

Screenshot-driven design is still correct for exploration and for capture of things that are not in Figma (a live product bug, a photo). It is incorrect for anything the team will restyle twice.

When to promote a pasted PNG

Promote when any of these is true:

• The same object was pasted into a third frame
• A critic asked to change corner radius everywhere
• Dark mode needs a twin
• Engineering asked for a name
• Two designers disagree because they copied different weeks

Steps (official commands only):

1. Clean the object (auto layout if the team uses it — that is a separate Figma feature; use it if the file already does)
2. Create component
3. Add variants instead of duplicating files
4. Replace stray PNGs with instances (swap instance)
5. Publish when a second file needs it
6. Delete the old bitmaps from the canvas and from Win+V

Do not "promote" by pinning the PNG. Pinned Win+V Items Are Not a Real Library.

What should stay a file or a clipboard item

• Photographs and illustrations that are not UI chrome — export and Place. Best Clipboard Setup for Photoshop Users
• Brand PDF policy — a path, not pages. Brand Guidelines PDFs Do Not Belong in History
• This hour's hex — text in Win+V
• Client markup — a review folder with an end date. Client Feedback
• HUD tiles in a game repo — components *plus* exported files the engine imports. Game UI Artists

Creative Cloud Libraries remain the Adobe-native kit for Photoshop/Illustrator color and logo. They do not replace Figma components for UI. Keeping Brand Assets Off the Desktop and On a Shelf.

Windows history after a design system exists

Leave history on for:

• Ticket IDs
• Token strings
• A URL to the library file

Leave it off the critical path for:

• Icons
• Buttons
• Nav
• Illustrations that have exports

A 25-slot bitmap list next to a published library is how detached leftovers sneak back into production. Friday clear. Sync off on machines that copy unreleased UI.

A hover shelf can still stage export files for a PR. Edge-Drop is optional for that drag. It should not become a shadow icon kit. If the object has a main component, insert an instance.

Tablet and pen

Promotion to components is a desktop-precision job. On a tablet, capture and comment; sit down with a keyboard to build the set. Working From a Tablet on Windows: Pencil vs Clipboard. Figma's Windows app will not eyedrop the whole screen.

How to tell the team

One paragraph in the README:

Exploration can paste. Anything we will restyle twice is a component. Icons and buttons live in the published library. Do not ship a screenshot of a component. Export only what engineering cannot take from Dev Mode.

Worked example: the primary button finally grows up

Week 1: someone pastes a PNG of a web button into three exploration frames. Fine.

Week 3: four files use slightly different radii. Create Button/Primary with variants Size=S|M|L and State=Default|Hover|Disabled. Replace the PNGs with instances. Publish.

Week 6: brand changes the CTA green. Update the variable once. Instances follow. The intern's pinned Win+V bitmap does not — delete that pin in the Friday hygiene.

Engineering inspects the component in Dev Mode. They do not ask for "the button screenshot from Slack last month."

Troubleshooting

That is the maturity model. The clipboard does not graduate. The design system does.

Windows limits after the library exists

Once buttons are components, Win+V should hold ticket IDs and token strings, not PNGs of those buttons. A pinned screenshot of Button/Primary will disagree with the library the week the radius changes.

Microsoft's history is still 25 items, 4 MB, text/HTML/bitmap, restart-volatile except pins. It cannot publish, cannot accept library updates, and cannot swap variants. Use it as a notepad beside Figma, not as a second design system.

If a teammate insists on pasting UI, point them at Create component and the official component guide. The clipboard is still allowed for exploration. It is no longer allowed for production chrome.

A useful audit once a quarter: search the file for rasterized buttons and icons that are not instances. Replace them. Clear Win+V pins that look like UI chrome. If a marketing illustration is still a PNG, that is fine -- illustrations are often files, not components. The line is repeated chrome. Repeated chrome belongs in the library. One-off art belongs in export\. History belongs to strings and accidents.

New hires should get the library link on day one, not a zip of PNGs. A zip teaches screenshot design. A library teaches instances. If the team is still on Adobe XD leftovers or Sketch files, convert chrome to Figma components instead of copying bitmaps across tools. Adobe XD, Figma, and Sketch on Windows: Clipboard Reality is already the warning that vectors rarely survive that hop.

If you are choosing on product lines rather than the built-in panel, Creative Cloud Libraries vs Local Clip Staging is the honest split.

Related reading

• Packaging Dielines: Files, Not Bitmaps
• Creative Cloud Libraries vs Local Clip Staging
• Best Clipboard Setup for Photoshop Users
• Best Clipboard Habits for Developers in 2026

Sources

• Guide to components in Figma — main components, instances, team libraries.
• Create and use variants (Figma) — component sets and Windows shortcut Ctrl+Alt+K.
• Components, styles, and shared library best practices (Figma) — publishing and reuse at scale.
• Copy and paste objects (Figma) — what paste still is (fills, Copy as PNG at 2×).
• Using the clipboard (Microsoft Support) — 25 / 4 MB / bitmap / restart — why history cannot be the kit.
• How to use clipboard history in Windows 11 (Microsoft) — leftover pins after a library exists.

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