On the WebGL renderer, a sync re-measure of copies shared a 40 ms batch with user resizes of the main text. The batch skipped the component sync when any request asked for that. So a resize of the main (grow type, font size, paste, search and replace) often never reached copies on other pages or in other files, and the viewer and exports showed the old size. A batch now skips the sync only when every request asks for it, the same rule as :save-undo?. Such an edit costs one extra short sync round. That round holds only skip requests, so it stops after one pass. A copy that the sync switched from fixed to auto-grow was never re-measured, because the check read the grow type before the sync. The check now reads the grow type that the change sets. A copy that the sync makes fixed is not re-measured. A sync started without an undo group (library update dialog, color and typography sync) committed with a fresh group, and its re-measure and layout pass took other ones. Ctrl+Z first undid only the re-measure and left the copies in the old box. The sync now picks its group when it runs: inside an undo transaction (color, typography and asset deletes) it takes the transaction's, otherwise a fresh one. The re-measure and layout pass share it, so one undo reverts the edit, the sync and its follow-ups, and a failed save rolls them back together. On the SVG renderer, opening a page resized a copy with no position data even when its size had not drifted. Measured sizes round up, so 17.4 became 18. The measurement from that resize then landed on the user's last undo entry. The heal now reports whether it resized, and the check phase resizes only when the size drifted. The SVG page-open check covered only texts with overridden content. A copy loses its touched flags, so a label overridden inside a main (a Button label in a Card main) was never checked in the main's copies, and its heal skips the component sync. The check now covers every auto-grow text inside a copy, as the WebGL check does. The heal's reflow now skips the component sync too: without undo it touched the main component on every page open. A page-open check measured with a font that failed to load wrote the fallback font size. It now writes no size then; a copy without position data still gets it. The WebGL and SVG renderers can measure a text differently; a gap over 1 px makes each page open by a user of the other renderer write the size back. Two browsers on the SVG renderer can do the same: a long auto-width line can differ by more than 1 px, and an auto-height text can wrap a line differently. This is a known limit, noted in the text-heal docstring. The drift check moves to text-size-drifted? in app.common.geom.shapes.text, and takes a tolerance. Both renderers use it: 1 px for the SVG check and the WebGL page-open check, 0.1 px for the WebGL font-load check. The WebGL check did not skip axes that fill their layout parent, so those texts looked stale on every page open and were resized for nothing. It now reads the stored width and height and skips fill axes. The sync docstring and a test message gave the wrong reason for :skip-component-sync?. :ignore-touched stops the resize from marking :geometry-group. :skip-component-sync? stops the re-measure commit from starting another sync. "Remasure" is now "re-measure" in identifiers, test names and comments. The sync docstring now states that an auto-grow copy takes the main's size on each geometry sync, also with overridden content, until the re-measure or the page-open check corrects it. The sync's undo comment no longer says the layout pass gets the sync's undo group: the layout buffer drops it, and the pass joins the same undo entry through :stack-undo?. Tests: heal undo tests cover mixed user and sync batches in both orders, and undo for both renderers. A heal leaves the undo stack unchanged, and undo reverts the user edit. A heal reflow skips the component sync. Sync tests cover a copy that becomes auto-grow (re-measured) and one that becomes fixed (not), and a sync with no undo group that shares one with its re-measure, also inside an undo transaction, with and without a group of the edit. Viewport tests cover no resize without drift, a drifted copy that resizes and settles, the check of every auto-grow text in a copy, and no size write from a failed font. Component tests mount the SVG renderer: a drifted copy is measured once to check and once to settle, with no undo step, and a matching copy is measured once. Stale-selrect tests cover skipped fill axes. The drift tests move to common-tests.geom-shapes-text-test, with tolerance and grow-type cases. Relates to #12721 AI-assisted-by: claude-opus-5-5
Website • User Guide • Learning Center • Community
Youtube • Peertube • Linkedin • Instagram • Mastodon • Bluesky • X
Penpot is the open-source design platform for teams that build digital products at scale.
Penpot’s key strength lies in giving you full ownership of your design infrastructure. Built on open source and designed for self-hosting, it puts teams in complete control of their design environment supporting strict compliance and governance requirements. Whether used in the browser or deployed on your own servers, Penpot works with open standards like SVG, CSS, HTML, and JSON.
Real-time collaboration strengthens this foundation, helping teams scale and bring design closer to the product through top-tier capabilities. Additionally, developers feel at home using Penpot, because design is expressed as code, enabling a direct translation and shipping products faster.
Best-in-class native Design Tokens provide a single source of truth between design and development. They ensure consistency, improve collaboration, and make it easier to manage complex design systems.
The MCP server takes it further by enabling multi-directional workflows between design and code. A powerful open API and plugin system makes the workspace programmable, enabling automation, AI-driven workflows, and integrations with the tools and systems you already use.
With CSS Grid and Flex Layout, teams can design responsive interfaces that behave like real code from the start.
Combined, these features turn Penpot into a full-stack design platform for building scalable design systems and fully integrated product development processes.
If your organization is scaling and needs extra support, we’re here to help. Talk to us
Table of contents
Why Penpot
Penpot connects design, code, and AI workflows through a code-based approach, making designs readable by developers and AI via the MCP server. This approach helps teams ship what’s actually designed and manage design systems at scale with powerful design tokens. As a self-hosted, open-source and real-time collaboration platform, Penpot offers full flexibility, security, and ownership without vendor lock-in. Learn more about why Penpot is the platform for your team.
Plugin system
Penpot plugins let you expand the platform's capabilities, give you the flexibility to integrate it with other apps, and design custom solutions.
Designed for developers
Penpot was built to serve both designers and developers and create a fluid design-code process. You have the choice to enjoy real-time collaboration or play "solo".
Inspect mode
Work with ready-to-use code and make your workflow easy and fast. The inspect tab gives instant access to SVG, CSS and HTML code.
Integrations
Penpot offers integration into the development toolchain, thanks to its support for webhooks and an API accessible through access tokens.
Building Design Systems: design tokens, components and variants
Penpot brings design systems to code-minded teams: a single source of truth with native Design Tokens, Components, and Variants for scalable, reusable, and consistent UI across projects and platforms.
Getting started
Penpot is the only design & prototype platform that is deployment agnostic. You can use it in our SAAS or deploy it anywhere.
Learn how to install it with Docker, Kubernetes, Elestio or other options on our website.
Penpot Enterprise
Penpot Enterprise is our paid plan for organizations that need to scale their design work across multiple teams with advanced governance, security, and administration. Manage teams and access from a centralized Admin Console, configure advanced permissions, and connect your identity provider through SSO. Available for cloud and self-hosted environments, it combines enterprise controls with Penpot’s open-source foundation and open standards.
Community
We love the Open Source software community. Contributing is our passion and if it’s yours too, participate and improve Penpot. All your designs, code and ideas are welcome!
Want to go a step further? Become a Penpot Ambassador and help grow the Penpot community in your region while contributing to a global, open design ecosystem.
If you need help or have any questions; if you’d like to share your experience using Penpot or get inspired; if you’d rather meet our community of developers and designers, join our Community!
Categories include:
- Ask the Community
- Troubleshooting
- Help us Improve Penpot
- Events and Announcements
- Penpot in your language
- Education
Code of Conduct
Anyone who contributes to Penpot, whether through code, in the community, or at an event, must adhere to the code of conduct and foster a positive and safe environment.
Contributing
Any contribution will make a difference to improve Penpot. How can you get involved?
Choose your way:
- Create and share Libraries & Templates that will be helpful for the community.
- Invite your team to join.
- Give this repo a star and follow us on Social Media: Mastodon, Youtube, Instagram, Linkedin, Peertube, X and BlueSky.
- Participate in the Community space by asking and answering questions; reacting to others’ articles; opening your own conversations and following along on decisions affecting the project.
- Report bugs with our easy guide for bugs hunting or GitHub issues.
- Become a translator.
- Give feedback: Email us.
- Contribute to Penpot's code: Watch this video by Alejandro Alonso, CIO and developer at Penpot, where he gives us a hands-on demo of how to use Penpot’s repository and make changes in both front and back end.
To find (almost) everything you need to know on how to contribute to Penpot, refer to the contributing guide.
Resources
You can ask and answer questions, have open-ended conversations, and follow along on decisions affecting the project.
✏️ Tutorials
🏘️ Architecture
🧑🏫 UI Design Course
License
This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0. If a copy of the MPL was not distributed with this
file, You can obtain one at http://mozilla.org/MPL/2.0/.
Copyright (c) KALEIDOS SUBSIDIARY SL
Penpot is a Kaleidos’ open source project