Skip to main content
Question

Incorrect (incomplete) copying

  • August 6, 2026
  • 3 replies
  • 36 views

Oleksii Sokolov

So. Incorrect (incomplete) copying. 

When you duplicate a frame, it's duplicated entirely. Copying and pasting only partially duplicates it.

What could be the reason? Is this a bug in the program or did I do something wrong?

 

 

3 replies

Tom Reem
Figmate
  • Figmate
  • August 8, 2026

Hey ​@Oleksii Sokolov, welcome to Figma Forum and thanks for flagging this! Appreciate your recording as well.

I tested this on a sample file on my end and wasn't able to reproduce it. You're right to expect the same result from both, though — the Figma Learn article describes duplicating as shorthand for copy and paste: Copy and paste objects → Duplicate. A frame that copies over without all of its child layers isn't expected behavior, so let's take a closer look together.

Please check a couple of things that may narrow this down:

  1. Reload before you copy. If the file has been open in that tab or window for a long stretch, close and reopen it (or fully quit and relaunch the Figma Desktop App), then copy again.
  2. Check on the structure. In the layers panel, expand the frame and confirm every layer is actually nested underneath it. This likely isn't the cause on its own, since a duplicate would leave loose layers behind too, but it's quick to rule out.

And a few questions that would help me test on my end:

  • Does it happen with every frame and file, or just this one?
  • Are you encountering this in the Figma Desktop App, the browser, or both?
  • If you're on the app, is it up to date (version 126.7.10 or later)?

Please post back with whatever you find and we’ll go from there.


Oleksii Sokolov

Hello, ​@Tom Reem. Thanks for the reply. I checked, I have 126.7.10. I checked in the browser — and it turns out there's no such error there. It's only on PC (Windows 11). It happens specifically with bulleted list on these frames. I've already found a workaround for myself, but it's curious, yes. Maybe it's just some coincidence of factors.

You can view this on your PC in the Desktop App:

 


Oleksii Sokolov

Yes, there is some random bug. Possibly related to the font. It helps even if you simply use the Scale (K) to first increase the frame by 2 times, and then reduce it back :)