ASCII Art Text Generator

Convert text to large ASCII art using a 5×5 pixel block font.

Text (max 20 chars · supports A–Z, 0–9, common punctuation)

Fill character

Letter spacing

Output

Letters: 0

About ASCII art text

ASCII art text places printable characters in a grid to form large letters. This generator uses a 5×5 pixel bitmap font — each letter is 5 pixels wide and 5 tall. The output is plain text: paste it into chat apps, terminal banners, README headers, or code comments. Lowercase input is rendered using the same uppercase glyphs. Supported characters: A–Z, 0–9, and common punctuation including ! ? . , - _ + = / # * ( ) [ ] @ : < > ^ % $ & " '. Related: text repeater and upside down text generator.

Built and maintained by Meet Shah · Last updated 19 July 2026

What this tool is used for

Producing a banner for a command-line tool's startup output.
Making a heading for a README that renders in any terminal.
Creating a text-only logo for a plain-text channel.
Producing a splash graphic for a script.
Making a header for a log file or a build output.

Frequently Asked Questions

Why does the art only line up in some places?: It needs a monospace font. Every character in the art is positioned by counting columns, so a proportional font — which most chat apps, email clients and web pages use by default — collapses the alignment immediately. Wrap it in a code block wherever one is available.
What breaks it besides the font?: Line wrapping and whitespace trimming. Art wider than the container wraps mid-figure and is unrecoverable, and any system that strips trailing spaces destroys the right-hand edge of letters that end in blanks — a common surprise in Markdown and in email.
Where does the style come from?: FIGlet, a 1991 program whose font files (`.flf`) defined the banner lettering still used in terminal splash screens and CI logs today. Its name comes from "Frank, Ian and Glenn's letters", after its authors.
Is ASCII art accessible?: No — a screen reader announces it character by character, which is unusable. Always pair it with the plain text it spells, and keep it out of anything essential. In a terminal application, gate it behind a flag rather than printing it by default.
Where is it still genuinely useful?: CLI banners, build logs, README headers, commit-message art, and diagrams in code comments — anywhere a monospace grid is guaranteed and an image is not possible. That last case is the strongest: a box-drawing diagram in a comment survives every diff.

Common errors and gotchas

Producing a banner wider than the terminal, which wraps and becomes unreadable.
Rendering in a proportional font, which destroys the character grid the art depends on.
Using it where the text must be searchable or accessible, since it is a picture made of letters.
Assuming every character is available in a given font, where box-drawing glyphs often are not.
Putting it in output that gets parsed by another program.