# Feature request: support variable fontWeight tokens

**URL:** <https://community.penpot.app/t/feature-request-support-variable-fontweight-tokens/10888>\
**Category:** Help us improve Penpot\
**Tags:** feature-request, design-tokens\
**Created:** [September 11, 2026, 7:34pm UTC](https://community.penpot.app/t/feature-request-support-variable-fontweight-tokens/10888 "2026-09-11T19:34:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![scottdotis](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/scottdotis/32/8400_2.png) [@scottdotis](https://community.penpot.app/u/scottdotis)\
**Post date:** [September 11, 2026, 7:34pm UTC](https://community.penpot.app/t/feature-request-support-variable-fontweight-tokens/10888/1 "2026-09-11T19:34:58Z")

</div>

When entering numbers for font weight tokens, it’s currently only possible to enter a number that’s already aliased to a named weight (e.g. 400/normal/regular). Trying to enter a number other than an already-aliased one causes a validation error. E.g. 333 is invalid, but 300 is not.

The DTCG Format Module spec allows any number in the [1, 1000] range as a valid value for a token of type fontWeight.

A key practical benefit of fontWeight tokens is to alias ‘magic’ numbers of a variable weight axis to more memorable aliases, e.g. `font.weight.default: 420` `font.weight.thicc: 744`. Given that the standard 100–step values (up too 900) are _already_ well-aliased in most tools and languages, it almost feels pointless to set weight tokens in Penpot.

This is still by far the best, most complete token feature in a design tool right now (as you can tell from the niche request) and I’d love to see it be just a little better aligned to the DTCG format module!

---

<div class="post-metadata">

**Author:** ![LauraKalbag](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/laurakalbag/32/5014_2.png) [@LauraKalbag](https://community.penpot.app/u/LauraKalbag)\
**Post date:** [September 15, 2026, 10:02am UTC](https://community.penpot.app/t/feature-request-support-variable-fontweight-tokens/10888/2 "2026-09-15T10:02:03Z")

</div>

I don’t think this is a niche request for typography lovers!

We’d need variable font support first. ([User story here](https://tree.taiga.io/project/penpot/us/3686) if anyone wants to add their use cases! It’s on the [roadmap](https://community.penpot.app/t/not-a-roadmap-but-whats-coming-in-penpot-june-2026/10628)!) Right now, you can use variable fonts from Google fonts or upload variable fonts, but only use them at the predefined weights and styles.

> [@scottdotis](#):
>
> A key practical benefit of fontWeight tokens is to alias ‘magic’ numbers of a variable weight axis to more memorable aliases, e.g. `font.weight.default: 420` `font.weight.thicc: 744`. Given that the standard 100–step values (up too 900) are _already_ well-aliased in most tools and languages, it almost feels pointless to set weight tokens in Penpot.

Such a great point.