ASCII Art Generator

What is figlet?

Figlet — Frank, Ian and Glen’s letters — is a small utility originally written in 1991 to render large banner-style ASCII text. It defines a font file format with the .flf extension, in which each printable character is laid out as a small multi-line grid of characters (/, \, _, |, +, - and space, mostly). Render a string by looking up each input character in the font, then concatenating the per-character grids horizontally row-by-row. The result is what every developer who has ever opened a MOTD file or read a verbose CLI prompt has seen — large stylised letters made of plain ASCII characters.

Figlet has shipped with every Linux distribution for three decades and is the default banner-text tool in scripts, container entrypoint prompts, README hero sections, and the welcome screens of self-hosted services. There are thousands of community-contributed .flf fonts in the wider archive; this tool ships eight of the most-used permissively-licensed ones.

How it works

The engine is the figlet JavaScript port — a faithful reimplementation of the original C figlet’s layout logic. When you type into the input field, the engine:

1. Loads the chosen .flf font file (lazy — only the fonts you actually use are downloaded, and once downloaded they are cached by the browser).
2. Parses the font’s header: character height in rows, baseline, maximum width, hardblank character, layout rules.
3. For each character in your input, looks up the corresponding grid in the font (or substitutes a space for unsupported characters).
4. Concatenates the per-character grids horizontally, applying the font’s smushing rules — figlet fonts include rules for how adjacent letters should overlap so the result reads as a single word rather than spaced-apart letters.
5. Renders the resulting multi-line string into the preview <pre> element.

Smushing is the subtle bit: at full kerning, H and e sit side-by-side with a gap; with universal smushing, the right edge of H and the left edge of e overlap one column, producing tighter, more cohesive banners. The Standard, Slant and Big fonts all specify smushing rules in their headers; the tool respects them.

Common use cases

• Terminal welcome prompts. Add a figlet banner to your ~/.bashrc or your container’s entrypoint.sh so SSH login greets you with the host name in big letters. Standard or Slant fonts work well.
• README banners. Drop a figlet rendering of your project name into the first lines of the README, inside a code block. It shows in GitHub, GitLab, and on the terminal when someone cats the file. Big or 3-D fonts make the strongest first impression.
• Source-code comments. Section headers in long source files — // ─── HELPERS ─── style, but rendered as big ASCII letters — make navigation easier in editors without good outline support. Small or Standard fonts at small inline sizes are the right fit.
• Retro art and demos. ASCII art remains a beloved subculture — Doom, Banner and Block fonts produce the chunky retro look that fits BBS-era nostalgia, demoscene productions, and text-mode game splash screens.
• Slide decks for technical talks. A figlet rendering of the next section’s title, copy-pasted into a monospace text box, is a surprisingly effective slide.

How to use this ASCII Art generator

1. Type your text into the Input field. Short words (3 to 12 characters) work best — figlet banners get unwieldy fast.
2. Pick a Font from the dropdown. Standard is the safe default; Slant gives italicised letters; Big and 3-D produce taller, chunkier output; Doom and Block are the strongest retro looks; Banner is wide and minimal; Small is for inline use.
3. The Preview updates immediately as you type or change fonts.
4. Click Copy to grab the result as plain text — paste anywhere that accepts monospace text (terminal, README, comment block, chat, slide).
5. Click Download .txt to save the result as a text file.

Quality tips

ASCII banners need a monospace font to render correctly. If you paste the output into a destination that uses a proportional font (plain Notion text, regular Word, an email body without code formatting) the letters will collapse into illegible noise. Always paste into a code block, a <pre> element, or a monospace-formatted section.

For longer text, prefer the narrower fonts (Standard, Slant, Small). Big, 3-D, and Block fonts are tall and wide — a five-character word in Block may already overflow a standard 80-column terminal.

Privacy

The figlet engine runs in your browser. The .flf font files are static assets — fetched from the page’s CDN on first use, cached thereafter — and contain only character templates, no scripts. Your input text is processed entirely client-side; no network request ever includes the string you’re rendering. Confirm in the browser Network panel before pasting anything sensitive.

Compatibility notes

The output is plain ASCII / Unicode text. It works in every terminal emulator, every editor, every chat, every Markdown renderer, every code-block in every tool. The visual quality depends on the display font — anything monospace renders the banner correctly; anything proportional collapses it. Across Linux, macOS, Windows Terminal, iTerm, Alacritty, Kitty, Termux, the result is identical because the input is just characters.