Skip to main content
Daniel_Robbins
February 5, 2021

Move a page from one Figma file to another

  • February 5, 2021
  • 239 replies
  • 67765 views

Pretty simple ask: I want to move a page from one Figma to another. I don’t see a way to do it.
Select All + Cut + Paste is not a good solution as I might have locked objects that don’t come with the copy and there might be properties set on the page (background color, etc.) that I might lose.

239 replies

Jeremy_Chevallier
September 14, 2023

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.

Sean_Yeoh
September 19, 2023

+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.

September 20, 2023

+1 This feature is a must

September 22, 2023

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.

Per
October 3, 2023

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)

Ondrej2
October 3, 2023

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

October 5, 2023

Big Fat +1 here.

Khan1
October 16, 2023

@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
Mariam
October 19, 2023

+1 exactly my issue.

Courtney_Hall
New Member
November 1, 2023

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