Paste Properties shortcut not functioning on latest update

Hey ​@TeeterTotter — thanks for flagging this, and welcome to Figma Forum!

I tested this out, and the workflow worked as expected in my file, but I want to make sure we get to the bottom of this. To help narrow it down, can you confirm the following:

1. Does this happen if you copy/paste using the menu instead of the key commands? For example: Right-click the text layer → Copy/Paste as → Copy Properties or Paste Properties.
2. Does this happen in both the browser and Figma Desktop App? If you're on the desktop app, can you confirm you're on version 126.6.12 or later?
3. Does this happen on one file, or across all files in your account? For example: If you create a duplicate and test there, does the behavior change?
4. If possible, do you recall how long before the latest release you first noticed this issue?

If you've tried all of the above and it's still happening, let me know and I'll escalate this to the Product Support team for a deeper look. 🙏🏻

Hey Tom, thanks for the reply.

(VIA DESKTOP APP)

using the menu or the shortcuts does not work.

(VIA BROWSER)

-It looks like it is functioning properly in the browser version, either using the shortcuts or the mouse menu controls.

--

*This occurs in all files.

*I am in  126.6.12

*I just noticed this issue within the last week or so

-Thanks

Thanks for confirming, ​@TeeterTotter — appreciate the thorough testing. The fact that it works in the browser but not in the Figma Desktop App (and that both shortcuts and menu actions fail) may point to something specific to the app environment.

I've opened a ticket with our Product Support team so they can dig into more specifics for this. Your case number is: 1998168. To help them reproduce it, please check your inbox for an email from me with steps on sharing file access securely.

A couple of things to check in the meantime:

1. macOS keyboard settings. Sometimes third-party apps (like TextExpander or Jumpcut) or system-level shortcuts can intercept ⌘+⌥ combos. Worth a quick look under System Settings → Keyboard → Keyboard Shortcuts to rule that out.
2. Test on a different OS version. Since you're on macOS 15.7.7, if you have access to a Mac running Tahoe (macOS 26), it would be really helpful to know if the same issue occurs there. Completely understand if this isn’t an option at this moment, though that'll help us determine whether the OS version is a factor.

I'll keep an eye out for your reply, and thank you again for sticking with me as we troubleshoot this.

Hi ​@TeeterTotter — checking back in. I've been in touch with our engineering team and they're investigating additional reports to identify the root cause. We'll follow up here as soon as there's more to share.

If anything changes on your end, let us know.

Hi Tom, unfortunately the bug is still very much active for me even after multiple tab reloads and system restarts. 

This issue occurs on BOTH the Figma Desktop App and Google Chrome Browser. And it’s happens even when I try to open figma with other device.

To clarify, the general "Copy/Paste Properties" (Ctrl+Alt+C) is working fine, but the individual property rows are completely messed up:

1. EFFECT ROW: The issue is STRICTLY and EXCLUSIVELY isolated to copying an INDIVIDUAL EFFECT row (e.g., clicking on a specific Drop Shadow, Inner Shadow, or Layer Blur row, pressing Ctrl+C, and trying to paste ONLY that effect onto another object via Ctrl+V). Figma completely fails to register the selection of that specific effect row, causing it to paste the previous item from the clipboard instead.

2. STROKE ROW: Additionally, I just found out that when I try to copy an individual STROKE row via Ctrl+C and paste it onto another object, Figma mistakenly applies it as a NEW FILL using that previous stroke's color instead of applying it as a stroke.

It seems the engineering team's recent fix broke the indexing/focus of the right sidebar property panels entirely for both desktop and browser versions. Please reopen and double-check this ASAP!

Hey ​@Kiratinski, thanks for bringing this to my attention and sorry for the slow reply. These details help a lot.

Quick gut-check that I've got it right: Copying an individual effect row (say, a specific drop shadow) with Ctrl+C pastes the previous clipboard item instead of that effect, and copying an individual stroke row pastes it as a new fill rather than a stroke. Is that accurate?

I tried to reproduce it on my end and wasn't able to hit it. Since you're seeing it across the Figma Desktop App, the browser, and multiple devices, the fastest way for us to dig in is to see it directly. Two things would go a long way: a short screen recording of the steps you're taking, and view access granted to support-share@figma.com with a file URL where it happens.

Please let me know if this is still happening and I'll get the investigation started. Really appreciate your patience.

Gut zu wissen, dass das Problem inzwischen durch das Engineering-Team behoben wurde. Falls die Tastenkombinationen weiterhin nicht reagieren, würde ich zuerst den aktuellen Tab neu laden und anschließend die Desktop-App einmal vollständig schließen und neu starten. Auf dem Mac sollten Cmd + Option + C zum Kopieren und Cmd + Option + V zum Einfügen der Eigenschaften wieder funktionieren. Es kann außerdem sinnvoll sein, die Funktion zunächst an einem einfachen Textelement zu testen, um auszuschließen, dass bestimmte gemischte Formatierungen oder Ebenentypen das Ergebnis beeinflussen. Bei mir klingt das eher nach einem Update- oder Cache-Problem als nach einer Einschränkung älterer Intel-Macs.

This is still very much broken.  please fix, it’s one of my most used shortcuts and extremely frustrating.

Option Ctrl C, Option Ctrl V does not paste the color tokens correctly.

If I am in a Darkmode frame, and copy properties from Object A (that is using dark mode tokens), onto Object B within that frame (dark mode), it pastes the light mode token value. 

To get it to switch back to the right color, i have to go to right panel and switch to a different token then switch back and it works.

Please fix this, its been going on for months.

Hey ​@ajk 👋 Sorry to hear you’re running into this. My teammate ​@Tom Reem had a few requests that will help us get this triaged to support:

Two things would go a long way: a short screen recording of the steps you're taking, and view access granted to support-share@figma.com with a file URL where it happens.

Please let me know if this is still happening and I'll get the investigation started. Really appreciate your patience.

If you have a few minutes to help with that, we can get the ticket open and get this to the right folks on our side. Thank you! — Jaycee

Hey ​@ajk — weighing in here as well. I touched base with the Technical Quality team, and they're reviewing a new set of reports. As Jaycee mentioned, we'd love to take a closer look at the file where this is happening — it'll help us determine if what you're seeing is related to what we're already tracking. Please check your inbox for a message from me tied to ticket number: 2053821.