Skip to main content
Participant
September 17, 2026

Adobe Express blocks both the Adobe Fonts version and the static version of BioRhyme ExtraBold

  • September 17, 2026
  • 2 replies
  • 12 views

I am creating reusable branded templates in Adobe Express and need BioRhyme ExtraBold as part of my brand typography.

Adobe Fonts supplies BioRhyme as a variable font, which Adobe Express currently does not support. Adobe's documented workaround is to use a conventional/static version of the font.

I have the legitimate static TTF version of BioRhyme ExtraBold, but when I try to upload it to Adobe Express, Express rejects it with the message: “Font cannot be uploaded because it already exists in the Adobe Fonts library.”

This creates a dead end:

  • Adobe Express cannot use the Adobe Fonts variable version.
  • Adobe Express recommends using the static version.
  • Adobe Express then prevents me from uploading that static version.

This is a significant workflow problem because I use Adobe Express specifically to create reusable templates and streamline repeated content production. Creating the typography separately in Illustrator defeats the purpose of using Express templates.

Could Adobe please either:

  1. add variable-font support to Adobe Express;
  2. expose the static BioRhyme weights in Express; or
  3. allow users to upload a static font weight when the Adobe Fonts version of that family is incompatible with Express?

Please escalate this to the Adobe Express product/engineering team.

    2 replies

    paulbothaAuthor
    Participant
    September 17, 2026

    Hi Rose,

    Thanks for getting back to me. I was able to use AI to change the file name and meta data of the app, while keeping the original copyright in tack. The upload worked and I was able to use the font, although under a different name. If this is a problem, please let me know and I will remove the newly added and named font. This would not be ideal as you do not have a workable solution for this issue. AI also suggested that, based on your documentation, that this would not be an issue and would not have helped me do this had it been.

    Many thanks,
    Paul

    Rose DV
    Community Manager
    Community Manager
    September 17, 2026

    Hi @paulbotha,

    This is a really well-documented report, thank you, and you've pinpointed a genuine catch-22: Express can't use the variable version, our own guidance says use a static one, and then the upload check blocks the static one because the family already exists in Adobe Fonts. That last part turns the documented workaround into a dead end.

    Splitting your three asks, since they route differently:

    • The upload block on the static version (your point 3): I reproduced this on my end with BioRhyme ExtraBold and got the same block, so it's confirmed, not something on your side. I'm raising it with the team, since it prevents the workaround our own docs recommend.

    • Variable font support and exposing the static weights directly (your points 1 and 2): these are feature requests, and there's already an entry our product team monitors, so upvoting it adds your weight: https://adobeexpress.uservoice.com/forums/951181-adobe-express/suggestions/46811443-variable-fonts

    Being honest with you: I don't have a clean in-Express workaround right now. I tried renaming the static file to get it past the upload check and it still blocked, so that route's out. Until the upload issue is fixed, the only options are building the type outside Express (which I know defeats the purpose of your template workflow) or waiting on the fix. I'd rather tell you that straight than send you chasing something that won't work.

    I'll come back here as soon as I have an update from the team.

    Rose