Hi, I want to duplicate a file but doing so doesn’t duplicate version history. A newly duplicated file has no history at all. Is there any way to export version history or make it duplicate as well along with the file?
If Figma doesn’t provide such a functionality is there any plugin you can recommend? I have a quite big files with around 500 versions and “Figma Comments & Version History Exporter” plugin seems to support only small files (around 200 versions looks to be the limit).
Cheers
I guess it must not be available. Tried every possible way. Would be cool, if it were possible to make it happen.
Did you ever find a way around the 500-version limit?
I’m looking at the same archive/duplicate problem and trying to understand what actually broke: version count, file size, pagination, permissions, or the duplicate not being able to carry history back in.
If Figma can’t recreate the history inside the copy, would a clean export/audit trail have helped, or did it need to live inside the duplicated file?
I didn’t face the 500-version limit tho.
The largest file I work on has 2543 (!) version history syncs:
I’m unable to duplicate this history along with the newly duplicated/exported file. The plugin I shared in the initial post can’t handle it. It looks it supports only reasonably small files.
That screenshot helps. When the plugin fails on a file that size, do you think the blocker is mainly the number of versions / file size, or the fact that Figma won’t carry history into the duplicated file at all?
I’m trying to understand whether a useful workaround would be a searchable/exportable audit trail of the version history, or whether it really needs to preserve actual restore points inside Figma.
I think it’s the last one - Figma not carrying history into the duplicated file at all. Because when I try with a file that has around 250 version history syncs Figma doesn’t carry history at all but the plugin does.
What do you mean by “searchable/exportable audit trail of the version history” vs “it really needs to preserve actual restore points inside Figma” - aren’t these the same? Or do you mean the former is history being exportable with selected syncs and the latter is exporting full history as it is?
Yeah, I meant those as two different levels.
An exportable/searchable audit trail would be more like a readable history report you can keep or share, but it would not make the copied Figma file roll back to old states. Preserving restore points inside Figma would mean the duplicate actually keeps usable version checkpoints.
For your case, is rollback inside the copied file the must-have, or would a complete external history/export solve enough of the archive problem?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.