Skip to content
Back to Blog
Penpot vs. Figma for Data Visualization Framing
August 15, 2026 · 6 min read · Career DataViz Data Analysis Open Source

🛠 The Analyst’s Toolkit IV.

This post is also a small manifesto. I’ve become genuinely passionate about open source software lately, and Penpot is one of the most exciting examples of what open source can look like when it’s done right.

If you’ve followed this series, you know I’ve been building my design workflow around a small set of tools: Figma for wireframing and layout, Coolors for colour palette building, and Tableau Public for the actual visualizations. Today I want to introduce a tool that’s been sitting in the back of my mind for a while and talk honestly about why I haven’t fully switched to it yet, even though I really want to.


🏢 Who’s Behind Each Tool?

Before comparing features, it’s worth understanding who you’re actually depending on when you choose a tool.

Figma was founded by Dylan Field and is based in San Francisco. After a high-profile attempted acquisition fell through in 2024, Figma went public in 2025, making it one of the more anticipated tech IPOs of recent years. It’s now a publicly traded company, which brings its own set of pressures around growth, monetization, and shareholder expectations.

Penpot is built by Kaleidos, a Madrid-based startup founded in 2011 by Pablo Ruiz-Múzquiz and Enrique Posner. The platform is on a mission to bridge the gap between designers and developers, and today over 80,000 teams run on Penpot including Mozilla, Accenture, IBM, Google, and Microsoft. It’s not a scrappy side project. It’s a serious, growing platform with a clear philosophical mission: design tooling should be open, free, and owned by nobody.

The ownership question matters more than it might seem. Because Penpot is open source, it cannot be discontinued or paywalled retroactively. That’s a guarantee Figma — now accountable to public market shareholders — simply cannot offer.


✅ What Figma Does Well

Let’s be honest. Figma is the industry standard for good reason.

It’s fast, polished, and the collaboration experience is genuinely excellent. Real-time multiuser editing, comments, design tokens, a mature component system, and a plugin ecosystem with a solution for almost every niche need. Every designer you hire already knows it, every plugin you might want already exists, and every design system reference you find online ships as a Figma library.

For analysts using Figma to frame dashboards — sketching layouts, defining colour systems, wireframing before building in Tableau: it’s a smooth, friction-free experience. The auto-layout system is powerful, and once you’ve internalized how it works, it’s genuinely fast to use.

The tradeoff? As a publicly traded company, Figma is now under pressure to grow revenue. Price hikes, feature paywalling, and shifting priorities are real risks for any tool that’s gone from an independent startup to a listed company.

🌱 What Penpot Does Well

Penpot is no longer just an open source alternative. With the release of Penpot 2.0, it has become a mature tool that offers features Figma still doesn’t have like true CSS Grid. For analysts, that might sound like a developer concern, but it matters for layout precision.

A few things Penpot genuinely gets right:


⚠️ Where Penpot Still Has Ground to Cover

I want to be fair here because I genuinely root for Penpot but honesty matters more than cheerleading.

There’s no equivalent to Figma’s auto-layout, which is a significant limitation for responsive design work. Colour management is functional but basic, and there’s no equivalent to Figma’s robust variable system for managing design tokens at scale.

Figma’s maturity still provides undeniable polish, scale, and enterprise stability. The synchronous editing and performance on massive design systems generally remain a high bar. Performance can also be an issue in Penpot because files can render slowly, and some users report placeholder images appearing when zooming on the canvas. These are the kinds of friction points that slow you down when you’re trying to work quickly.


🏁 My Honest Conclusion

I love what Penpot stands for. Open source, community-driven, free from corporate ownership. These are values I genuinely believe in, and I want to support tools that embody them.

But I’ll be honest: I can’t make the full switch yet. I’ve spent years building muscle memory in Figma. I know where everything is. I know how auto-layout behaves. I know how to move fast. Switching to Penpot right now would slow me down in ways that would affect my actual work and that’s a real cost, even when the reasons to switch are compelling.

So where does that leave me? Penpot is already in my toolkit as a tool I experiment with and keep an eye on. Every release it gets closer. The gap is narrowing. And the moment the friction of switching feels smaller than the discomfort of staying on a platform driven by public market expectations, I’ll make the move.

For now: if you’re starting fresh with no Figma habits to unlearn, I’d genuinely recommend giving Penpot a serious look. The concept is right. The direction is right. And the open source community deserves your support.

Want to build something together?

If you need executive-ready dashboards built with this approach, let's talk.

Get in Touch →
Series · The Analyst's Toolkit

Enjoyed this story?

Share it with your network.

Copied!

The Analyst's Edge

Enjoyed this? Get the next one in your inbox.

One practical Tableau or DataViz technique per month.

No spam. Unsubscribe any time.

Comments

Comments are powered by Giscus via GitHub Discussions. A GitHub account is required to comment.

← Older On-Premise vs Cloud: What Nobody Tells You Before You Decide Newer → DBeaver: The SQL Client I've Used Since Day One