Skip to main content
Question

Figma links are breaking on merging

  • August 14, 2025
  • 3 replies
  • 54 views
Dhruv_Srivastava

We wrote stories and linked it to figma components(via copy link to selection cmd+L) within the stories. 

We then did branching and started rolling out incremental updates, but now on merging a branch, the pasted Figma links are taking the users to a cover page and not the component.

Is this normal? How do you work when the components are getting incremental updates? 

3 replies

Tom Reem
Figmate
  • Tom Reem
  • Figmate
  • September 1, 2025

Hey ​@Dhruv_Srivastava — welcome to Figma Forum, and thanks for raising this! I checked with our Technical Quality team and wanted to share some context on what may be happening.

It sounds like the links you created point to frames within the branch file, which means the URLs include the node ID and branch ID. When the branch is merged and archived, those URLs still reference the archived branch rather than the main file node. Does that match what you’re seeing?

Let me know if this helps. If this doesn’t clarify things or if other questions remain, please reply here and I’ll be happy to help troubleshoot further. 🙏🏻

Dhruv_Srivastava
Dhruv_Srivastava

Hey ​@Tom Reem, thanks for the kind welcome, and checking in with the Technical Quality team
So we’ve actively copied links from the main file and not the branch. 

Here’s some additional detail listed with the two separate scenarios we encountered, we have a frame with a modal component...

  1. Contents of the modal got replaced in the merge, link copied was for the whole modal(frame). (Link broke on merge)
  2. Entire modal(contents + frame) got replaced in the merge, link copied was for the whole modal(frame). (Link broke on merge)

Lemme know if you need more info on this. 
Thanks again Tom!

🤗

Tom Reem
Tom Reem
Figmate
  • Tom Reem
  • Figmate
  • September 16, 2025

Hi ​@Dhruv_Srivastava — thanks so much for laying out these scenarios, and apologies for the wait. The extra detail is really helpful for narrowing this down and I’ve raised this internally as well.

If you’re open to it, I’d love to loop in our Technical Quality team directly so they can take a closer look at the specific file where you’re running into this. Catching the behavior directly in context will help with next steps. To kick things off, could you please fill out this form and include:

  • a link to the file where this is happening
  • ‘can edit’ access granted to support-share@figma.com for the impacted file (this will not impact billing)
  • a screen recording showing the issue in action (if possible).

Please keep me posted on how it’s going — I’m always happy to dig deeper. 💯

Terms & ConditionsCookie settingsAccessibility statement