Guide9 min readUpdated
Penpot: A Guide to the Open Source Design Tool for Startups
Penpot is an open-source design tool you can use in a browser or self host. See who it suits, how handoff works and the trade-offs for a small team.
Suppose a startup in Indore has 4 people: a founder, a designer and 2 developers. The developers ask "what is the padding here" on WhatsApp many times a day. A client from a bank asks where the design files are stored. Someone on the team says: "Should we look at Penpot?"
Penpot is an open-source design platform for designing interfaces and design systems. Penpot can be used in a browser or installed on your own servers. Open source means the source code is public, and anyone may read the code and run the code under the terms of its licence.
A note on my own position. I do my client work in Figma. This guide is not a ranking of tools, and I am not claiming to have tested Penpot. I read Penpot's official website, repository and user guide. Here is what Penpot is, how its handoff works according to its documents, and where I think Penpot fits.
Checked in November 2026. Tools change quickly, so confirm details on the project's own page.
What is Penpot?
Penpot is a design tool for product interfaces whose code is public and which a team can run on its own machines. The repository describes Penpot as "the open-source design platform for teams that build digital products at scale". The repository states that the code is under the Mozilla Public License 2.0 and that Penpot is a project of a company named Kaleidos.
The official pages list these main parts:
- Open standards. The repository says Penpot works with open standards such as SVG, CSS, HTML and JSON.
- Components and variants. A component is a reusable piece, such as a button. A variant is a version of that piece, such as a disabled button.
- Design tokens. A design token is a named design value, such as a brand colour or a spacing size, that designers and developers both use.
- Layout that follows CSS. Penpot offers Flex Layout and CSS Grid Layout, which are the same layout methods that developers use on the web.
- Collaboration. The repository mentions real-time collaboration, and says a person can also work alone.
- Plugins and an API. A plugin system and an open API let developers extend the tool.
Who does Penpot suit?
Penpot suits a team that cares about open formats, about developers working inside the design file, or about control over where files are stored. This is my reading of the official material, not a claim from Penpot.
I would look at Penpot seriously in these situations:
- Developers sit close to design. The layout tools use the same ideas as CSS. A developer may find the file easier to read.
- A client or regulator asks where data lives. A self hosted design tool keeps the files on a server that the team controls.
- The team prefers open source software. Some teams choose open source tools as a principle, and some teams want to inspect or extend the code.
- The team wants design and code collaboration in one place. Tokens, components and inspect tools are built for that shared work.
I would think harder in one situation. If your clients, freelancers and partners already send files in another tool, a switch creates friction for those people. That friction is not a judgement on either tool. It is the practical side of working with others. When people search for "Figma alternative open source", this is usually the question behind the search: will the people I work with open my files easily?
How does handoff work in Penpot, according to its docs?
Handoff happens through an Inspect mode, a Code tab and a shareable link. Handoff is the step where a designer gives a developer everything needed to build a screen. According to the project's documentation, the pieces work as follows.
| What the developer needs | Where the Penpot user guide says to find it |
|---|---|
| Sizes, colours and text styles | The Info panel in Inspect mode, with copy buttons for each property |
| Distances between elements | Select a layer and hover over other layers |
| Code snippets | The Code tab, with markup in SVG and HTML and styles in CSS |
| CSS for selected layers | The right-click option "Copy as CSS" |
| Images and icons | The export option at the bottom of the Info panel |
| Access without editing rights | A share link from View mode |
Three details in the user guide matter for a small team.
First, the guide describes Inspect in the Workspace as a view-only mode, so that developers can work in the file without the fear of breaking things.
Second, View mode can create a share link. The guide describes the link as a public URL, so a person can see the prototype without a Penpot account. The person who creates the link chooses which pages are shared. The same person chooses whether outside viewers can comment and whether outside viewers can inspect code. A public link is convenient, and a public link is also a reason to be careful about what is on the shared pages.
Third, the guide says design tokens can be exported and imported as JSON files. The guide says Penpot follows the draft format of the W3C Design Tokens Community Group. For a developer, that means colours and spacing can arrive as a structured file, not as a list typed in a chat.
The tool does not change what a good handoff contains. Screens, states, tokens, assets and notes are needed in any tool. My developer handoff checklist is written for Figma, and the list of what to hand over applies here too.
What does self hosting mean for a small team?
Self hosting means your team runs Penpot on a server that your team controls, and your team then owns the upkeep. Penpot's technical guide lists several ways to install, including Docker and Kubernetes. Docker and Kubernetes are tools that developers use to package and run software on servers.
The technical guide says the experience stays the same in the cloud version and in a self-hosted copy. The guide also says the self-hosted images are published shortly after the cloud update.
The guide does not make the decision for you, so here is my view. Self hosting gives control, and control has a price in time:
- Someone must install the server and keep the server updated.
- Someone must take backups and test that a backup can be restored.
- Someone must manage who has access when people join and leave.
- Someone must be reachable when the server is down on a deadline day.
A team of 4 with no person for server work should start with the hosted version. Check the current plans on the official website. A team with a strict data requirement and a capable developer can consider self hosting.
How could a small team try Penpot this week?
Run one real handoff through Penpot, on one small flow, and decide from that experience. A full migration is the wrong first step.
- Choose one small flow, such as Login with phone number, OTP entry and Home.
- Rebuild those 3 screens in Penpot. Use Flex Layout for the form.
- Make the primary button a component with 2 variants: normal and disabled.
- Define a few tokens: 1 brand colour, 1 text colour, 1 error colour and 3 spacing sizes.
- Create a View mode link with code inspection allowed, and send the link to one developer.
- Ask the developer to build the screens from Inspect only, and to note every question.
- Count the questions. Compare the count with your usual handoff.
The number of questions is the honest measure. If the count falls, the tool is helping your team. If the count stays the same, the problem is in the file, not in the tool.
What are the honest trade-offs?
The trade-offs are switching cost, upkeep, the limits of generated code, and care with AI features. None of these makes Penpot a wrong choice. Each one deserves a clear answer before the team moves.
- Switching cost. Existing files, shared libraries and habits live in your current tool. Rebuilding a component library takes real days. Read Penpot's current documentation on importing files before you assume that old files will move across.
- Working with outsiders. Ask your regular freelancers and clients which tools they can open. My guide on how to work with a remote designer covers this conversation.
- Server upkeep. Self hosting adds the duties listed above.
- Code is a starting point. The CSS and HTML in the Code tab describe how a layer looks. I would not expect that code to include your app's logic, data or error handling. A developer still writes the product.
- AI features need review. The official website promotes an MCP server that connects AI agents to Penpot. MCP means Model Context Protocol, a way for AI assistants to connect to other software. Any such workflow carries the usual risks: the cost of running models, design files sent to an outside model, and output that looks correct but contains made-up details. A person must review what an agent changes.
What does a design tool not decide for you?
No design tool decides what your product should do, in what order, and for whom. Those decisions come before the first frame is drawn, and they are the same in every tool.
On a seller app I designed for a marketplace, the important work was the order of onboarding and verification steps. That work was thinking, talking and testing. The tool only recorded the result. The same is true of a design system: the tool stores tokens, and a person has to choose them. My guide to a design system for startups explains which choices to make first, and what files to ask your designer for lists what you should own at the end of a project.
Real users also remain outside the tool. A neat file with clean tokens can still describe a confusing flow. Only people trying the flow can show that.
If you want a second opinion on your design files or your handoff process, whatever tool your team uses, you can get in touch.
Sources
Frequently asked questions
Is Penpot really open source?
+
Yes. The Penpot repository on GitHub is public and states that the code is under the Mozilla Public License 2.0. Confirm the current licence terms in the repository before you build on the code.
Can developers get CSS from Penpot designs?
+
According to the Penpot user guide, the Code tab in Inspect mode shows markup in SVG and HTML and styles in CSS, and layers can be copied as CSS. Treat that code as a starting point that a developer still reviews.
Do viewers need an account to see a Penpot prototype?
+
The user guide says a View mode share link is a public URL, so a person can see the prototype without a Penpot account. The creator of the link chooses the pages, and whether outside viewers can comment or inspect code.
Should a small startup self host its design tool?
+
Only if someone on the team can install, update and back up a server. Without that person, a hosted version is the safer start, and the team can revisit self hosting later.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.