ASCII Art

About ASCII art

ASCII art is the practice of building pictures and stylised text out of the 95 printable characters in the ASCII set. The form predates the modern web by decades: early teleprinter operators sent novelty prints in the 1960s, and Usenet posts of the 1980s and 1990s carried entire galleries of cows, dragons, and movie posters rendered in characters because images could not pass through plain-text email. ASCII art lives on today in terminal banners, GitHub README badges, retro startup logos for command-line tools, and bot messages on Discord and IRC, where monospace rendering is the norm.

This generator focuses on the simplest and most common case: text-to-big-text. You type a phrase, the tool maps each character to a pre-drawn glyph (a small grid of ASCII characters that resembles the letter shape), and the glyphs are concatenated side by side across five lines. The output is plain text. You can paste it into a chat window, a code comment, a shell startup banner, or a static-site footer with no extra encoding.

How the rendering works

The font is a dictionary that maps each input character to a 5-line glyph stored as an array of strings. To render a phrase, the tool iterates the input one character at a time, looks up the glyph, and appends each glyph row to the corresponding output row. The final output is the five output rows joined with line breaks.

lines = ['', '', '', '', '']
for char in input.toUpperCase():
    glyph = font[char] || ['? ','? ','? ','? ','? ']
    for i in 0..4:
        lines[i] += glyph[i] + ' '
return lines.join('\n')

Each glyph occupies a fixed width per row, which is why the output is rectangular and aligns cleanly in any monospace font. Unknown characters fall back to a question-mark glyph so the row count stays consistent.

Worked example

Input: HI with the Big font.

 _ _    _
| | | || |
| |_| || |
| _ | || |
|_| |_||_|

The H glyph is five rows wide, the I glyph is two rows wide. The tool concatenates them side by side. The result is a 5-line block that prints identically in any terminal, Slack message, or fenced code block.

One subtlety worth noting: because the glyphs are joined left to right, the width of the finished banner grows with every character you add, while the height stays fixed at the font's row count. A five-letter word in the Big font is roughly 30 columns wide, already close to half an 80-column terminal, so short, punchy words read best. If you need a long phrase, split it across two separate banners stacked vertically rather than one line that overflows and wraps.

Font and glyph reference

Larger fonts wrap or overflow narrow terminals. Test in your target display before publishing.

Common pitfalls

• Non-monospace rendering. ASCII art only lines up when displayed in a fixed-width font. Many email clients and chat apps switch to a proportional font, breaking the alignment.
• Wide phrases overflow. 80-column terminals fit roughly 12 characters in the Big font. Longer phrases wrap and turn the art into gibberish.
• Lowercase and special characters. Most ASCII art fonts cover A-Z, 0-9, and a few punctuation marks. Lowercase often falls back to uppercase or a missing-glyph mark.
• Markdown code fences. Paste inside fenced code blocks (three backticks) so renderers do not interpret stray characters like _ as italic.
• Trailing whitespace. Some editors strip trailing spaces on save, which can collapse the right edge of glyphs. Disable that rule for files containing ASCII art.
• Unicode bait. "ASCII art" is sometimes pasted with Unicode box-drawing characters, which look better but are not strict ASCII. If your target system insists on ASCII, verify each character is in the 0x20 to 0x7E range.

Related tools

Frequently asked questions