Every other design tool gives you an approximation of the web. Penpot gives you the web. That's not a marketing line. It's the actual architectural decision that separates it from Figma, Sketch, and everything else in the space: Penpot's canvas is built on SVG, its layout engine uses real CSS Flexbox and Grid, and when you open the Code Inspect panel, what you see is actual HTML and CSS that a browser would render, not a translation of some proprietary format.
Kaleidos, the Spanish open-source company behind it, has been building Penpot since 2019 under an MPL 2.0 license. That means you can read the source code, contribute to it, or self-host it on your own infrastructure using Docker or Kubernetes. The files are stored as SVG and JSON, formats you own. There's no vendor lock-in because there's no vendor to lock you in.
Penpot 2.0 was a significant release. CSS Grid landed as a first-class layout option, which means you can design grid-based layouts that actually correspond to what a developer would implement. Native design tokens arrived at the same time, making Penpot the first general-purpose design tool to bake tokens into the product rather than treating them as a plugin concern. The component system was redesigned, and the UI itself got a substantial refresh. The version that exists now is materially different from the Penpot many designers wrote off in 2022.
The Code Inspect view is where the design-to-development story plays out most clearly. Select a component, open the panel, and you get the CSS that actually renders it in a browser. Not approximately. Not a suggestion. The actual rules. For developer-centric teams, or designers who write code themselves, this removes an entire category of interpretation error from the handoff process.
The self-hosting option deserves more attention than it usually gets. GDPR compliance, IP ownership, regulated industries, and teams with strict data residency requirements all have legitimate reasons to want their design files on their own servers. Penpot is essentially the only production-ready general-purpose design tool that makes this feasible without enterprise sales calls.
The honest assessment is that Penpot is not yet Figma in terms of polish or ecosystem. The plugin library is smaller. Some interface panels feel more utilitarian than considered. Real-time collaboration works well but has occasionally shown performance issues on very large files. The community is active and the pace of development has accelerated, but it's still a tool that rewards patience.
Who it's for: teams that care about IP ownership and data sovereignty. Engineers who work closely with design and want handoff specs they can trust. Organizations in regulated industries that can't use cloud-hosted design tools. Open-source believers who want their toolchain to match their values. And, increasingly, teams who have simply gotten tired of Figma's pricing trajectory.
Who it's not for: teams that live in the Figma plugin ecosystem or depend on Figma-specific features. Solo designers who want a polished, zero-setup experience. Teams where speed of getting to a shareable prototype matters more than handoff accuracy.
The cloud version is free. Paid tiers add preferred hosting region, priority support, and enterprise controls. Self-hosting is free and fully featured. The open API and MCP server mean Penpot is already starting to show up in AI-assisted design workflows.
The thing worth watching is what happens as more design work moves closer to code. Penpot is the only design tool whose underlying model is already aligned with how browsers render things. That alignment may matter more as the line between design and development continues to compress.
Latest Updates
Say hello to background blur
Have you ever heard what "glassmorphism" is? Maybe not, but I'm sure you've seen an increase in glass effects in UI design across websites, apps, and operating systems.
Penpot ships background blur, after rebuilding its renderer to make it possible
Glassmorphism has been requested for years, but Penpot's old SVG pipeline couldn't render it. Getting there meant swapping in a new WebGL renderer built on Rust, WebAssembly, and Skia — real engine work, not a checklist feature, and a sign Penpot is closing the rendering gap with Figma rather than just matching its feature list.
5 best Sketch alternatives for design teams in 2026
Looking for a Sketch alternative? Compare Penpot, Figma, Lunacy, Framer, and Paper on AI integration and self-hosting to find the best fit for your team.
Background grids vs grid layouts: what’s the difference?
Background grids are guides you use to help you manually position design elements by eye. Grid layouts automate layouts (often responsively) based on the design rules you provide.
5 best Paper alternatives for UI and UX design in 2026
Considering Paper for UI/UX design? See how it compares to five alternatives, including Penpot, Figma, and Framer, before committing to an open alpha tool.
Every other design tool gives you an approximation of the web. Penpot gives you the web. That's not a marketing line. It's the actual architectural decision that separates it from Figma, Sketch, and everything else in the space: Penpot's canvas is built on SVG, its layout engine uses real CSS Flexbox and Grid, and when you open the Code Inspect panel, what you see is actual HTML and CSS that a browser would render, not a translation of some proprietary format.
Kaleidos, the Spanish open-source company behind it, has been building Penpot since 2019 under an MPL 2.0 license. That means you can read the source code, contribute to it, or self-host it on your own infrastructure using Docker or Kubernetes. The files are stored as SVG and JSON, formats you own. There's no vendor lock-in because there's no vendor to lock you in.
Penpot 2.0 was a significant release. CSS Grid landed as a first-class layout option, which means you can design grid-based layouts that actually correspond to what a developer would implement. Native design tokens arrived at the same time, making Penpot the first general-purpose design tool to bake tokens into the product rather than treating them as a plugin concern. The component system was redesigned, and the UI itself got a substantial refresh. The version that exists now is materially different from the Penpot many designers wrote off in 2022.
The Code Inspect view is where the design-to-development story plays out most clearly. Select a component, open the panel, and you get the CSS that actually renders it in a browser. Not approximately. Not a suggestion. The actual rules. For developer-centric teams, or designers who write code themselves, this removes an entire category of interpretation error from the handoff process.
The self-hosting option deserves more attention than it usually gets. GDPR compliance, IP ownership, regulated industries, and teams with strict data residency requirements all have legitimate reasons to want their design files on their own servers. Penpot is essentially the only production-ready general-purpose design tool that makes this feasible without enterprise sales calls.
The honest assessment is that Penpot is not yet Figma in terms of polish or ecosystem. The plugin library is smaller. Some interface panels feel more utilitarian than considered. Real-time collaboration works well but has occasionally shown performance issues on very large files. The community is active and the pace of development has accelerated, but it's still a tool that rewards patience.
Who it's for: teams that care about IP ownership and data sovereignty. Engineers who work closely with design and want handoff specs they can trust. Organizations in regulated industries that can't use cloud-hosted design tools. Open-source believers who want their toolchain to match their values. And, increasingly, teams who have simply gotten tired of Figma's pricing trajectory.
Who it's not for: teams that live in the Figma plugin ecosystem or depend on Figma-specific features. Solo designers who want a polished, zero-setup experience. Teams where speed of getting to a shareable prototype matters more than handoff accuracy.
The cloud version is free. Paid tiers add preferred hosting region, priority support, and enterprise controls. Self-hosting is free and fully featured. The open API and MCP server mean Penpot is already starting to show up in AI-assisted design workflows.
The thing worth watching is what happens as more design work moves closer to code. Penpot is the only design tool whose underlying model is already aligned with how browsers render things. That alignment may matter more as the line between design and development continues to compress.
Latest Updates
Say hello to background blur
Have you ever heard what "glassmorphism" is? Maybe not, but I'm sure you've seen an increase in glass effects in UI design across websites, apps, and operating systems.
Penpot ships background blur, after rebuilding its renderer to make it possible
Glassmorphism has been requested for years, but Penpot's old SVG pipeline couldn't render it. Getting there meant swapping in a new WebGL renderer built on Rust, WebAssembly, and Skia — real engine work, not a checklist feature, and a sign Penpot is closing the rendering gap with Figma rather than just matching its feature list.
5 best Sketch alternatives for design teams in 2026
Looking for a Sketch alternative? Compare Penpot, Figma, Lunacy, Framer, and Paper on AI integration and self-hosting to find the best fit for your team.
Background grids vs grid layouts: what’s the difference?
Background grids are guides you use to help you manually position design elements by eye. Grid layouts automate layouts (often responsively) based on the design rules you provide.
5 best Paper alternatives for UI and UX design in 2026
Considering Paper for UI/UX design? See how it compares to five alternatives, including Penpot, Figma, and Framer, before committing to an open alpha tool.