Hi team, we have been prototyping some fairly complex web app concepts, and just wanted to understand what happens as we get into really high version numbers (e.g. up version 95 in the one I am looking at right now) – would like some understanding/reassurance of the limits before we really start orienting our prototyping process around Figma Make.
Is there a limit on how many prompts a single file can have?
Are there any risks in having a file with very high numbers of versions? I saw another post saying their file stopped being able to iterate at version 900 because of how large the prompt was getting (with all the history).
Is there a way to “fork” a new file, and this file effectively restarts at version 0 – I was surprised that duplicating retains all the previous versions.
Slightly worried about the usage limits of roughly 80 prompts per month – I could do this in a morning! Are we doing something wrong? I have been very happy with the results (and breaking complex app flows into very small prompts and building it up iteratively – so will obviously expend a lot of prompts).
Would love to know if anyone else has similar questions or experiences. Cheers!
Page 1 / 1
Hi @Willnz ,
I understand your concerns about version history and prompt limits in Figma Make.
As you may know, Figma AI uses a shared credit system across all AI features, so it’s difficult to provide a specific prompt limit per file. However, as mentioned in the article, if you're on the Enterprise plan with a Full seat, you can expect to use about 80–100 Make prompts per month, based on current estimates.
Please rest assured that we’re planning to offer the ability to purchase extra AI credits later this year. In the meantime, credit limits for Full seats are not being strictly enforced.
Note: If you're on the Starter plan or using a non-Full seat, you’ll see an in-product message when you reach your AI credit limit, along with details about when the limit will reset.
High version count and potential risks
I couldn’t find any specific documentation related to issues caused by high version counts. While we wait for more insights from the community, here are a couple of helpful resources:
If you’re experiencing problems (such as being unable to continue iterating) and these steps don’t help, feel free to Submit a bug report, so our team can take a closer look.
Resetting version history
Currently, there’s no self-serve way to reset or delete the chat and version history in a Figma Make file.
If you’re seeing any performance issues and believe that clearing the history might help, we’d be happy to take a look. Please use this form to report it: Submit a report
In the form, include the file URL and grant edit access to support-share@figma.comThis won’t affect your billing.
Thanks,
@Junko3, keeping in mind of your reply, I continued to make my iterations. Today I received a message saying I’ve reached my limit. I’m a full seat paid user. No prior notice has been served for this.
@Junko3, keeping in mind of your reply, I continued to make my iterations. Today I received a message saying I’ve reached my limit. I’m a full seat paid user. No prior notice has been served for this.
Likewise, i have just had the handbreak yanked on too. My first reaction is find an alternative.
@Junko3 - Our company has about 10 seats of Figma, so is this restriction per seat or per company. Is there an upgrade option or do we need to just wait.
Hi team, we have been prototyping some fairly complex web app concepts, and just wanted to understand what happens as we get into really high version numbers (e.g. up version 95 in the one I am looking at right now) – would like some understanding/reassurance of the limits before we really start orienting our prototyping process around Figma Make.
Is there a limit on how many prompts a single file can have?
Are there any risks in having a file with very high numbers of versions? I saw another post saying their file stopped being able to iterate at version 900 because of how large the prompt was getting (with all the history).
Is there a way to “fork” a new file, and this file effectively restarts at version 0 – I was surprised that duplicating retains all the previous versions.
Slightly worried about the usage limits of roughly 80 prompts per month – I could do this in a morning! Are we doing something wrong? I have been very happy with the results (and breaking complex app flows into very small prompts and building it up iteratively GrowthMount– so will obviously expend a lot of prompts).
Would love to know if anyone else has similar questions or experiences. Cheers!
High version numbers like 95 are generally fine, but very large histories (hundreds of versions) can eventually slow iteration or cause issues. There’s no strict limit on prompts per file, but complex iterative workflows can quickly use up monthly prompts. Duplicating a file retains all previous versions, so to truly restart at version 0, create a new file and copy over only the content you need. For complex prototypes, splitting work across multiple files can help manage version history, performance, and prompt usage efficiently.
