+1 here to continue the requests coming, as I search for solutions to my giant prototype turned nightmare

+1, really need this to create organized prototypes based on more complex design structures.

As probably mentioned multiple times. Having complex workflows is convenient to organize as seperate pages. Otherwise one looses track. Now converting these screens/states into a prototype it’s a Must-have to be able to do so without any duplication workarounds or such. It’s not a nice-to-hace it’s a most-have capability!

How on earth has this not been implemented yet? It’s a fundamental requirement of a web prototyping tool.

Add another vote… having to copy stuff to move it to a single page to have a prototype flow is crazy cumbersome. And if I tweak something in the copied element, I have to remember to do the same in the “original”.

It’s pretty odd, because it seems like a crazy common use case. The technical challenges must be legendary or something.

I suppose this topic has not moved forward so far, but nothing stops us from commenting here as to how helpful this feature would be.

I created a single file with a single page dedicated to the prototype. I use the rest of the pages as an archive for the screenshots, so that I can edit them more easily. Come on guys, let’s make this feature online!

+1 My team and I also need this feature ++++

New in Figma and this was the first pain I notice.

Please add this feature. This should be a must have! 🙂

Every vote helps for this dying feature request!

Really important for correct usability tests on desktop: Scrollbars in presentation view for scrollable elements. (changeable if they are permanently visible or just when the cursor enters the respective area) is a must when testing for desktop. There is no chance or workaround since no plugins work in this view.

Your vote and/or comment would help a lot: Display scroll bar in prototype preview mode

I’m sure someone has posted a solution already in this long thread. If you’re still looking for a solution, here is a workaround:

Say you have two flows (we’ll call it FLOW-A & FLOW-B) on separate pages. To connect the flows seamlessly in a prototype from a frame of FLOW-A to a starting screen in FLOW-B:

1. Open FLOW-B in a prototype view, click on share prototype, & copy link (making sure appropriate permissions are selected)


2. Go Back to FLOW-A, select the element you want to link to the starting screen in FLOW-B


3. Go to prototype mode, and select On tap > Open link > paste the link copied from FLOW-B here and uncheck “Open in a new tab.”

Now, the screens of the two flows should be connected in a single prototype view. 🎉

+1 for ability to link from one page to another page in prototypes (without work arounds).

Building a design system I would much rather have a page per screen, grouping it’s tabs/variations in one, easy to view, place. Right now I have all the screens (and variations) in one, very full, page to enable a fully clickable prototype.

Not seamless. Awful workaround. Does not give Ligma an excuse not to have this feature added.

Unfortunately, this is too slow, because it seems to be trying to load the entire content of the page, so you will always get that loading screen, and will never flow seamlessly. It is even slower for linking 2 projects.

I think that feature is only ideal for opening an external link because you are not actually linking screens, you are linking URLs.

This is definitely a huge thing that Figma missed from the start, and that is why its taking them so long.

I can’t believe that they missed this basic feature.

This feature is definitely needed. I work with components and component variants for different devices. So the only option is to keep ALL components, desktop AND mobile prototype in the same page

this is also my problem I want to connect the component like button when clicking it will navigate to other screen but my problem is that the screen is on the other pages within the file when i dropdown to the navigation panel i can’t see the screen that I would like to connect it because its on the other pages in the same file.

It is very important while I create a button component in a “component page” with an overlay tooltip message while hovering, but the tooltip doesn’t pop up for the instance of the button in another page. Common! do something! since 2021…

Dear Diary,

Here we are, on day 1107 of my desperate plea to the Figma gods, begging for the divine gift of prototyping across pages. Alas, it seems my prayers fall on deaf pixels, or perhaps they’re just trapped in some endless loop of version control purgatory.

As I sit here, staring at my screen like a deranged squirrel watching a digital nut disappear into the void, I can’t help but wonder: what does it all mean? Is life just a series of unfulfilled feature requests, doomed to be filed away in the forgotten corners of a backlog? Or perhaps it’s more like a nested component, waiting to be detached and set free.

In this Kafkaesque nightmare of design limitations, I find myself questioning the very fabric of reality. Are we but sketches on the canvas of existence, constrained by the borders of our artboards? And if so, who holds the eraser?

But I digress. Let us not dwell on the metaphysical quandaries of our digital existence. Instead, let us revel in the absurdity of it all. For what is life without a healthy dose of dark humor?

I imagine the Figma developers, huddled in their code caves, frantically trying to appease the masses. Do they hear our cries for multi-page prototyping, or are they too consumed by their own nested frames of despair? Perhaps they too yearn for the freedom to link between pages, like nodes in some cosmic wireframe.

Yet here we are, trapped in a perpetual state of click-and-drag monotony, like Sisyphus rolling his boulder up the hill, only to watch it tumble back down to the bottom of the artboard.

But fear not, dear diary, for amidst the chaos and frustration, there is still hope. Hope that one day, our voices will be heard. That one day, we will click our way to victory, and prototyping across pages will be but a distant memory, like Comic Sans in a world of Helvetica.

Until then, I shall continue my crusade, armed with nothing but my wit and a mouse pointer. For if there’s one thing I’ve learned in this endless quest for prototyping perfection, it’s that laughter is the best debug tool.

Yours in design and existential angst,

-C

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!