Commenting to add my support and keep this topic open. Come on, Figma team. This can’t be that complicated to build! Granted, it’s also not hard for me to select all, copy, create new page in other file, and paste.

+1. My file is getting larger and there isn’t a way for me to move some pages, along with the comments, to a new file to lighten up the memory usage.

+1 This feature is a must

Our company Figma file has unfortunately become very large in the meantime. I constantly get the warning “Almost out of memory”. 77% is already occupied.

We work mainly with one file that developers can always access the whole file and also find everything independently.

To solve the problem with memory issues I would like to copy individual pages into an archive file. It would be very helpful if you could copy complete pages into a new file (in the same project) without losing prototypes or links to the library.

I have only 23% memory left… so hopp hopp Figma 🙃 Hope to see this feature soon.

Figma also has a bug related to this. If you copy a page with “on tap” interactions those are not removed but rather set to “None”.

This means that if you copy pages, link them to eachother and try to run the prototype that does not work because you’ve now ended up with a lot of interactions for “on drag” (since “on tap” was already used up by the very very handy, on tap > do nothing-event)

+1, can´t believe it hasn´t been implemented yet.

Big Fat +1 here.

@Clara Thanks for sharing, but I guess it is not the Archive way of what a Agile work flow looking for.

I believe what Nick is looking for is similar to mine, which is “Moving pages to a separate file since the sprint is closed/ a year of work is closed.”

Needs:

1. Designers in the team still have to check what had been done before anytime


2. We would like to keep the same file as “sprints of this FY” with different sprints as different pages


3. We would like to move pages of past sprints to another file so those pages won’t eat up the memory


4. We DO NOT want to create a new file for new sprints cause we need to share the link and grant the access again to all the developers/BAs/PMs

+1 exactly my issue.

Just keeping this alive. Still REALLY need this to organize our old files. +1

Posting to keep this up because it’s super useful for file organization.

we also need this functionaility in our design team

Definitely a very fundamental feature. I loved Figma at first but as my project gets complicated I find out deal broker issues like this, so disappointing

Hi there, definitely +1.000.000

Keep this thread opened, this is really needed by lots of users 😉

+1. Please create this feature! When a file hits memory usage capacity and you are forced to reorganize, it really stinks to loose all past comments 😦

+1.000.001

Please Figma!

+1 - thought this would be baked in. You’re stuffed if you start hitting max resource.

+1 Insane this is still outstanding.

This is 100% needed. It makes it impossible for us to move compoents between files without creating a huge mess.

+1 - we need this!

Please please please add this to your FY25 Roadmap. This would have a huge impact on my work. I’ve started on a new team and it has tons of historical data. the team used to have less work and now the business needs have changed amplifying the amount of work going into Figma. Each product design concept should now have it’s own file instead of it’s own page. I went to move a page to new file and see it’s not possible. I CAN NOT loose the historical data. The only work around I can think of is keep the old files and linking back to them. Which means the designs work will not have a single source of truth. Could cause a bunch of confusion. YIKES! Please add aMove a page from one Figma file to another] to your product roadmap.

+1 on this bad boy.

+1, this is really important for any kind of restructuring of a project that has grown naturally and now needs to be seperated into respective projects

This is beyond necessary. Figma, please, please prioritize this asap!

+100 not being able to do this really messes with your workflow. losing comments when simply copying and pasting is a pain. not sure why this hasn’t been tackled yet. seems like a simple need.