Create one prototype across the pages in a file

Amen…! Ten times Amen!

An imperfect solution for your case is to have the tooltip as a part of the component, absolute positioned. Every time you use this component in prototype, you’ll have to modify the auto layout order so the tooltip comes on top…

There are several discussions on this topic on this site, but most are outdated, so I want to bring this issue back to Figma’s attention.

It would be INCREDIBLY nice to prototype across multiple pages. I’ve been using Sketch for the past 4 years but recently switched to Figma and noticed this feature is missing.

To give you a better ideas as to what I’m referring to:
I would like to place all my master components on their own components page, and separate out all of my website sections into pages for a nice clean file while still having a seamless prototype. For instance, in Sketch, my files were organized like this:

• Page 1: Login and Home page designs
• Page 2: About page and contact form
• Page 3: Symbols/Components: All local symbols

This organization is very clean and allows me to hand off specific pages to the developers or only show clients the pages that are complete.

If I use this same structure in Figma, I’m unable to prototype the site as a whole. For example if I wanted to link the Home page to the about page, I’m not able to. This also means that my imported Sketch files are basically useless.

I know there’s going to be a learning curve when adopting a new software, but I’m growing incredibly frustrated with the amount of features that are “missing” compared to sketch or are just flat out bugs.

pleaseeeee this needs to happen 🙏

This has sooooo many votes (just added mine), I really hope it’s being worked on!

Now deep into year four of waiting for this feature… I have projects that look like a grenade went off in Legoland on spaghetti night. I’m forced to maintain prototypes in one page, despite the need. It’s blatantly obvious that this is necessary. Clear out whatever code debt and roadblocks you’ve accumulated. Add this feature.

Workarounds-be-damned! Is it not apparent how many customers you may have lost, or new customers left on the table because this hasn’t been moved up in the roadmap?

We need something more than the occasional “Thanks, we’ve merged your comments” or a 3-year old comment that you’re aware of this need.

Communicate with us. Tell us something. We work with developers, we promise, we won’t bite. (Or is it byte?) Just give us whatever management-approved message tells us there’s a light at the end of this tunnel. Or some of these community members will start biting.

My company is at risk of joining others who’ve moved on to products that solved this fundamental need a while ago.

Still in 2024, searching for this feature 😀

I’ve spent far too long trying to find a solution/hack for this need - it seems like a fundamental requirement!

Yes! Please please please make this one of the top priorities, so many votes for this.

First off, I’d like to commend you on the fantastic piece of software that is Figma. Since the inception, you’ve continuously pushed the boundaries of what is possible in the design world, making our lives as designers and creatives notably easier.

Yet today, I reach out to address a feature that has been in high demand, surfacing again and again in forum threads, and garnering substantial upvotes. This is the addition of Cross-Page navigation.

The Paradigm Shift

For the uninitiated, cross-page navigation allows for interactions where a user clicks on an element in one page, which then navigates them to a frame in another page.

This presents an exponential increase in navigational efficiency and interconnectivity across different pages. It’s akin to the transition of the web from static individual pages to the interconnected, hyperlinked behemoth we have today.

Impact and Importance

From complex projects that have multiple user flows spanning across different pages to shared components and design systems used in various contexts, cross-page navigation manifests as a significant game-changer.

This feature could drastically reduce the time needed when testing multi-flow processes, making UX/UI designer’s workflow more efficient, and helping usability testers to have a more cohesive, fluid experience during their tests.

Echoing the Voice of Figma Users

Tousands of Figma users have raised their voices, asking — sometimes pleading — for this feature. The need is evident and the support overwhelming. Let’s consider a few instances:

“I have main nav where each item stands for different page, it’s important to be able to switch from frame to another page.”

_“Figma’s prototyping is really weak without cross page linking, especially when maintaining more expansive design systems.”_

The overwhelming demand suggests not only the desirability for such a compelling feature, but highlights that this is a necessity for many, both designers and clients. In an environment that is rapidly changing, cross-page navigation is no longer a luxury but an expected standard.

Conclusion: A Call to Action

With user-centred design at heart, it seems clear that this is a feature whose time has come. I humbly plead with you, dear caretakers of this fine tool, to please prioritize the addition of cross-page navigation in the roadmap of Figma’s forthcoming updates.

As the collaborative interface design tool, Figma has an exceptional opportunity to pioneer this widely-anticipated upgrade and once more prove its commitment to the community by responding to their needs.

Thank you for considering this request. I hope to continue seeing Figma evolve and impress us with its innovative tools and features, leading the design world towards even better ways to create and connect.