This page lists common problems and their usual causes.
A feature applies but nothing changes
Usually, the font does not contain that feature. Check with the Glyphs Panel. It reads the font file and lists the features that the font contains.
If the font has the feature, check whether it changes your letters. A swash feature that changes only H, C, and T shows no change in a word without those letters.
Also make sure that a font is selected. If no font is selected, the features apply to the theme font.
Fonts do not appear in the editor picker
- Make sure that the upload completed on the Custom Fonts tab.
- For Adobe Fonts, make sure that you typed the family names and that the families are in your Adobe project.
- Click Clear Font Cache on the Options tab. The editor font list is cached for one hour.
- Reload the editor after you clear the cache.
- A font that you install in the WordPress Font Library shows the next time you open the editor.
Fonts work in the editor but not on the frontend
The usual cause is the detection cache. Click Clear Font Cache on the Options tab, and reload the page.
If the problem continues on an archive page, read about archive pages in Performance and font loading.
For a font in the WordPress Font Library, check whether it is activated in global styles, not only installed. WordPress prints no @font-face for a font that is installed but not activated. In that case, the plugin prints its own. If the font still does not load, the cause is something else.
For a font that only your theme CSS uses, select Load on all pages on its card.
Uploading a font kit fails
- Make sure that the ZIP contains font files, not a folder of installers.
- Compare the file size with the upload size limit of your server.
- Make sure that
wp-content/uploads/is writable.
Styled text lost its font after I changed fonts
When you add a font again, it gets a new numeric ID. The plugin never uses an old ID again. Content that uses the old ID, for example var(--font-5), then shows a fallback font.
To fix this, go to Replacement Fonts and map the old ID to the new font. To prevent this problem, choose a replacement font in the delete dialog when you delete a font.
The block says its content is invalid
The saved markup does not match what the block expects. This usually occurs after someone edits the HTML by hand. Click Attempt recovery in the block’s warning. Recovery keeps your content and rebuilds the markup.
Enter does not do what I expect
In a Typography Stylist block, Enter adds a line break by default. It does not start a new block. To make Enter start a new block, clear Enter adds a line break inside the block at Settings → Typography Stylist → Options.
Shift+Enter always adds a line break, whichever way that setting is set.
If Backspace at the start of a paragraph joins it to the heading with no space, add a line break with Shift+Enter.
A toolbar button is missing
The Glyphs and Paragraph Styles toolbar buttons are on by default. If a button is missing, examine its setting in Options: a button that you turned off stays off. The Paragraph Styles button shows in Typography Stylist blocks, and next to the Typography Stylist Features button (the swash T) in other blocks. The Glyphs… button in the typography panel is always available.
A font preview on the Custom Fonts tab shows a fallback font
Fonts load when their card comes into view. Scroll to the card and wait.
An Adobe font preview is blank in the editor
The editor loads an Adobe Fonts kit only when the post uses it, or when you pick or preview its font. Wait for the kit to load. If the preview stays blank, make sure that your domain is authorized in your Adobe Fonts project settings.
A screen reader reads fragments of words
The accessibility model prevents this. Convert the block to a Typography Stylist block. It keeps a plain heading next to the styled version.
Still stuck?
Write down the font, the feature, and where the problem occurs: the editor, the frontend, or both. These three facts usually show the cause.