E-ink font preview
A page of prose in your font, at the panel's exact size and its four grays, before you copy anything to the card.
480×800 · 4 grays · 1:1
Screen
Line breaks are this page's, not the firmware's: a reader paginates with its own margins, hyphenation and widow rules, so the words per line will differ slightly. The size, the grays and the font are the reader's.
What it does to the file
Everything below can be checked against the file you get back.
- Four grays decide more than the font
- The panel draws black, two mid grays and white. A thin stroke at 18 px does not become a thin gray line — it becomes a dot pattern, and at arm's length that reads as gray fuzz. The percentage under the preview is the share of ink that ends up that way.
- The layout is ours, not the firmware's
- Line breaks, hyphenation and margins here are approximations. A reader paginates with its own rules, so the words per line will differ by a few. What carries over exactly is the size, the four grays and the glyph shapes.
- What the file says about itself
- The table directory is read in the tab: a colour-glyph table (COLR, SVG, sbix) means colour the panel cannot show, an fvar table means a variable font that the reader resolves to one instance, and the glyph count tells you how far the character set goes before you find a box on the page.
- Nothing is uploaded
- The font is loaded into this tab and rendered here; the file never leaves the browser, which is also why there is no font to download afterwards — we cannot redistribute someone's font.
Why a font needs its own preview
A wallpaper fails loudly: it is the wrong size, or it is mush. A font fails quietly. It looks acceptable on a laptop, and then on the reader the stems are dot patterns, the quotes are boxes, and the only fix anyone suggests is “try another font”. This page makes the reduction visible at the size it happens: Licorice on a 480×800 Xteink panel, where the body text sits somewhere between 18 and 28 pixels and the panel has four levels to draw it with.
The second half of the problem is the character set. A font built for English may have no é, no — and no Cyrillic, and a reader with no fallback font draws a box. The probe line includes accents, quotes, dashes and two non-Latin scripts so a gap shows up here rather than on page forty of a book.
What this page cannot tell you
Whether your firmware accepts the file at all, where it goes on the card, and how big the menu lets you set it. Those are firmware facts that change between builds, and they belong in that firmware's documentation — the firmware chooser links each project's own pages.
Questions
›What font format does an e-ink reader take?
Xteink's stock firmware Licorice takes TrueType (TTF) and stopped showing the older BIN/XTF fonts; the community firmwares each document their own folders and formats. This page reads TTF, OTF and WOFF because that is what a browser can load — check your firmware's docs for what it accepts before you copy a file across.
›Why does my font look thin or muddy on the reader but fine on my laptop?
A laptop draws at 200–400 ppi with 256 gray levels; the reader has four, at about 220 ppi in a 480×800 window. Light weights lose their stems to dithering first, and small sizes lose them next. Raise the body size a step, or pick a face with a heavier regular weight — the percentage under the preview is the quickest read on which of the two is happening.
›Is the preview exactly what the device shows?
The size, the four grays and the glyph shapes are the device's. Two things are not: the line breaking is this page's greedy wrapper rather than the firmware's typesetter, and the reader's own anti-aliasing and hinting may be tuned differently from a browser's. Judge weight, spacing and legibility here; judge pagination on the device.
›Why does the preview say a character is missing when my editor shows it?
An editor substitutes a glyph from another font without telling you. A reader usually has no second font to fall back on, so it draws a notdef box. The check here compares each character's width with the font's own missing-glyph width, so a substituted accent shows up as missing rather than hidden.
›Should I use a variable font?
Only if you can pick the instance. A reader that takes a variable file without offering an axis gets the default weight, which is often lighter than the one you previewed. If the preview flags a variable axis, try the static weight you actually want instead.
›Which body size should I use?
There is no single answer: it depends on the face, the reading distance and your eyes. Drag the slider and watch the percentage of ink that turns into dots — the size where that number stops climbing steeply for a step up in size is usually the size that reads best.
›Is it free?
Yes, no sign-up and nothing watermarked.
Next
- Licorice on the X4 Pro and X4 Classic the stock firmware's fonts, Desk and sleep screen, and what an upgrade resets.
- What four grays do to a picture the same reduction, on photos instead of text.
- Xteink X4 Pro wallpaper size 480×800, and what the panel draws.