Bug: import custom font only works if it is woff

The app says that it accepts ttf, otf and woff, but when I tried to upload ttf and otf nothing happened. No error message. It only worked with woff.

Tried on both desktop app and web, even after restarting a few times I couldn’t get it to work.

But woff format works perfectly. The test was made with Satoshi font, from fontshare.com. Didn’t tested it with other fonts.

Hi, thanks for reporting! It does work if you import the TTF within the web folder of that font asset. However, you should have gotten an error message. I created this issue on GitHub, if you want to track it No feedback when uploading custom font fails · Issue #12304 · penpot/penpot · GitHub

2 Likes

Hi @Milton_Jose you should expect the bug to be fixed in the next release. Note that then you will get an error message (instead of no UI feedback), since the issue is that the font asset you are using is malformed and missing metadata (like the font family name). As a workaround, the font assets in the web folder of that font download should work OK.

2 Likes

If you want to keep using the desktop OTF or TTF files, you can usually repair the missing metadata yourself before importing. Open the font in FontForge, check that the Family Name and the name table entries are filled in under Element > Font Info, then generate a fresh OTF and import that. It’s also worth checking the font’s license first, since some free foundry licenses allow converting formats and some don’t. In the meantime the WOFF files from the web folder are the same design, so nothing is lost by using those for now.

2 Likes