ASCII art generator
█ █ ████ █ █ ██ █ █ █ █ █ █ █ ████ ███ █ █ █ █ █ █ █ █ █ █ █ █ █ ████ ████ ████ ██
Made in your browser · nothing is uploaded
Turns text into a five-row block banner made of characters. Anything the font has no glyph for is left out and listed, rather than replaced with a question mark.
How to use the ascii art generator
The font here is five rows tall and built in, rather than loaded from a figlet file. That is a size decision: a real figlet font is tens of kilobytes for one typeface, and this page has a JavaScript budget to keep. Five rows is enough to be clearly legible in a terminal or a code comment, which is where these end up.
ASCII art in this sense goes back to teletypes, where the only way to make a heading was to type characters in the shape of letters. It survives because a plain-text file has no other way to emphasise anything — which is why you still find banners at the top of source files, in terminal splash screens and in the output of command-line tools.
A practical note on where it breaks. The banner only lines up in a monospace font, where every character is the same width. Pasted into an email, a word processor or most chat apps it becomes a jumble, because those render in a proportional font where an M is wider than an i. Code comments, terminals, README files and anywhere marked as code will be fine.
Unsupported characters are dropped and named rather than substituted. A question mark standing in for a missing glyph reads as though it were part of the text, which is worse than an obvious gap.
Questions
It is pasted into a proportional font. It only lines up in monospace — a terminal, a code block or a README.
The built-in font has no glyph for them. They are listed rather than replaced with a question mark, which would read as part of the text.
Not here. A real figlet font is tens of kilobytes for one typeface, which does not fit this page’s budget.
Headings in plain text — source file banners, terminal output, README files. Places with no other way to emphasise anything.
No. Everything happens in your browser — you can load the page, go offline, and it still works.