What ASCII art is and why it survives
ASCII art uses keyboard characters to form drawings and large typography. It started as a pragmatic solution on 1960s teletypes when graphics weren't an option: if you wanted a prominent header, you built it from asterisks. Sixty years later it's still everywhere — in every GitHub README, in the welcome banners of projects like Docker or Kubernetes when you launch the CLI, and in plain-text email signatures of developers who prefer not to deal with HTML.
Real use cases in 2026
- Open source READMEs. A logo in ASCII at the top of the file gives the project personality and renders identically on GitHub, GitLab, Bitbucket or a local git log.
- CLI welcome banners. The first time someone runs your tool, seeing the project name big creates instant identity.
- Section dividers in code. Marking large sections with an ASCII heading helps you scan long files without opening a symbol explorer.
- Slack, IRC, forums. Anywhere rich-text formatting is awkward, ASCII art conveys hierarchy without images.
- Memorable error messages. A big ASCII banner makes a critical failure impossible to miss in logs.
Monospaced fonts: rule number one
ASCII art only works when every character takes the exact same horizontal space. That property is called monospaced or fixed-width. Examples: JetBrains Mono, Fira Code, Menlo, Consolas, Courier. If you copy an ASCII banner and paste it into Word with Calibri, everything falls apart because M is wider than i. Before pasting your art anywhere, confirm the destination renders with a mono font.
Choosing the right size
Bigger isn't better. A 12-line tall banner in a README pushes the actual content below the fold, and visitors leave before reading the description. Practical rule: the ASCII shouldn't take more than a third of a typical 1080p screen, which is roughly 6 to 8 lines. For terminal output, 4 to 6 lines is the sweet spot.
Encoding compatibility
Pure ASCII uses only 128 characters and renders correctly on any system built since 1963. If your banner uses extended box-drawing characters from Unicode or CP437, it will look great on modern systems but may break on legacy terminals or emails forced into strict ASCII encoding. For maximum portability, stick to the 95 basic printable characters.
Presentation tips
- Center the banner where context allows; don't pin it to the left margin.
- Leave a blank line above and below so it breathes visually.
- If the ASCII is wide, wrap it in a markdown code block so the reader's word-wrap doesn't break it.
- Don't mix two ASCII fonts in the same block — it looks inconsistent.