Penpot 2.18: New Features for Open-Source UI Design and Team Collaboration
Penpot 2.18 brings several practical improvements to the open-source design editor, with particular attention to vector drawing, typography, shared design systems and teamwork. Announced in September 2026 under the release name “Born This Way”, the update introduces stroke-to-path conversion, dedicated line and arrow tools, improved font previews and more reliable handling of design tokens. It also marks the introduction of Penpot Enterprise, a paid option offering additional administrative controls for larger organisations. The core editor remains free and open source, allowing designers to create interfaces, develop interactive prototypes and collaborate with developers without purchasing a commercial subscription. Rather than radically changing the familiar workspace, version 2.18 concentrates on making everyday design tasks more convenient and giving teams better control over their projects.
Penpot 2.18 Introduces More Flexible Drawing and Editing Tools
One of the most significant additions in Penpot 2.18 is the ability to convert strokes into editable vector paths. Previously, a stroke was primarily a visual property applied to an existing line or shape. Designers could change its thickness, colour and appearance, but working directly with the visible outline was less straightforward. The new Outline Stroke command converts that outline into vector geometry that can be modified independently. This is particularly useful when preparing custom icons, decorative interface elements, illustrations or graphics that require more precise adjustments than ordinary stroke settings allow.
To use the feature, designers select an object with a stroke, open its context menu and choose Outline Stroke. Penpot converts the stroke into an editable path following its visible contours. The resulting shape can be adjusted using vector editing tools, combined with other objects through Boolean operations or exported as SVG. For example, a designer creating a navigation icon can turn a thick line into a shape and modify individual sections without having to redraw the entire symbol. There is one important requirement: Outline Stroke is available when the newer WebGL rendering engine is enabled. Teams still using the previous renderer need to account for this limitation.
The drawing toolbar has also been reorganised to reduce clutter and make frequently used tools easier to access. Penpot 2.18 groups drawing functions into two expandable menus. The shape group includes rectangles, ellipses, lines and arrows, while the free-draw group contains path and pencil tools. Each menu remembers the most recently selected tool, helping designers return to common actions without repeatedly navigating through the available options. Dedicated Line and Arrow tools are another welcome improvement. They eliminate the need to recreate simple directional elements using more complicated combinations of paths and stroke settings, making tasks such as drawing connections, annotations and interface diagrams more straightforward.
Improved Typography and More Consistent Visual Elements
Typography selection receives a smaller but particularly useful improvement in Penpot 2.18. Font names in the selector now appear in their corresponding typefaces, allowing designers to recognise the visual character of each family before applying it to a text element. Previously, choosing between unfamiliar fonts could require repeatedly selecting and testing different options. The new previews make comparisons easier, especially when developing interfaces that need a distinctive visual identity. Designers can assess whether a font appears formal, geometric, condensed or decorative directly from the selection menu, although the final decision should still involve testing real interface text.
The update also improves how design tokens behave when properties are copied between elements. Design tokens are reusable values that help teams manage colours, spacing, typography and other recurring interface properties. Instead of assigning the same colour manually to dozens of buttons, for example, a designer can connect those buttons to a shared token. Penpot 2.18 preserves token references when copying and pasting supported properties, rather than simply replacing them with their underlying values. This seemingly modest change has practical consequences: copied elements remain connected to the original design decisions, making subsequent updates easier and reducing the risk of inconsistent styling.
Consider a product interface containing several screens that use the same primary button colour. If the colour is controlled by a token, changing that token can update the connected elements throughout the design. When copied properties retain their token references, newly adjusted components can continue following the same visual rules. This is especially valuable in projects involving multiple designers or extensive component libraries. The improvement does not replace the need for carefully organised design systems, but it removes a common source of accidental inconsistencies. Together with the typography previews and drawing changes, it makes Penpot 2.18 more comfortable for detailed interface work without requiring designers to change their established methods.
Better Collaboration and Design System Management in Penpot 2.18
Penpot has long supported collaborative interface design, allowing teams to work with shared files, reusable components and interactive prototypes. Version 2.18 builds on these existing capabilities rather than introducing collaboration as an entirely new concept. One of its notable improvements concerns comments within the design workspace. Designers can view and manage feedback while continuing to work on their layouts, reducing the need to switch between editing and reviewing activities. This matters during projects where product managers, developers and designers regularly discuss the same screens. Keeping comments close to the relevant visual elements helps maintain context and makes it easier to understand which changes have been requested.
For example, a product manager reviewing a registration screen might suggest changing the placement of an error message, while a developer might flag a potential problem with the spacing between form elements. These discussions are most useful when the comments remain associated with the design itself. Penpot 2.18 also addresses a keyboard interaction that previously caused difficulties when writing comments: pressing the space bar could activate the hand tool instead of inserting a space into the text. Correcting this behaviour removes an unnecessary interruption from the feedback process. Although such fixes rarely attract as much attention as major features, they can noticeably improve the experience of teams that review designs throughout the working day.
Shared components remain central to maintaining consistency across larger projects. A design team might use one component library for navigation bars, buttons, form fields and notification messages, with individual screens reusing those elements. Penpot supports this approach through reusable components and shared libraries, while design tokens provide a further level of consistency for visual properties. Version 2.18 includes fixes related to component synchronisation and layout behaviour, helping shared elements respond more reliably when their underlying properties change. Designers should still check complex layouts after updating libraries, particularly when components contain nested elements or multiple variants. The release improves reliability but does not eliminate the need for normal design reviews.
Penpot Enterprise Adds Administrative Controls for Larger Teams
A major development accompanying Penpot 2.18 is the introduction of Penpot Enterprise. This paid option focuses on organisational administration rather than placing the editor’s standard drawing and prototyping tools behind a subscription. Penpot continues to offer its open-source capabilities without a licence fee, while Enterprise provides additional controls for businesses managing numerous users, teams and projects. The distinction is important because the needs of an independent designer differ considerably from those of a large organisation. A small team may only require shared design files and ordinary user permissions, whereas a company with several departments may need centralised rules governing access, invitations and administration.
Penpot Enterprise introduces a dedicated Admin Console that allows authorised administrators to manage independent organisations and apply policies across their teams. It also supports organisation-level single sign-on through identity providers, including generic OpenID Connect services, Microsoft Azure Active Directory and Google. Single sign-on allows employees to access their organisation’s Penpot resources using an established corporate identity system. This can simplify account management, particularly when staff join, move between departments or leave the business. Instead of relying entirely on separate access arrangements for individual tools, administrators can connect Penpot to their existing identity infrastructure and manage authentication more consistently.
Advanced permissions provide another important distinction. Administrators can establish rules controlling who may create or manage teams, projects and files, who can invite additional members and which users are eligible to receive invitations. These organisation-wide restrictions work alongside ordinary user roles. For instance, a company may allow designers to edit project files while limiting the ability to invite external collaborators. Such controls can be useful for agencies handling confidential client work or businesses with formal internal security requirements. Enterprise is not essential for every Penpot user, however. Freelancers, students, small studios and many product teams can continue working with the free edition, making the paid offering primarily relevant to organisations requiring more extensive governance.
What Penpot 2.18 Means for UI Designers and Developers in 2026
Penpot’s broader appeal comes from combining interface design, prototyping and developer-oriented workflows within an open-source application. Designers can create screens, organise reusable assets and build interactive flows, while developers can inspect design properties and work with assets intended for implementation. The editor uses familiar web technologies and supports common formats such as SVG, which makes it particularly relevant to teams building websites and web applications. Penpot 2.18 strengthens this existing approach through practical improvements rather than attempting to redefine the entire design process. Its drawing enhancements are useful during visual production, while better token handling and component reliability support the transition from individual screens to consistent products.
The update also includes maintenance work affecting the WebGL renderer, plugins and Model Context Protocol (MCP) integration. WebGL rendering is particularly relevant because it enables newer visual capabilities, including the stroke conversion introduced in this release. Penpot has been developing this rendering engine to improve the handling of demanding design files and more advanced visual effects. MCP integration, meanwhile, provides a way for compatible AI-assisted development tools to interact with Penpot through a defined connection. Version 2.18 addresses problems involving connections when browser tabs are inactive, alongside other reliability issues. These changes are useful for teams experimenting with connected design and development workflows, although MCP remains optional for conventional interface design.
Penpot’s open-source model also gives organisations a choice between using its hosted service and operating a self-hosted installation. Self-hosting can appeal to businesses that want greater control over their infrastructure, data storage and maintenance arrangements. However, it also introduces responsibilities that are largely handled by a service provider in a hosted environment. Teams running their own installations need to consider software updates, backups, access management and server security. The availability of source code does not automatically make an installation secure or maintenance-free. For designers evaluating Penpot in 2026, the practical decision is therefore not simply whether the editor has the necessary features, but also how the chosen deployment arrangement fits the organisation’s technical resources.
Practical Benefits, Limitations and Choosing the Right Workflow
The most useful way to assess Penpot 2.18 is through a realistic design task. Consider a small team developing an online booking application. The designer begins by creating a set of screens for searching, selecting and confirming reservations. Dedicated line and arrow tools can help illustrate navigation paths, while vector stroke conversion provides additional flexibility when refining custom icons. Font previews make it easier to narrow down suitable typography, and shared design tokens keep colours and spacing consistent between screens. Once the initial interface is prepared, colleagues can review the design through comments, while developers inspect the relevant properties and prepare the corresponding application components.
Several limitations still deserve attention. Outline Stroke requires WebGL rendering, and converting a stroke into geometry changes how the resulting element must be edited. Designers should therefore retain an original version when they may need to adjust stroke width or other stroke-specific properties later. Similarly, reusable components and tokens are only effective when a team establishes sensible naming conventions and maintains its libraries. Penpot does not automatically resolve conflicting visual decisions or guarantee that every design translates perfectly into working code. Teams moving from another editor should also test imports, fonts, prototypes and complex components before transferring an important project. Compatibility with a file format does not necessarily mean every detail will behave identically after migration.
For existing Penpot users, version 2.18 offers worthwhile improvements to familiar tasks, particularly vector editing, typography selection and the preservation of design-system relationships. New users may find its combination of free access, open-source code, collaborative editing and developer-friendly features attractive, especially when software ownership and flexibility matter. Larger businesses can also consider Enterprise if centralised identity management and organisation-wide permissions are necessary. The September 2026 release is best understood as an incremental but meaningful improvement, not a complete reinvention of the editor. Its value lies in removing small obstacles from everyday work while giving teams more dependable ways to create, review and maintain interface designs as their projects grow.
