Smallest Typeface

If you can spare extra pixels, Tom Thumb (3x5) [1] is more legible. The upper case M and N are somewhat hard to distinguish without context, but it&#x27;s the only major flaw compared to this one.<p>Tom Thumb is also Public Domain (CC0).<p>[1] <a href="https:&#x2F;&#x2F;robey.lag.net&#x2F;2010&#x2F;01&#x2F;23&#x2F;tiny-monospace-font.html" rel="nofollow">https:&#x2F;&#x2F;robey.lag.net&#x2F;2010&#x2F;01&#x2F;23&#x2F;tiny-monospace-font.html</a>

I recently put together some very small fonts (3x3, 3x4, 3x5, 3x6, 4x4, and 5x5) and tried to enumerate most of the possible glyphs as part of working on little projects on SSD1306 OLED screens: <a href="https:&#x2F;&#x2F;moonbench.xyz&#x2F;projects&#x2F;tiny-pixel-art-fonts&#x2F;" rel="nofollow">https:&#x2F;&#x2F;moonbench.xyz&#x2F;projects&#x2F;tiny-pixel-art-fonts&#x2F;</a>

World&#x27;s smallest typeface <i>for 36 alphanumeric characters</i>, to be exact. :-) There are some small typefaces for other scripts; my go-to example is the Misaki font [1] that supports all JIS X 0208 character within 8x8 pixels (spacing included, and most glyphs are within 7x7 bounds). It is incredibly hard to recognize some individual characters at this size, but the overall text is surprisingly readable.<p>[1] <a href="https:&#x2F;&#x2F;littlelimit.net&#x2F;misaki.htm" rel="nofollow">https:&#x2F;&#x2F;littlelimit.net&#x2F;misaki.htm</a>

A while ago I created an even smaller typeface (2x3) but that is barely readable without memorising certain glyphs:<p><a href="https:&#x2F;&#x2F;zserge.com&#x2F;posts&#x2F;tiny-font&#x2F;" rel="nofollow">https:&#x2F;&#x2F;zserge.com&#x2F;posts&#x2F;tiny-font&#x2F;</a>

S and 5 are identical, as are Z and 2, and O and 0 (edit: and Q and 9). No punctuation either; semicolon vs. colon vs. exclamation mark needs creativity. There&#x27;s no hope for $ or *.

I threw together a figlet font for this typeface, with a preview, here: <a href="https:&#x2F;&#x2F;wonger.dev&#x2F;posts&#x2F;monospace-dump#creations" rel="nofollow">https:&#x2F;&#x2F;wonger.dev&#x2F;posts&#x2F;monospace-dump#creations</a><p>It won&#x27;t render nice here because of line spacing and unicode but it should work fine in the terminal.<p>See also another 3x3 font and someone else&#x27;s figlet port of that one:<p><a href="https:&#x2F;&#x2F;fakoo.de&#x2F;en&#x2F;fakoo&#x2F;fakoo-ttf.html" rel="nofollow">https:&#x2F;&#x2F;fakoo.de&#x2F;en&#x2F;fakoo&#x2F;fakoo-ttf.html</a><p><a href="https:&#x2F;&#x2F;brontosaurusrex.github.io&#x2F;2021&#x2F;05&#x2F;18&#x2F;3x3-typeface&#x2F;" rel="nofollow">https:&#x2F;&#x2F;brontosaurusrex.github.io&#x2F;2021&#x2F;05&#x2F;18&#x2F;3x3-typeface&#x2F;</a>

Not totally sure what I&#x27;d use this for. Silkscreen is bigger, but is a lot more legible at small sizes.<p><a href="https:&#x2F;&#x2F;fonts.google.com&#x2F;specimen&#x2F;Silkscreen" rel="nofollow">https:&#x2F;&#x2F;fonts.google.com&#x2F;specimen&#x2F;Silkscreen</a>

this is actually 4×4 if you&#x27;re counting pixels needed on the output device instead of rom space needed; another, more comprehensive font of the same size is <a href="https:&#x2F;&#x2F;simplifier.neocities.org&#x2F;4x4" rel="nofollow">https:&#x2F;&#x2F;simplifier.neocities.org&#x2F;4x4</a><p>the same problem happens with the public-domain &#x27;tom thumb&#x27; font pushfoo linked in <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=38800409">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=38800409</a>. it is actually 4×6 (24 output pixels) but claims to be 3×5<p>it can be accessed despite tls problems at <a href="http:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20230828193815&#x2F;https:&#x2F;&#x2F;robey.lag.net&#x2F;2010&#x2F;01&#x2F;23&#x2F;tiny-monospace-font.html" rel="nofollow">http:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20230828193815&#x2F;https:&#x2F;&#x2F;robey.lag....</a> but says &#x27;Please do not post this article to Hacker News.&#x27;<p>my own 4×6 font is demonstrated at <a href="http:&#x2F;&#x2F;canonical.org&#x2F;~kragen&#x2F;sw&#x2F;dofonts-1k.html" rel="nofollow">http:&#x2F;&#x2F;canonical.org&#x2F;~kragen&#x2F;sw&#x2F;dofonts-1k.html</a>, where it fits into a 1024-byte web page along with all the logic needed to render ascii text with it; but the proportional font i used in <a href="http:&#x2F;&#x2F;canonical.org&#x2F;~kragen&#x2F;bible-columns" rel="nofollow">http:&#x2F;&#x2F;canonical.org&#x2F;~kragen&#x2F;bible-columns</a> (rendered with <a href="http:&#x2F;&#x2F;canonical.org&#x2F;~kragen&#x2F;sw&#x2F;netbook-misc-devel&#x2F;propfontrender.py" rel="nofollow">http:&#x2F;&#x2F;canonical.org&#x2F;~kragen&#x2F;sw&#x2F;netbook-misc-devel&#x2F;propfontr...</a>) is at <a href="http:&#x2F;&#x2F;canonical.org&#x2F;~kragen&#x2F;sw&#x2F;netbook-misc-devel&#x2F;6-pixel-1-bit-proportional-font.png" rel="nofollow">http:&#x2F;&#x2F;canonical.org&#x2F;~kragen&#x2F;sw&#x2F;netbook-misc-devel&#x2F;6-pixel-1...</a> and is slightly smaller; it averages 21.5 pixels per character. this is more than anders de flon&#x27;s so-called 3×3, which is 16 pixels per character, but it supports the full character set, if you think ascii is the full character set anyway. so does simplifier&#x27;s 4×4 font<p>i think you could do better by using grayscale for antialiasing, and as rafabulsing pointed out, matt sarnoff&#x27;s millitext <a href="http:&#x2F;&#x2F;www.msarnoff.org&#x2F;millitext&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.msarnoff.org&#x2F;millitext&#x2F;</a> uses subpixel antialiasing to get very readable text at 1⅔×5 pixels

I took a slightly different approach, while also using a 3×3 grid. It&#x27;s explained here: <a href="https:&#x2F;&#x2F;minimalwim.com" rel="nofollow">https:&#x2F;&#x2F;minimalwim.com</a><p>It&#x27;s more of a typographic concept than being fit for actual use, but it was interesting to explore creating a font within a tight set of constraints.

Hopefully the opt-out button and disclaimer designers won&#x27;t discover this.

Anyone have some text set in this font so we can all see how easy it is to read?<p>On my MacBook Air 13&quot; seems like you could fit 640*400 = 256000 characters at once. Which ought to fit, for example, the complete text of Alice&#x27;s Adventures in Wonderland.

For anyone thinking about using this: At some point I tried to do a logo for myself on a 3x3 grid (so pretty much the same as this) and while the text was perfectly readable to me a few people I tested it with couldn&#x27;t read it.

I blame Adobe, Microsoft and Apple for the common misuse of font instead of typeface.

Didn&#x27;t everyone do this exact font in the 80s when we did not have enough room and needed something for eg debug output on our computers ?

3×3 pixels is almost certainly the smallest legible font.<p>You need at least 6 pixels to encode 27 letters + 10 digits because:<p><pre><code> 2⁵ &lt; 37 2⁶ &gt; 37 </code></pre> But 2×3 pixels seems unlikely to be legible. From 2×3 pixels, you can increment the height to 2×4 pixels or the width to 3×3 pixels. The latter feels more feasible.

Does anyone remember that one weird block script that people post to HN sometimes? The only thing I remember is that it&#x27;s the kind of thing that would take a good while to learn to read—maybe the blocks for the letters in a word could be recognised as a single shape when juxtaposed?

reminds me of the time I&#x27;d have the smallest font possible running in xwindows with a server log scrolling in it. I was so used to the pattern of the logs, I&#x27;d only need to see a change in said pattern to know something was wrong.<p>this would probably have beaten that smallest font back then

A similar concept for print: the Miniscule family, supposedly legible down to 2pt. <a href="https:&#x2F;&#x2F;typographica.org&#x2F;typeface-reviews&#x2F;minuscule&#x2F;" rel="nofollow">https:&#x2F;&#x2F;typographica.org&#x2F;typeface-reviews&#x2F;minuscule&#x2F;</a>

Some observations:<p>- 5 and S are indistinguishable<p>- 0 and O are indistinguishable<p>- 2 and Z are indistinguishable<p>- no lowercase<p>While context will generally suffice in making the indistinguishable glyphs understood correctly, there are some use cases where we mix letters and numbers in the same string and those would be ambiguous.

With subpixel rendering you could get down to 1x3 (or at least 2x3). ;)

That&#x27;s 9 bits, or 512 total combinations in that grid; thus, theoretically one should be able to fit all of ASCII, but many of the characters would be very difficult to distinguish or recognise.<p>(Incidentally, a common 7-segment display can also fit all of ASCII, and if you include a decimal point too, can represent a single byte completely: <a href="https:&#x2F;&#x2F;dkeenan.com&#x2F;7-segment%20ASCII%20characters.txt" rel="nofollow">https:&#x2F;&#x2F;dkeenan.com&#x2F;7-segment%20ASCII%20characters.txt</a> )

Damn, I&#x27;m pretty sure I did something similar on a piece of paper when I was a kid. I could have been the &quot;creator of the world&#x27;s smallest typeface&quot;!

Not sure I&#x27;d be able to read this without context off the bat (especially the E, G, M, and W), but it&#x27;s an interesting project!

In an ideal world where people are fluent in binary, we would only need 5 pixels. Just imagine how efficient the world could be…

Smallest monospace typeface. You could make &quot;I&quot; and &quot;1&quot; a single line and make &quot;J&quot;&#x2F;&quot;L&quot; and &quot;P&quot;&#x2F;&quot;Q&quot; only 2 pixels wide.

I think this is a more elaborate approach.<p><a href="https:&#x2F;&#x2F;simplifier.neocities.org&#x2F;4x4" rel="nofollow">https:&#x2F;&#x2F;simplifier.neocities.org&#x2F;4x4</a>

The first two Wing Commander games were great at this. You could read everything and it was still tiny.

Try mouse, the smallest pixel font that is surprisingly readable at really small font sizes.

Any samples with this font? I&#x27;d love to see it in action even if it&#x27;s impossible to read.

Why isn’t the M missing the top center pixel? Seems like it would make it way easier to read

Pretty great. I only saw s and 5, as well as q and 9 were the same symbols.

0 and O is same.

(2005)

Wait til that they figure out that braille is only 3x2...

i like it!