ASCII art for GitHub README

Put your banner in a README

1. Enter your project name above and choose a font. Small and Mini are useful starting points for compact titles.
2. Check the number of columns. A target of 80 is useful on desktop; use a narrower banner when mobile readers matter.
3. Choose Copy Markdown and paste into your README. The opening and closing code fences are included.
4. Keep a normal Markdown heading next to the banner so the project name remains readable without the artwork.

Why the code block matters

Spaces and line breaks define the picture. A fenced code block preserves the monospace layout; ordinary Markdown paragraphs do not. Copy Markdown wraps your result without adding a syntax-highlighting language.

```
+------------+
| MY PROJECT |
+------------+
```

Choose a width for your readers

There is no single width that fits every phone, font size and GitHub view. The generator reports the actual width of your banner and warns when it exceeds the target you select. A compact font or shorter title reduces the width without stretching or shrinking the characters. Preview your README on the devices you care about.

Headers, dividers and logos

Use a title at the top and shorter dividers for Installation, Usage and Contributing. For a picture-based project logo, try the image converter. For more fonts and PNG exports, open the full text generator.

Keep the information accessible

ASCII art can be difficult for screen readers. Put essential names, commands and instructions in ordinary text too, and use banners as decoration rather than the only way to convey information.