To ensure we’re addressing the right issue, could you let us know if this is happening in the desktop app, in the browser, or both? If you’re using Safari and experiencing this issue, it might be related to a long-standing bug. If this is the case, please let us know so we can add your post to our internal bug report. Looking forward to hearing back from you soon!
If you are using Safari, it is recommended to consider using another browser or the desktop app as a workaround, as mentioned in the second comment on this post. If you have tried everything mentioned in the post and are still experiencing the same issue, I recommend submitting a bug report to our support team for further investigation. Please include a recording demonstrating the issue you are facing. Make sure the entire window is visible, including the properties and layers panels.
Understanding the Issue
Figma paste-to-replace not working typically involves disruptions in clipboard operations when replacing layers or components. Users report inconsistencies between browser and desktop applications, and occasional browser-specific bugs, especially in Safari. A clear reproduction path helps engineers identify whether the problem is isolated to a platform, a particular file, or a broader version issue.
Common Causes and Clues
- Platform mismatch: desktop app vs. browser, or both experiencing the problem.
- Browser-specific bugs: Safari is frequently mentioned as having long-standing issues with certain paste-to-replace actions.
- Selection state: active layers or nested groups might interfere with replacement operations.
- Clipboard permissions: browser security settings can affect paste actions from external sources.
- UI state: open properties and layers panels must be fully visible for the operation to register correctly.
Step-by-Step Troubleshooting
First, identify the environment: desktop app, browser, or both. Then apply the following steps in sequence to maximize the chances of a temporary fix or to prepare a precise bug report.
- Switch environment: test with the Figma desktop app if you are on the browser, or try a different browser if you are on the desktop app.
- Ensure all panels are visible: open the properties and layers panels so that the paste-to-replace action is fully detected by the UI.
- Try a minimal file: create a simple file with a couple of shapes and a symbol or component, and attempt paste-to-replace there to rule out file-specific issues.
- Check for updates: confirm you are running the latest version of the desktop app or browser extension, as patches often address clipboard-related bugs.
- Test keyboard vs. right-click: use both paste-to-replace shortcuts and context menu options to determine if the problem is input-method related.
- Review permissions: ensure clipboard access is allowed in your browser settings, particularly in Safari where stricter controls can affect pasting operations.
- Disable conflicting extensions: temporarily disable clipboard-related or privacy extensions that could intercept paste actions.
- Document with a recording: if the issue persists, record a short video showing the entire window, including properties and layers panels, to accompany a bug report.
Workarounds to Keep Working
When the paste-to-replace feature is unreliable, these workarounds can help maintain workflow momentum while a fix is investigated.
- Use the desktop app: as recommended for Safari users, switching to the desktop application often bypasses browser-specific clipboard bugs.
- Switch browsers: if you’re on Safari, try Chrome or Firefox, which may handle clipboard operations differently.
- Manual replacement: temporarily duplicate the target layer or component and re-link properties manually if replacement fails.
- Clipboard hygiene: clear clipboard contents or restart the application to reset clipboard state between operations.
Reporting a Bug: What to Include
Effective bug reports speed up resolution. If you’re still facing the issue after applying the above steps, submit a report to the support team with:
- A brief description of the problem and where it occurs (desktop app, browser, or both).
- Your operating system and exact app/browser versions.
- A recording demonstrating the issue, ensuring the entire window is visible, including the properties and layers panels.
- Steps to reproduce from a clean file to ensure consistency.
Additionally, indicate whether the problem persists across files or is isolated to a specific project. If Safari is involved, mention any known bugs and the suggested workaround to help triage.
Examples of Effective Bug Reports
Case notes that help engineers quickly identify the root cause often include platform details, a precise sequence of actions, and accompanying media. A well-structured report reduces back-and-forth and accelerates fixes.
For ongoing issues, keep an eye on official updates and internal bug reports that may reflect a growing list of user-reported cases with similar reproduction paths.
Quick tip | The paste to replace shortcut in Figma
As soon as a workaround is validated or a fix is released, you can update the report to reflect new behavior and any remaining edge cases.