ASCII headers make a README stand out
A plain README opens with a line of text. A great one opens with a banner. ASCII art gives your project a recognisable header, section dividers, and status badges without adding image files to the repository — it is just text, so it loads instantly and works in any Git viewer.
Always use a fenced code block
GitHub Markdown renders normal text proportionally, which destroys ASCII alignment. Wrap the art in a fenced code block so it renders in monospace:
```__ __ _ _ _ _ ___| \/ | | | | | | | / __|| |\/| | |_| | |_| \__ \|_| |_|\__, |\___/|___/|___/```
Use a plain triple-backtick block (no language tag) so no syntax highlighter recolours your art.
Pick the right width
READMEs are read on wide desktop screens but also in narrow mobile previews and in the GitHub file list. Aim for 80–100 characters: wide enough for a confident header, narrow enough that it does not scroll sideways on a phone. For sub-section dividers, shorter is better.
Where to use it
- The project title banner at the very top.
- Section dividers above Install, Usage, and License.
- Simple status markers such as
== BUILD PASSING ==. - An ASCII logo generated from your app icon.
Keep it accessible
Screen readers will read ASCII art character by character, so do not bury essential information inside the art. Keep a normal text heading next to the banner so the page still makes sense without it.