Published 19 July 2026 · Source dated 1 September 2025
Penpot now bundles native design tokens and shared component libraries into its open-source platform at no cost — a feature set that's often gated behind paid tiers elsewhere. Design tokens themselves are a well-established practice, just newly accessible without a licence fee.
Design tokens (the named values behind colour, spacing, type that keep a system consistent) have been standard practice in mature design systems for years — that part isn't new, which is why this is **established**, not a trend. What's notable is Penpot folding native token support and shared libraries into its free, open-source offering, alongside CSS/SVG/HTML export.
For a junior building portfolio pieces, this matters because you can now practise proper token-based system thinking without needing an Enterprise seat anywhere. It's also a genuinely useful thing to show in an interview: 'I built this component using tokens, here's why' is a stronger answer than 'I made it look nice.'
Coach
rebuild one component (a button, a card) using tokens in Penpot this week, and be ready to explain in one sentence why tokens beat hardcoded values.
Design tokens are still the backbone of Material Design
Google's Material Design continues to push token-based theming as the default way to build flexible, on-brand components — it's the clearest real-world example of tokens done at scale. For juniors, understanding tokens beats memorising any one system's components.
material.io ·
Established
Material 3 Expressive: systems that flex, not just scale
Google's Material 3 Expressive update layers more personality — motion, colour, shape — onto Material's existing token structure without a rebuild. It's a solid case study in how mature design systems evolve.
The Penpot-vs-Figma debate is really about who controls your design system's tokens and infrastructure. Self-hosting is now a real option, not just a theory.