ASCII Art Text Generator: Turn Any Phrase Into a FIGlet Banner
An ASCII art text generator converts ordinary words into oversized banner lettering drawn entirely from keyboard characters. The style is usually called FIGlet text, after the classic Unix program that popularised it, and it still turns up everywhere developers work in plain text: terminal login screens, README headers, CLI splash screens, code comment banners and retro forum signatures. This tool renders the art in your browser as you type, with a library of thirteen fonts, full control over spacing and framing, and one-click copy or download. Nothing is uploaded, so the text you enter never leaves your device.
How ASCII Banner Rendering Works
A normal font describes each letter as a scalable outline. A FIGlet-style font instead stores every character as a small rectangle of monospaced characters — the letter A might be five rows of slashes and underscores. Rendering a word means fetching each glyph rectangle and joining them together row by row, so row one of every letter becomes row one of the banner. Because the glyphs are fixed-width grids, the result only lines up when it is displayed in a monospaced context such as a terminal, a code editor or a Markdown code fence.
The interesting part is what happens where two letters meet. Full width places the glyph boxes edge to edge exactly as they were designed. Fitted layout slides them together until their ink would collide, which is the ASCII equivalent of kerning and typically saves one or two columns per letter pair. Smushing goes one column further and lets compatible strokes overlap and merge, producing the tightest banner of all. Extra wide does the opposite, inserting two blank columns for an airy, spaced-out look.
Choosing the Right Font for the Job
The bundled fonts are grouped by style. The Classic group holds line-art fonts drawn with _ | / \ characters: Standard at six rows tall, Small at four, Mini at three and a seven-segment Digital face that mimics a calculator display. The Block group contains solid fonts — Banner, Big, Block, Bold, Huge and a sheared Slant — that read well from a distance but consume far more columns. The Decorative group adds Shadow, Ghost and Stars for logos and splash screens.
Height and width matter more than looks. A six-row font turned into a forty-character-wide banner still fits a standard 80-column terminal, but the same phrase in Huge can easily exceed 200 columns and wrap into an unreadable mess. Switch to Font gallery mode to render your text in every font at once, compare the reported line count and widest line, then jump straight into the winner with a single click.
Fitting the Banner to a Terminal
The preview sits under a column ruler with a tick every five characters and a digit every ten, so you can see at a glance where column 80 falls. The statistics row reports the line count, the widest line, the total character count, the UTF-8 byte size and the number of ink characters. Byte size is measured with a real encoder rather than string length, because Unicode block fills and box-drawing borders take three bytes each while plain ASCII takes one — an important difference for size-limited message-of-the-day files.
The max width setting wraps long input at word boundaries so each rendered block stays inside your chosen column budget, and the fits-terminal badge compares the result against an 80, 100 or 120 column target.
Borders, Comment Wrappers and Custom Fill
Frames turn a banner into a boxed notice. Choose an ASCII +--+ frame for maximum portability, or Unicode single, double and rounded frames when you know the target terminal renders box-drawing characters. Border padding controls the breathing space between the art and the frame.
Comment wrappers prefix every line with //, # or --, or enclose the whole block in a C-style or HTML comment, so the banner can be pasted into a source file without breaking compilation. The fill character option swaps the drawing character of the solid fonts for anything you like — @, * or a solid block — while line-art fonts keep their own characters because a single fill would destroy their shapes.
Practical Uses and Limitations
Typical uses include README headers, /etc/motd login banners, section dividers in long shell scripts, npm package splash screens and chat art posted inside code fences. The main limitation is character coverage: the fonts handle A–Z, digits and common punctuation, while accented letters and emoji have no glyph and are reported in a warning under the preview. Keep phrases short, prefer uppercase for the block fonts, and always paste the result somewhere monospaced.