Learn / Guide
Rainmeter Fonts Not Working: Family Names, Files and Clipping
Check Rainmeter FontFace family names, root @Resources font placement, supported weights and clipping before reinstalling fonts or changing a skin.
If a Rainmeter font is not working, check the String meter's FontFace against the font's actual family name, then confirm that the font is either installed in Windows or supplied as a .ttf/.otf file in the skin's root @Resources\Fonts folder. A font filename is not necessarily its family name.
Scope: these are official-documentation checks, not a test of your font files. They do not establish that a downloaded font includes every symbol or that you have permission to redistribute it.
1. Identify whether this is the wrong font, missing text or clipping
| Symptom | Inspect first |
|---|---|
| Text appears in a different face | FontFace family name and font availability |
| Only icons or certain characters are wrong | Whether the intended font contains those characters |
| Text ends with dots or is cut off | ClipString, W/H and fixed skin dimensions |
| No text at all | Measure output, Hidden state, FontColor and loaded configuration |
Do not reinstall fonts just because a track title or weather label is empty. A String meter may be correctly configured but bound to a measure returning an empty string. About → Skins shows the underlying measure values so you can separate missing data from text rendering.
2. Read the actual font family name
- Locate the font file supplied by the creator, if one exists. Keep the skin's original folder structure intact.
- Double-click a trusted
.ttfor.otffile to open Windows font preview and read its Font Name. - In Manage, select the affected configuration and choose Edit. Find the String meter or shared style that supplies FontFace.
- Use the appropriate family name, save the correct file and refresh that skin. Keep a backup of the original value.
For example, a file named ExampleSans-Regular.ttf might have a family called Example Sans. Do not assume that dropping the file extension always produces the correct FontFace. FontWeight selects a supported weight within a family; renaming files is not a substitute for using its metadata.
3. Check the bundled font location
The documented structure is Skins\SuiteName\@Resources\Fonts\FontFile.ttf. The @Resources folder belongs directly inside the suite's root configuration, even when the visible clock is several subfolders deeper. Placing Fonts beside a nested clock file can put it outside the shared resources location.
Rainmeter automatically loads TrueType and OpenType fonts from that folder for use with FontFace. You do not need to install a font system-wide solely to use it in that skin. Conversely, a font already installed in Windows can be referenced without a bundled copy. Old LocalFont instructions are deprecated in favor of @Resources\Fonts.
If an archive was extracted with an extra wrapper folder, correct the overall structure using the skin installation guide. Avoid scattering font files and includes into separate guessed locations.
4. Check styles, weights and clipping separately
A shared MeterStyle, include file or author variable may control the final font. Changing a value in an inactive variant will not affect the visible skin. Follow the active configuration's settings before concluding Rainmeter ignored your edit.
For a heavier face, inspect FontWeight. If the family does not support the requested weight, Rainmeter uses the closest available weight; some families use simulated bold behavior. That is different from failure to load the family.
If the new font is wider, check ClipString, meter W/H and any fixed SkinWidth/SkinHeight. A correctly loaded face can still be truncated. The resizing guide explains why FontSize, pixel dimensions and visual scale are separate controls.
Failure boundaries and a useful support report
If only special symbols fail, confirm the creator intended an icon font and that you have the specified file. A valid font cannot display a glyph it does not contain. Replacing it with a normal text font may remove the icons rather than repair them.
For support, provide the active configuration, relevant FontFace/FontWeight lines, resource folder structure and font family name. Do not upload commercial font files or assume that a personal-use license allows sharing. Use file backups to reverse edits; a saved layout alone does not restore changed font settings in skin files.