Custom Fonts
If your design team licensed a typeface, or your website already serves one, you can upload it to Paminga and use it everywhere your prospects see you: Landing Pages, Forms, CTAs, and Emails.
You upload once, in Account Settings. From then on your typeface appears in the font pickers throughout the builders, right alongside the Google and web-safe options. No CSS, no hosting, no cache-busting on your end.
Families and Variants
Paminga models fonts the way the web does: a family containing one or more variants.
The family is the name your team already uses. The variants are the individual font files that make up that family, one per weight and style combination.
So a family named Acme Grotesk might contain four variants:
| Weight | Style | File |
|---|---|---|
| 400 | Normal | AcmeGrotesk-Regular.woff2 |
| 400 | Italic | AcmeGrotesk-Italic.woff2 |
| 700 | Normal | AcmeGrotesk-Bold.woff2 |
| 700 | Italic | AcmeGrotesk-BoldItalic.woff2 |
Weights run from 100 to 900 in steps of 100, following the standard CSS numeric scale:
| Weight | Common name |
|---|---|
| 100 | Thin |
| 200 | Extra Light |
| 300 | Light |
| 400 | Regular / Normal |
| 500 | Medium |
| 600 | Semi Bold |
| 700 | Bold |
| 800 | Extra Bold |
| 900 | Black |
Each weight and style combination can appear only once per family. If you try to add a second 400 Normal, Paminga tells you the combination is already taken.
If you upload only 400 Normal and then set text to bold, the browser fakes the bold by smearing the regular face. Same with italic; it just slants the upright letters. The result is passable, but it isn't your typeface. Upload a real file for every weight and style your designs call for.
Supported File Formats
Paminga accepts four formats:
| Format | Extension | Notes |
|---|---|---|
| WOFF2 | .woff2 | Best choice. Smallest files, supported by every modern browser. |
| WOFF | .woff | Larger than WOFF2. Useful only for very old browser support. |
| TrueType | .ttf | Uncompressed. Works, but the files are big. |
| OpenType | .otf | Uncompressed. Works, but the files are big. |
Each file may be up to 5 MB.
Reach for WOFF2 when your foundry offers it. A WOFF2 file is typically a third the size of the equivalent TTF, and every byte counts on a landing page you're paying to send traffic to.
Paminga checks the actual contents of the file, not just its name. Renaming logo.png to logo.woff2 won't get it through. The upload is rejected with a message telling you the contents don't match the extension.
Creating a Font Family
- Go to Settings → Account → Custom Fonts.
- Click Create Font Family.
- Give the family a name. This is the name that shows up in every font picker in the builders, so use the name your team recognizes.
- Set the Weight and Style for the first variant.
- Click the upload icon and choose the font file for that variant.
- Click Add a new Variant for each additional weight and style, and repeat.
- Click Create.
A family needs at least one variant. Paminga won't let you save an empty one.
As soon as you pick a file, the sample text above that row renders in it. That preview runs entirely in your browser before anything is uploaded, so you can confirm you grabbed the right file out of a folder full of near-identically-named ones.
Naming Your Family
The family name is what the builders write into the underlying CSS, so pick it deliberately.
If your family name matches a Google font name exactly, yours wins, because the font pickers dedupe by name and give your uploaded family precedence. That's handy when you've licensed a full version of a typeface that Google only offers a subset of. It's less handy when you didn't intend the collision, so give your family a distinct name unless you're overriding on purpose.
Editing a Font Family
Open the Actions menu on any row and choose Edit Font Family. From the drawer you can:
- Rename the family. Existing assets that reference the old name will no longer resolve to it, so treat renaming as a change you follow up on.
- Change a variant's weight or style. Useful when you realize the file you labeled 600 is really the 500.
- Replace a variant's file. Click the upload icon on an existing row and choose a new file. The old file is replaced when you save.
- Remove a variant. Click the delete icon on the row. The variant isn't actually deleted until you click Update, so you can back out by closing the drawer instead.
Changes take effect on your published Landing Pages, Forms, and CTAs shortly after you save. Paminga clears the relevant render caches for you.
Deleting a Font Family
Choose Delete Font Family from the Actions menu. This permanently removes the family and every variant file under it.
Any asset still styled with that family falls back to a generic system font. Check your published Landing Pages, Forms, and CTAs before you delete a family that's been in circulation.
Using Your Fonts in the Builders
Once a family exists, it's available in the font pickers in the builders. Select it the same way you'd select a Google font.
Custom families are merged into the same alphabetized list as the Google and web-safe fonts, so there's no separate "custom" section to hunt for. Search by your family name.
You can also set a custom font as part of a Brand Kit so new assets inherit it automatically instead of relying on everyone to pick it by hand.
Selecting the font works the same everywhere. How reliably it renders depends on the medium.
Landing Pages, Forms, and CTAs
These are hosted web assets, so Paminga serves the font file to the visitor's browser along with the page. Your typeface renders exactly as you designed it.
Emails
You can select a custom family in the Email Builder the same way, and your choice is saved and sent with the email.
Whether the recipient actually sees it is up to their email client, and email clients have never agreed on this. Several of the biggest, including Outlook on Windows and the Gmail apps, won't load a web font at all. They fall back instead.
This isn't specific to custom fonts. It's how every non-web-safe font behaves in email, Google fonts included, which is why the Email Builder has a Fallback Font setting under Styles in the first place.
The Fallback Font list is limited to web-safe fonts on purpose, because those are the ones you can count on. Pick the closest web-safe match to your brand typeface and treat that as the design most recipients will see. Rendering your actual typeface is a bonus from the clients that support it, not the baseline.
Keep in mind that the Email Builder canvas is a browser, so it will happily show you your custom font while you work. That preview is showing you the best case, not the common one.
Licensing
Paminga hosts and serves the font files you upload, which makes them publicly reachable to anyone who loads your pages. That's how web fonts work, but it's worth confirming your license permits webfont use and self-hosting before you upload. Desktop-only licenses generally don't.
Check with whoever purchased the license. Foundries differ, and a few meter usage by pageview.
