Be a Beta Tester for Penpot’s Plugins System. Call for creators!

Penpot Plugins are coming!

We are about to launch the beta of our much-awaited Plugins System and we are looking for creators to be among the first ones to build plugins in Penpot.

I always say that at Penpot we are not only building a product, but also a community. The influence between the product and the community goes both ways. The product helps the community while the community shapes the product. We strongly believe that plugins will play a key role in empowering the community on its path to making Penpot the design tool of our dreams.

We already provide options to integrate Penpot into your workflow. The open API, access tokens, and webhooks have been proven great. We also understand that the next natural step forward is having a plugin system that will bring the flexibility that creators need -we intentionally avoid the word “developers” here because we are aware that designers and other roles can also build plugins- to create and publish their own custom extensions.

The development of the basic system to create plugins is pretty much advanced. You can see some examples in action in these 5 hands on use cases that we recently showed in a live demo. In these examples, we see plugins that can both read and write the document model and also access the assets library.

Our approach to plugins

We want to give users the power to extend Penpot’s capabilities in a meaningful way and provide value to other users (and themselves) with as little friction as possible, and also with the peace of mind that you are not going to break anything at Penpot. That is why:

  • Plugins can be written using standard web technologies such as Javascript, CSS, and HTML.
  • Plugin development is highly decoupled from Penpot’s development environment. Nope, you don’t need to know Clojure or comply with our contribution guidelines.
  • Plugins are sandboxed and executed in a separate process to prevent conflicts with Penpot features and security vulnerabilities.

It looks like we have all figured out, so why this beta test?

Given the experimental nature of this brand-new plugin system, there is a specific level of uncertainty that we want to reduce. This beta testing will help us identify and address any issues or areas for improvement, ensuring a more refined and user-friendly plugin system by gathering feedback.

The scope of this test is reduced to the “creator flow” (building plugins). In the future, we will consider doing a similar practice for the “consumer flow” (using plugins).

The main questions that we want to answer are simple:

  • Can users develop plugins in a user-friendly way?
  • Are documentation and support materials clear and comprehensive enough?

Who should join the beta testing?

Anyone with basic knowledge of web development (JS, CSS, and HTML standards) is welcome to participate.

Will there be help?

Yes, of course. Once you join the test process, we will provide guidelines, plugin templates, and a UI kit with basic CSS and components. We’ll also be available to give direct support if needed.

How can you join the beta test?

Simply email us at with the subject line “Plugin Beta test volunteer.” In the email, please share a brief overview of your role and if you have some experience that might be relevant to this test. And we’ll get back to you to let you know whether your application has been accepted.

We are beyond excited and looking forward to seeing what can come out of the creativity of our amazing community!


Don’t miss the opportunity, we’re still looking for volunteers !


I’m happy to help. I’ve worked on two Figma plug-ins, one for the Bitcoin UI Kit, and one for Bitcoin Icons, and I’d like to feel out the possibilities in Penpot.

The former plug-in provides a series of helper tools for automatically preparing screens for export, listing components from external files, listing text fields without text styles, etc. Those are very helpful when managing a big library (or design system) file that needs to have a super clean structure. You can find it here.

The latter lets you quickly browse and insert icons from the Bitcoin Icons set. You can see it here.


Hi @Christoph,

Those are great plugins! We’d love you to participate in the betatest. Could you write to so we can include you in the invite list?


Awesome. I just sent the email. Thanks.


I’m happy to help. +1
email send.

Very good news.


I wrote some days ago but didn´t get response or I missed it.
Could you add me please? @myfunnyandy @carolina.portugal

Same here, still waiting.

1 Like

You all should get an ack mail soon (it’s been a weekend and bank holidays and we do not send automated responses).

We estimate that the test itself will start in a couple of weeks, we are still wrapping up things and recruiting volunteers.

It feels great to see this level of interest!


Thanks a lot for the reply, I didn´t want to miss it :slight_smile:
Btw, already trying design tokens in penpot and it fells great! Token Studio partners are doing an amazing work. Well done everyone
:clap: :clap: :clap:


Happy to join, I would like to transfer some of my Figma plugins over:
@david51 – Figma ^^

+++Mail send

1 Like

I have already sent the email to you, but I would also like to mention that I want to attempt migrating the functionality from my plugins for Figma:

It would be disappointing not to receive an invitation. :pensive:


Do you need a help with beta testing from the professional QA expert?
Try it for 30 days for free! :wink:

Hopefully, the Beta Test is still open to new volunteers!?

we already have our own QA team, but thanks for the offering :slight_smile:

We will send the invitations in the next few days. If you want to be included write soon (ideally today) to so we can include you in the invite list!

1 Like

Migrated my simple PDF Viewer plugin from Figma to Penpot, here is the link for testing →

What I’m currently missing for this plugin is the option to resize the plugin-window.


I put together a simple plugin, called “Day & Night”, for creating light/dark color palettes and switching between them. Would love to hear if it’s useful, any bugs you may encounter, and ideas for improvement. You can see how it works in the video intro and get more info in the repo.