How FIGlet works
This generator uses FIGlet (the name is the initials of its creators plus “LETters”), the classic system for turning a short string into large text built from smaller characters. Each FIGlet font is a .flf file containing a multi-line ASCII drawing for every character; the engine looks up each letter of your input and concatenates their drawings horizontally, line by line, to build the banner. Different fonts produce dramatically different looks — blocky, 3D, script, outline — from the same text.
The two non-negotiables
ASCII art is fragile because its meaning is entirely positional. Two conditions must hold wherever you display it:
| Requirement | Why |
|---|---|
| Monospaced font | Every glyph must be equal width or columns drift |
| Preserved whitespace | Spaces carry the shape; collapsing them destroys it |
A terminal satisfies both by default. On the web, a <pre> tag or a Markdown code block satisfies both. Anywhere else (a rich-text editor, a chat with proportional fonts), expect breakage.
Where ASCII banners shine
- CLI tools — a banner printed at startup gives a program personality and identity.
- README files — a stylized project name at the top (in a code block).
- Source headers — big section markers in a codebase, in comments.
- Terminal MOTDs — login messages on servers.
Width is the silent killer
The other thing that breaks a banner is line wrapping. A FIGlet banner can easily be 100+ characters wide; if the terminal, editor, or comment column wraps at 80, the right side folds onto the next line and the art shatters. Keep banners narrower than your target’s wrap width, or disable wrapping where you display them. For glitchy/stacked text effects instead of clean banners, see the Zalgo Glitch Text Generator; everything here runs locally in your browser.