# Not a roadmap, but… what's coming in Penpot (June 2026) **URL:** \ **Category:** Inside Penpot\ **Created:** [June 3, 2026, 2:19pm UTC](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628 "2026-06-03T14:19:04Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![myfunnyandy](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/myfunnyandy/32/54_2.png) [@myfunnyandy](https://community.penpot.app/u/myfunnyandy)\ **Post date:** [June 3, 2026, 2:19pm UTC](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628/1 "2026-06-03T14:19:04Z")
![Cover for "Roadmap (Updated in June 2026)"](https://europe1.discourse-cdn.com/flex017/uploads/penpot/original/2X/7/722403a7d9ee83b231ba4427e602fa4d1c4cb092.webp) ## What’s next for Penpot? If you read our [2025 “not a roadmap”](https://community.penpot.app/t/not-a-roadmap-recent-current-and-2025-initiatives/7375), you already know the deal: this is not a promise list. It is an open window into what we are working on now, what is coming up, and why. A lot has happened since that post. We shipped **native design tokens** and **variants**. We worked through a long list of **design deal-breakers** (the small and medium fixes that make daily work less painful). **Tokens sync** with external tools is still in progress. The **new render engine** is no longer a distant headline: [it is here](https://community.penpot.app/t/whats-next-for-the-penpot-webgl-renderer/10627), in beta, and getting real. And we built things we did not even picture back then, like the **Penpot MCP server** , because the world (and our community) moved faster than our older roadmap could. We have kept a **six-week release rhythm** on purpose. Not because we love deadlines for their own sake, but because steady improvement is how Penpot stays usable week after week. If you like watching work land in public, our [dev diaries](https://penpot.app/dev-diaries) are the backstage pass. We are quietly proud of that cadence. The design industry is going through a seismic shift: AI, agents, bigger files, stricter enterprise expectations, more design-system maturity. We feel it too, sometimes with vertigo, but mostly as energy. We would rather **ride the wave** than pretend nothing changed. ### Penpot 2.16: a turn of the cycle This roadmap starts from **2.16** ([Penpot 2.16 release: Alegria Geral](https://community.penpot.app/t/penpot-2-16-release-alegria-geral/10626)), which we see as more than another version number: - **Design tokens in the Design sidebar:** pick, check, and apply tokens next to the controls you already use, without bouncing back to a separate panel - **WebGL rendering (beta):** an optional faster canvas for heavy files (off by default until you enable it in settings) - **A big pile of small wins:** on the order of fifty enhancements and sixty bug fixes, so the day-to-day feel improves even when no single headline explains it - **Community at scale:** not one or two patches at the edge, but a unprecedented wave of contributions (import tokens from linked libraries, find and replace, read-only version preview, and plenty more) From here we ask the practical questions: **What’s next? What’s the near future? What are we already building?** ### Where Penpot is heading Penpot is an **open-source, full-stack design platform** on **open web standards**. We want cross-functional teams to **think and build in one loop** : design, dev, ops, and product working on the same intent in the same flow, so decisions do not rot on the way to production. Two ideas keep showing up in every hard decision: - **Remove the gap** between design and delivery: that single loop is the goal, not parallel worlds that drift apart. - **Digital sovereignty:** self-host, integrate, and leave without lock-in. This is how we are organizing the work ahead. Five tracks that are the areas where we want to push Penpot to the next level, with stronger foundations and higher quality: 1. **Reliability first:** keep making render and stability even stronger, so complex files stay fast and trustworthy at scale. 2. **Design systems as infrastructure:** make libraries, tokens, components, and their governance more scalable and easier to run across teams. 3. **AI that multiplies workflows:** build on MCP and structured design data for automation that is useful in real work. 4. **Enterprise with leverage:** deepen self-host and admin controls for larger and regulated orgs, without forking the soul of the product. 5. **Design-to-delivery:** developers as first-class users. Better ways to consume design intent in real delivery work. Plans will change as we learn, ship, and react to feedback. Our priorities will evolve too (and I’m sure that we all agree that lately the context has been especially wild). ## The five tracks Each track below has **Planned** work (what we are committed to pushing forward) and **Candidates** (strong directions we are actively considering, but not locked in yet). * * * ## At a glance [![What's coming in Penpot](https://europe1.discourse-cdn.com/flex017/uploads/penpot/original/2X/2/25c14fd3f7fe29b111fae7494e5637b9f89074ba.webp)](https://design.penpot.dev/#/view?file-id=998a9243-2b34-81b9-8004-a27fc157ab04&page-id=db30b61d-8094-8070-8008-1d81aea503e1§ion=interactions&index=0&share-id=d8d8a01c-9d7b-8030-8008-1dabe5bee2b1&zoom=fit) * * * ## Track 1: Design Experience and Reliability **Goal:** Make Penpot feel faster, more stable, and more trustworthy for daily work, especially on complex files. ### Planned - **New render engine (WASM/WebGL renderer)** → In progress A new rendering architecture to dramatically improve performance and stability at scale. Taiga epic: [Taiga epic #8525](https://tree.taiga.io/project/penpot/epic/8525) - **Stability and reliability improvements** → In progress A focused effort to reduce crashes and stability issues in real-world usage. - **Design deal-breakers** → In progress Design improvements we deliberately held back while the new renderer was still the big bet. With WebGL in beta, that backlog is unblocked and we can ship them (for example: Background blur, Stroke per side, PDFs export improvement, Numbered lists, Image crop, Video player). - **Component overrides and refactor** Strengthen core component behaviour so design system workflows are more predictable. Taiga: [Taiga US-11311](https://tree.taiga.io/project/penpot/us/11311?milestone=262806) · [Taiga US-11028](https://tree.taiga.io/project/penpot/us/11028?milestone=262806) · [Taiga US-12124](https://tree.taiga.io/project/penpot/us/12124) · [Taiga US-10508](https://tree.taiga.io/project/penpot/us/10508?no-milestone=1) ### Candidates - **Variable fonts** Add support for variable font axes and controls. Taiga: [Taiga #3686](https://tree.taiga.io/project/penpot/us/3686) - **File sharing without team access** Share files across boundaries without forcing team membership flows. Taiga: [Taiga #11503](https://tree.taiga.io/project/penpot/us/11503) - **Prototyping: Scrollable boards** Taiga: [Taiga #4519](https://tree.taiga.io/project/penpot/us/4519) - **Prototyping: Component interactions** Taiga: [Taiga #12067](https://tree.taiga.io/project/penpot/us/12067) - **Prototyping: Smart animate** Taiga epic: [Taiga epic #12304](https://tree.taiga.io/project/penpot/epic/12304) - **Visibility in history versions (content, authorship)** Better accountability and visibility when reviewing past versions. Taiga: [Taiga US-14267](https://tree.taiga.io/project/penpot/us/14267?no-milestone=1) - **Size units (cm, pt, in, rem, em, etc.)** Taiga: [Taiga #2328](https://tree.taiga.io/project/penpot/us/2328) * * * ## Track 2: Design System Operations **Goal:** Make design systems even more scalable and maintainable across teams, files, and environments. ### Planned - **Auto-link used libraries on file import** → In progress Keep libraries connected when importing across environments. Taiga: [Taiga #13976](https://tree.taiga.io/project/penpot/us/13976) - **Share a library across teams** → In progress Allow cross-team library sharing with access levels and proper governance. Taiga: [Taiga #12473](https://tree.taiga.io/project/penpot/us/12473) - **Design tokens: Internal libraries and files sync** → In progress Tokens become a real shared source of truth through libraries. Taiga: [Taiga #12015](https://tree.taiga.io/project/penpot/us/12015) ### Candidates - **Design branching (before merging library changes)** Safer workflows for library maintainers to batch changes and publish confidently. Taiga: [Taiga #13981](https://tree.taiga.io/project/penpot/us/13981) - **Design system governance** Pull/push editing flows and permission patterns for shared systems. Taiga: [Taiga US-14268](https://tree.taiga.io/project/penpot/us/14268?no-milestone=1) - **Component slots** Container components with swap-friendly slots that preserve consistency. Taiga: [Taiga #12456](https://tree.taiga.io/project/penpot/us/12456) - **Design tokens GitHub sync** Connect tokens to repo-based sources and providers. Taiga: [Taiga #9968](https://tree.taiga.io/project/penpot/us/9968) - **Variants: Standard states** Taiga: [Taiga #10562](https://tree.taiga.io/project/penpot/us/10562) - **Variants: Nested component copy properties** Taiga: [Taiga #11987](https://tree.taiga.io/project/penpot/us/11987) * * * ## Track 3: Agentic and AI-Native Workflows **Goal:** Unlock safe automation and agent workflows on top of real design infrastructure, without sacrificing trust and control. ### Planned - **Design as a graph (SDG)** → In progress A structured graph representation of design files to enable advanced workflows and AI/ML experimentation. - **Agentic dev environment** → In progress Technical foundations for agent-driven workflows in development environments. Doc: [GitHub doc](https://github.com/penpot/penpot/blob/develop/docs/technical-guide/developer/agentic-devenv.md) - **MCP server improvements** Hardening architecture, documentation, and operability of MCP. Docs: [Penpot docs](https://help.penpot.app/mcp/) · [Taiga epic #12407](https://tree.taiga.io/project/penpot/epic/12407) ### Candidates - **MCP apps** Embedded UIs inside MCP clients (ChatGPT/Claude/VS Code/etc.) to speed up selection, review, and confirmation. Requirements: [Affine](https://app.affine.pro/workspace/4f3c3bb0-6bfe-421d-8277-b304d2473930/MqScVNtTJ1bTsNovH9c4w?mode=page) · Taiga: [Taiga US-14269](https://tree.taiga.io/project/penpot/us/14269?no-milestone=1) - **SDG integrations: GitHub, Storybook** Connect structured design data to delivery workflows. * * * ## Track 4: Enterprise and Self-Host Platform **Goal:** Provide governance, control, and self-host confidence for large and regulated organizations. ### Planned - **Admin Console: Organizations** → In progress Multiple organizations: set boundaries for separate workspaces without losing central governance. - **Admin Console: People section** → In progress Visibility and governance across the org: remove somebody from all teams at once. - **Admin Console: Advanced permissions** → In progress Control who creates teams, brings people in, or moves teams. - **Admin Console: SSO Config** → In progress Familiar sign-in flows and access control for enterprise deployments. ### Candidates - **Admin Console: Plugins allowlist** Control which plugins are allowed in an org. Concrete and easy to explain in enterprise conversations. - **Admin Console: MCP Management** Manage which MCP integrations are allowed in an organization. - **Admin Console: Audit log** Compliance traceability without depending on unfinished infrastructure. - **Admin Console: Org-admin role** Delegation for mid-size and larger companies. - **Admin Console: User directory sync** The natural next step after SSO: keep org membership automatically in sync with the corporate directory. - **Admin Console: Attributes and groups** Transversal sets of people for governance at scale. - **Admin Console: Teams overview** Give the org owner visibility into all teams without needing to be a team member. - **PassKeys and 2FA** Taiga: [Taiga #5692](https://tree.taiga.io/project/penpot/us/5692) - **Self-host sizing and operational guidance** Clear requirements and guidance for self-host environments. Taiga: [Taiga US-14270](https://tree.taiga.io/project/penpot/us/14270) * * * ## Track 5: Design-to-Delivery **Goal:** Give developers and delivery teams even clearer, more actionable design intent and tooling. ### Planned No planned items to announce yet. This track is currently represented by active candidates below. ### Candidates - **Inspect tab improvements** Make Inspect easier and more useful, especially for viewer-only use cases. Taiga: [Taiga #8851](https://tree.taiga.io/project/penpot/us/8851) - **HTML rendering / viewer** More implementation-aligned ways to consume designs. Taiga: [Taiga US-14271](https://tree.taiga.io/project/penpot/us/14271) - **Responsive breakpoints (CSS-based)** CSS-aligned breakpoint modelling for responsive design. Taiga: [Taiga US-14272](https://tree.taiga.io/project/penpot/us/14272) - **Mirror app / devices preview (View Mode responsive and mobile-first)** Better preview and interaction testing across devices and breakpoints. Taiga: [Taiga #12432](https://tree.taiga.io/project/penpot/us/12432) * * * ## Feedback We want this roadmap to stay useful and real. Tell us what you would add, what you would drop, and what would make the biggest difference for your day-to-day work in Penpot. We are all ears. ---
**Author:** ![Simone\_Provenzano](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/simone_provenzano/32/11034_2.png) [@Simone\_Provenzano](https://community.penpot.app/u/Simone_Provenzano)\ **Post date:** [August 15, 2026, 6:26am UTC](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628/2 "2026-08-15T06:26:19Z")
Rem support and auto building variations without having to define all permutations is probably what I miss more from figma. Apart from that Penpot is awesome and this roadmaps show it will. Get even better! Keep going! ---
**Author:** ![a-ng-d](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/a-ng-d/32/11021_2.png) [@a-ng-d](https://community.penpot.app/u/a-ng-d)\ **Post date:** [August 18, 2026, 1:49pm UTC](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628/3 "2026-08-18T13:49:18Z")
Hi @myfunnyandy, The roadmap is crystal clear. Thanks a lot for making it so detailed. I was asking myself about your position on your resources and plugins marketplace, because I’ve seen nothing about it except through the Phrase 3, which is focused on interacting with Penpot using an LLM client. Would you continue to spend any effort on making evolutions to encourage people to make resources or share inspiration? ---
**Author:** ![Frontside](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/frontside/32/11150_2.png) [@Frontside](https://community.penpot.app/u/Frontside)\ **Post date:** [September 3, 2026, 9:34am UTC](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628/4 "2026-09-03T09:34:15Z")
Dear Penpot-Team, one feature I would truly love to see is **auto-scaling font sizes, spacing, and units using the CSS `clamp()` function**. Using `clamp()` for font sizes and spacing is standard practice when creating **intrinsic web design** - that is, automatically scaling responsive web design -and it’s a standard in all the website builds I create. Having Penpot mirror this behaviour would be amazing and would eliminate guess-work for inter-device sizes. Right now, I’m using the technique @LauraKalbag demonstrated in her amazing videos about creating font scales using the `Tokens/Dimensions/density-text/1.25` value and applying it to different font-size tokens - for example: `desktop.text-xl = {desktop.text-l} * {desktop.density-text}` This is such a great way to use tokens, with references to other tokens, to create automatic, unbreakable systems. I want to congratulate you all on this - it’s so much better than Figma’s Variables. The icing on the cake would be using **CSS `clamp()` function** in addition to this system - which right now demands creating desktop and mobile tokens seperatly. Thanks for considering it. Best regards, Patrick ---
**Author:** ![LauraKalbag](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/laurakalbag/32/5014_2.png) [@LauraKalbag](https://community.penpot.app/u/LauraKalbag)\ **Post date:** [September 3, 2026, 9:54am UTC](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628/5 "2026-09-03T09:54:27Z")
I’d love me some `clamp`, and I’d be interested in what other units people consider vital in modern responsive web design? `minmax`? `vw`/`vh`? [`cqw`/`cqh`](https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Containment/Container_queries#container_query_length_units)?! ---
**Author:** ![Frontside](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/frontside/32/11150_2.png) [@Frontside](https://community.penpot.app/u/Frontside)\ **Post date:** [September 4, 2026, 8:24am UTC](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628/6 "2026-09-04T08:24:15Z")
In **addition to breakpoints** , maybe we could introduce **container queries** as well, perhaps at a much later stage. It might be worth exploring the idea and keeping it in the back of our minds. Although this would put us years ahead of other website design and development tools. I know, I know… I’m getting greedy. 😇 EDIT: Ohh @LauraKalbag I totally missed your previous suggestion of cqw/cqh. BTW, yes all of them. 🥰 ---
**Author:** ![Nikola](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/nikola/32/10765_2.png) [@Nikola](https://community.penpot.app/u/Nikola)\ **Post date:** [September 26, 2026, 9:10pm UTC](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628/7 "2026-09-26T21:10:34Z")
Do you remeber [video](https://www.youtube.com/live/TmVuRMf5Ojg?si=bq_vE9zVyHFIGiYt) you made with Krenn from Token Studio, some time ago? You demonstrated how you can use basic math functions in tokens and nest references. It would be great to continue with this idea, imagine being able to define clamp in tokens, define brake points and add logic to your design system. Make components truly intrinsic. ---
**Author:** ![myfunnyandy](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/myfunnyandy/32/54_2.png) [@myfunnyandy](https://community.penpot.app/u/myfunnyandy)\ **Post date:** [October 2, 2026, 6:00am UTC](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628/9 "2026-10-02T06:00:37Z")
> [@a-ng-d](#): > > Would you continue to spend any effort on making evolutions to encourage people to make resources or share inspiration? Hi @a-ng-d, sorry for the late reply, this one slipped under my radar! To be honest, there’s no specific work planned right now to improve the plugins marketplace. That said, it’s far from abandoned: we have an internal team supporting it, and it makes sense to keep doing so, since its activity keeps growing month after month. Where we are putting a lot of focus is on opening up more ways to integrate and interoperate with Penpot. And yes to your last question! Encouraging people to create resources and share inspiration is something we keep pushing through the community, contributions, the ambassadors program and more.