Record the affected characters and surface
Keep the item, selected subtitle track, language, client and server versions, plus a short example of the missing characters. Note whether the same script is readable in the surrounding interface and in another legitimate track. A box appearing for one writing system is different evidence from all subtitle text being absent.
For an illustrative comparison, Latin text appears correctly while Japanese characters become squares in a particular subtitle. Increasing the subtitle size can make the squares larger without supplying the missing glyphs. Preserve the language requirement rather than replacing it with an unreadable alternative just to remove the symptom.
Match the font location to the renderer
Jellyfin’s configuration guide says server system fonts are used for burned-in subtitles and rendered cover images. It separately identifies client system fonts for the interface and subtitle rendering in some clients. A font installed on a laptop is therefore not evidence that the server or television renderer can use it.
Ask the authorised operator to confirm the actual playback and rendering path for the failing track. If the server has already drawn text into video pixels, changing only the receiving client’s interface font does not supply the missing glyphs at the earlier drawing stage. Keep that reasoning tied to the observed mode.
Treat web ASS fallback as a specific case
The official guide also describes server-configured fallback fonts loaded by the web client for ASS subtitles when other available fonts cannot render the required characters. It documents a total size limit and preloading behaviour. This is a specific font-delivery mechanism, not a statement that every client shares the same font collection.
Choose a suitable licensed font with the required script coverage and follow the documentation for the actual deployment. Avoid an oversized collection installed indiscriminately across devices. A clear operator request names the script, renderer and intended font source so the change can be reviewed without guessing from a photograph alone.
Verify the same passage with the needed text
After the relevant supported change, compare the same subtitle passage, selected language and client. Check that the previously missing characters are readable and the viewer still receives the necessary information. Correct glyph display and synchronised timing are separate outcomes; fixing one does not establish the other.
Retain the before-and-after renderer context in a private support record, redacting paths and personal media names. This workflow combines Jellyfin’s documented font locations with a hypothetical language example. It does not install fonts, test a server or guarantee that a different subtitle format or client uses the same rendering path.
Questions about this guide
Will installing a font on the viewing laptop always fix burned-in subtitles?
No. Jellyfin documents server system fonts for the burn-in stage.
Do web ASS fallback fonts apply identically to every client?
No. The documented fallback mechanism specifically concerns web-client ASS rendering.