Skip to main content
Question

Will classic plugins be able to use PropKit and the new Generative Plugin APIs?

  • June 25, 2026
  • 3 replies
  • 74 views

jinson

HI Figma Team,

I've been browsing the new Generative Plugin capabilities, especially the new Tools experience that appears directly on selected layers, and I'm curious about the roadmap for existing (classic) plugins.

Is there a timeline or any documentation explaining whether classic plugins will eventually be able to use PropsKit and these new APIs? I've searched through the available documentation but haven't found anything that discusses migration or interoperability.

My concern is that many developers have invested years building and maintaining classic plugins. The new Generative Plugin model is exciting and lowers the barrier for creating plugins, which is great. However, it feels like there isn't a clear migration path for existing plugin developers.

It would be helpful to know:

  • Is there a plan to expose PropKit and the new layer-level Tools APIs to classic plugins?

  • Will there be an official migration path from classic plugins to the new Generative Plugin architecture?

  • Or are these two ecosystems expected to remain separate going forward?

From a developer's perspective, it would have been helpful to have some early guidance that these APIs were coming so existing plugins could be designed with migration in mind, rather than potentially having to be rebuilt.

I'd appreciate any clarification on the long-term direction. Thanks!

3 replies

adamsmasher
Figmate
  • Figmate
  • June 25, 2026

Hey, ​@jinson! Thanks so much for checking out generative plugins. Those are very valid questions for a long-time plugin developer. 

 

While I don’t have an answer to your questions right now, I did share this with the team for review. Did you have any other related questions that would be specific to migrating existing plugins over to generative plugins?


jinson
  • Author
  • New Member
  • June 25, 2026

Yes. I have two plugins that mimic the concept of shaders/effects, and another plugin that heavily depends on the Launch Data API.

I can see that the new generative plugins have access to a much better API, including native-style long-lived controls.

If these capabilities were also exposed to classic plugins, it would be much easier for us to adopt the latest features. My concern is that as users start adopting the new generative plugins with their richer controls, the overall experience of classic plugins will feel increasingly limited. Over time, that could make the classic plugin ecosystem feel obsolete, even if the plugins themselves are still useful.


adamsmasher
Figmate
  • Figmate
  • July 2, 2026

That makes sense - you’d definitely benefit from having parity between classic plugins and generative plugins (and even more so by migrating to a generative plugin). I checked with the team and have more info on this I can provide:

 

Can my classic plugin use the new APIs that agent-built plugins use?

Yes - new capabilities will be released to the Plugin API generally. We also plan to make the PropsKit, our UI kit for plugins, and on-canvas handles available to classic plugins in the coming months.


Can I migrate my plugin to be Figma hosted? What does migrating a classic plugin to Figma-hosted actually involve?

Later this year, we plan on launching the option to upload your existing plugin code into Figma's hosted workflow. It's optional (classic plugins aren't going anywhere), but migration will give you access to the same authoring tools as generative plugins.

 

Hopefully this should give you and other plugin developers maximum flexibility in terms of plugin creation and management. Let me know if you have any other questions!