Open a font file in your browser, type any custom text, and you can view every glyph the browser can render — without installing the font or uploading the file anywhere. A font glyph is the actual drawing inside a font that represents a character, and a single font file may ship with hundreds or thousands of them for different scripts, weights, and stylistic alternates. Using the Font Previewer, you pick a local TTF, OTF, WOFF, or WOFF2 file up to 10 MiB, type the words or characters you care about, choose a size between 8 and 200 pixels, and see exactly how those glyphs look in your current browser. Missing glyphs render as boxes or fallback characters, which makes coverage gaps instantly visible. The font bytes never leave the page: the browser reads them through its FontFace API, applies them as a temporary face to the document font set, and removes them when the tab closes or you choose a new file.
What "Viewing Glyphs" Actually Means
A character (or code point) is a number assigned by the Unicode standard. A glyph is the picture the font draws for that number. One character can map to many glyphs — an accented "a" might ship in three stylistic variants — and one font can carry tens of thousands of glyphs that never appear in plain ASCII. When designers say they want to view the glyphs in a font, they usually mean three things at once: confirming the shapes are well drawn, checking that the characters they plan to use actually exist in the file, and looking for stylistic alternates such as swashes, small caps, or old-style numerals.
Operating-system font viewers and design-suite glyph panels have done this job for years, but they require installation or a heavyweight editor. A local browser preview covers the same ground for the cases that matter most before you commit to a license or a redesign. That makes a no-install path useful for evaluating demo files from font foundries, font sample packs you downloaded long ago, or files a colleague sent for review.
View Font Glyphs With Font Previewer
- Open Font Previewer in a current browser tab. The tool runs entirely in the page; no extension, account, or server upload is required.
- Choose a trusted TTF, OTF, WOFF, or WOFF2 file from your computer. The selected file must be non-empty and no larger than 10 MiB, which keeps parsing time and browser memory bounded.
- Type the exact sample text you want to inspect into the preview field — a pangram, a brand name, a string of numerals, or a row of accented letters. Plain Unicode text is accepted.
- Choose a whole-pixel font size between 8 and 200. Small sizes reveal hinting and legibility issues at body-text sizes; large sizes reveal the outlines, curves, and spacing decisions of the design.
- Inspect the rendered glyphs in the preview area. Note any character that appears as a hollow rectangle (a "tofu"), a question mark, or a fallback shape from the operating system — these are the missing-glyph signals.
- Choose another font file to replace the current face. The previous face is removed from the document font set before the new one is loaded, so only one font is active at a time.
Closing or refreshing the tab removes the temporary font from the page entirely. The file is not copied into a system Fonts folder, application preferences stay untouched, and no CSS package is generated.
What the Preview Tells You About Glyph Coverage
Once a font is loaded, the preview reflects whatever glyphs the browser can resolve from the file at the size you chose. A clean rendering of every character you typed means the font contains glyphs for those code points and the browser engine decoded them successfully. A box, a question mark, or a clearly mismatched fallback letter means the font is missing that glyph — or, less often, that the file itself is damaged. The label shown above the preview is the filename, not an authoritative internal family or style record; a file called Demo Bold can carry different metadata inside.
Because the preview is purely visual, it is best used as a coverage sampler. The table below lists the most useful inspection strings and what each one typically reveals about the file.
| Text to type | What it checks |
|---|---|
| The quick brown fox jumps over the lazy dog | Full lowercase and uppercase Latin coverage, basic punctuation |
| 0123456789 $£€¥ | Tabular or proportional numerals, currency glyphs |
| áéíóúñçßøå | Accented Latin characters used by Western European languages |
| —–""''… | Em dash, en dash, smart quotes, ellipsis |
| АаБбВвЯя | Cyrillic script coverage if the font claims to support it |
| 日本語 中文 한국어 | Han, Hiragana, Katakana, and Hangul coverage |
If a row renders cleanly, you have direct evidence of coverage for those code points in this file. If a row contains fallback shapes, the file either lacks those glyphs or contains them in a way the browser could not decode. The tool itself does not synthesize missing glyphs, prove full language support, or enumerate the character map; you are reading the visual outcome of the browser's own font engine.
What the Preview Cannot Tell You
A browser preview is a quick look, not a certification. The table below separates the claims Font Previewer can support from the claims it cannot, so you do not over-trust the result.
| Preview can confirm | Preview cannot confirm |
|---|---|
| The browser engine decodes the file without error | The font is licensed for your intended use |
| Selected sample characters render in the chosen design | The full Unicode character map or every supported language |
| Glyphs are visually present at the chosen pixel size | Whether a fallback character was drawn by the font or by the browser |
| Re-loading the same file reproduces the same shapes | Exact print output, kerning quality, or hinting on other systems |
| A different file replaces the previous face cleanly | Accessibility, performance, or cross-platform rendering equivalence |
The tool does not generate an @font-face CSS block, subset the file, compare several fonts side by side, or claim that a clean render is permission to redistribute the file. Licensing decisions in particular must come from the font's actual license.
A Practical Glyph Inspection Checklist
Before deciding whether a font is worth installing, working through a short checklist usually answers most of the questions that matter. Open Font Previewer and type, in this order:
- Your own brand or product name in mixed case, to confirm shapes for the exact letterforms you publish.
- A pangram that includes every letter of the alphabet, to surface oddities such as a thin period or a quirky "g".
- Numerals from 0 to 9 at the smallest size you intend to use, to test for legible old-style or tabular figures.
- Every accented character you expect to need, especially the ones used by names in your audience.
- Punctuation you rely on: em dashes, smart quotes, the ellipsis, and any unusual marks such as the interpunct or middle dot.
- One word at a very large size — close to 200 pixels — to inspect outlines, terminals, and spacing decisions up close.
If every item renders as you expect, the file is a strong candidate for the next step: testing it inside the target browser at the target weight, then reading the license.
The Case for Inspecting Locally Before Installing
Installing a font writes files into a system Fonts folder and registers the face with every application that reads from that folder. On Windows and macOS this happens silently; on Linux it depends on the desktop environment. Even when you trust the source, each installation adds a permanent asset to your machine, and removing it requires more than deleting the file on some platforms. A browser-only preview sidesteps that side effect. The font exists only inside the page's document font set for as long as the tab is open. If you want to compare two files, you can do so without polluting your system with two new faces, and if you decide the file is wrong, closing the tab is enough to clean up.
This is also a safer way to look at font samples from unfamiliar sources: a font file is complex binary input processed by browser code, so keeping the bytes local and treating the preview as read-only is the cautious default. For a broader look at the same idea — previewing without committing to a system install — see how to preview fonts locally in your browser.
When a Preview Fails to Load
An accepted extension is no guarantee that a file will load. The browser font engine is strict about what it can decode. Common reasons a preview fails include a truncated or corrupted download, a file with the right extension but the wrong internal tables, a variable-font configuration the engine rejects, or a format the current browser does not support — for example, some legacy PostScript-flavoured fonts that never shipped as TTF, OTF, WOFF, or WOFF2. When a load fails, Font Previewer shows a visible loading error rather than pretending the font is loaded, so there is no silent fallback to a placeholder face. The simplest recovery steps are to re-download the file from the original source, confirm the extension matches the actual contents, and try the file in a different current browser before assuming the file is unusable.
The browser reports the decoding outcome through its FontFace and Document fonts APIs; both are documented at MDN — FontFace and MDN — Document fonts.