Skip to content
Lizely

Font Previewer

Load a local TTF, OTF, WOFF, or WOFF2 file into the current tab and inspect custom text from 8 to 200 pixels.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Choose a trusted TTF, OTF, WOFF, or WOFF2 file no larger than 10 MiB.
  2. 2.Enter representative preview text and choose a whole font size from 8 to 200 pixels.
  3. 3.Inspect glyph coverage and appearance in the current browser; choose another file to replace the temporary face.

About Font Previewer

Font Previewer loads one local font file into the current browser tab and applies it to custom sample text. Choose a non-empty TTF, OTF, WOFF, or WOFF2 file up to 10 MiB, enter the text you need to inspect, and set a size from 8 to 200 pixels. The browser reads and validates the font through its FontFace API. The file is not uploaded to Lizely and is not installed on the operating system.

The font exists only in the page's document font set. Closing or refreshing the tab removes it, and choosing another file deletes the previous face from the document before loading the replacement. The tool does not copy bytes into a system Fonts folder, change application preferences, create a CSS package, or retain the file for a later visit.

Supported filename extensions are TTF, OTF, WOFF, and WOFF2. An accepted extension does not guarantee that the browser can decode the actual bytes. Damaged files, unsupported internal tables, mislabeled data, and formats the current browser rejects produce a visible loading error. The tool trusts the browser font engine rather than claiming to repair or convert a font.

The 10 MiB limit bounds browser memory and load time. Font files can contain complex tables and many glyphs, so a valid file may still take time to parse. The interface shows a loading state and prevents an older slow load from replacing a newer selection. Font bytes remain local, but users should still obtain font files from trusted sources because fonts are complex binary inputs processed by browser code.

Preview text is ordinary editable Unicode text. Whether a character displays in the chosen design depends on glyph coverage inside the font. Missing glyphs can appear as boxes or browser fallback characters. The tool does not synthesize missing glyphs, prove full language support, enumerate the character map, or distinguish a fallback glyph from the chosen font by image analysis.

Font size must be a whole pixel value from 8 to 200. This control changes CSS preview size only; it does not modify font units, hinting, outlines, kerning tables, or exported bytes. The line height is fixed for readable inspection. Browser zoom, device pixel ratio, operating-system rendering, and antialiasing can affect how the same font appears elsewhere.

The displayed label comes from the selected filename, not an asserted internal family or style record. A file called Demo Bold can contain different internal metadata, and the tool does not claim the filename is authoritative. It creates a unique temporary family name to avoid colliding with fonts already used by the site.

Use Font Previewer to check sample words, numerals, punctuation, uppercase and lowercase shapes, rough spacing, and font-file browser compatibility before installation or web integration. It does not calculate licensing rights, inspect embedding permissions, subset glyphs, convert formats, generate @font-face CSS, measure exact print output, or compare several fonts side by side. Licensing and redistribution decisions must come from the font's actual license.

The preview is visual and remains in the current page; no output download is created because the source file is unchanged. For reliable web use, test the font in the target browsers and confirm its licensed formats and weights. This tool provides a private first look, not a certification of correctness, safety, accessibility, performance, or cross-platform rendering equivalence.

Methodology & sources

Validate a bounded local file by supported extension, create a unique temporary CSS family, construct FontFace from its ArrayBuffer, await browser decoding, guard stale asynchronous loads, add only the successful face to document.fonts, apply the user sample and validated pixel size, and delete the previous or unmounted face from the document set.

Frequently asked questions

Is the font installed on my computer?
No. It is added only to the current page's document font set and disappears when the page closes or reloads.
Why do some characters show boxes or fallback shapes?
The selected font may not contain those glyphs, so the browser displays missing-glyph or fallback behavior.
Does a supported extension guarantee loading?
No. Damaged, mislabeled, or internally unsupported font data can still be rejected by the browser engine.
Is the font uploaded?
No. The browser reads the selected bytes locally through the FontFace API.

Related tools

Text Tools guides

View all