ASCII Art Generator
Turn text into big ASCII art banners - 30 fonts, frames, colours and effects - then copy, or download as TXT or PNG
100% free. Runs entirely in your browser - your files and data never leave your device and nothing is uploaded to any server.
Font: Standard
Loading font…
Compare fonts
Loading…
Loading…
Loading…
Loading…
Recent banners
Banners you copy or download appear here, so you can re-open yesterday’s one in a tap.
Batch to ZIP
One name per line - each becomes its own .txt banner with the current font and settings.
About this tool
ASCII art banners - big letters built entirely from plain text characters - predate graphical fonts online: they were how people made headers in early forums, code comments and terminal output where no image could be displayed, using the classic "figlet" font format that is still the standard today. This tool renders any short word or phrase in four real figlet fonts - Standard, Big, Slant and Banner - entirely in your browser, so the result is always plain text you can paste into a code comment, README, terminal message or plain-text email where a real image would not work at all.
How to use this tool
- Type your textUp to 60 characters per line and up to 6 lines - or tap a template such as HAPPY BIRTHDAY or GAME OVER.
- Pick a fontChoose from 30 real FIGlet fonts - Standard, Doom, ANSI Shadow, Star Wars, 3-D and more. Open the gallery to see your own text in every font, and star the ones you use.
- Style itPick Fitted, Smushed or Full width spacing, fit it to 40, 80 or 120 columns, add a frame, mirror or flip it, stack it vertically, or redraw it in blocks, shades or #.
- Copy or downloadCopy as plain text, as a Markdown code block or as HTML, or download a .txt, a PNG or a share card. Colour is for the preview and PNG only - copied text is always plain.
Where ASCII art banners work best
ASCII banners shine in places that only show plain text: code comments, README files, terminal startup messages, commit messages and old-school forum signatures. Paste them inside a code block so they stay in a monospaced font and line up.
Keep banners short - one or two words - because wide banners wrap on narrow screens and break apart.
Key features
- 30 real FIGlet fonts, rendered in your browser from the actual .flf files, with a searchable gallery, favourites and a random-font button.
- Three spacing modes (Fitted, Smushed, Full width), fit-to-width wrapping, frames, mirror/flip, vertical banners and character sets.
- Copy as text, Markdown or HTML; download TXT, PNG or a share card with an optional QR code; batch many names into one ZIP.
- Pure plain text output - pastes correctly into a terminal, code comment, README, or any monospace context. On-screen colour is a preview only; the copied text is always plain.
- Free, instant, no watermark, no signup - fonts load once per session, then render offline.
Common uses
- A section header in a plain-text README or CHANGELOG file.
- A startup banner printed to a terminal or CLI tool.
- A comment-block header in source code.
- A novelty signature or banner for a plain-text forum, email or chat.
Tips for better results
- ASCII banners need a MONOSPACE font to line up correctly - if it looks jagged after pasting, the destination is using a proportional font.
- Keep it to one short word or a very short phrase; the banner width grows fast, especially in Big or Full width mode - a long phrase becomes impractically wide to read.
- Slant and Big read best in Compact mode; Banner - a chunkier, denser font - can look more distinct in Full width if Compact looks too fused for your taste.
- Characters the font has no glyph for render as a blank space rather than breaking the banner - check the warning note if that matters for your phrase.
Mistakes to avoid
- Pasting the result into a rich-text editor (Word, Gmail's default compose) where the font is not monospace - the columns will not line up.
- Expecting the on-screen colours to survive copy-paste - they are a preview only; the clipboard always gets plain, uncoloured text so it works anywhere plain text is expected.
- Making the phrase too long for the destination's line width - a wide terminal or narrow README column can wrap a banner and ruin it.
- Assuming every font looks equally readable at every length - Big and Banner are wide by design; a longer phrase fits Standard or Slant more comfortably.
Frequently asked questions
Real ones - all 30 fonts are parsed directly from their genuine .flf font files, the same format the classic Unix `figlet` command uses, so the letters match what figlet has always produced.
Fitted moves each letter as close to its neighbour as it can without touching. Smushed goes one column further, so neighbouring letters share an edge - the tightest, most figlet-like look. Full width gives every letter its own fixed cell, like a classic terminal banner.
No - rainbow, custom and Matrix colours are for the on-screen preview and the PNG only. Copy and .txt downloads are always plain, uncoloured text, which is what works in a terminal, README or chat.
ASCII banners rely on every character taking up the same width (a monospace font) so the columns of "#" and other characters line up into letter shapes. If you paste into an editor using a proportional (variable-width) font, like most rich-text editors default to, the alignment breaks. Paste into a code block, terminal, or plain-text editor instead.
It renders as a blank space rather than breaking the rest of the banner - a warning appears above the result when your input contains unsupported characters.
Each font file (10-35 KB) loads the first time you choose it; after that rendering is instant and works offline for the rest of your session.