Examples

Ideas for using ASCII glyphs.

Use these patterns as starting points for README headers, CLI banners, terminal dashboards, social profiles, and docs.

README project logo

  ###   #####  #####  ###  ###
 #   #  #      #      #  # #  #
 #####  ####   ####   #  # #  #
 #   #  #      #      #  # #  #

Great for open-source repositories and release notes.

Terminal welcome banner

╔════════════════════╗
║  deploy complete  ║
╚════════════════════╝

Use box fonts for scripts, demos, and status messages.

ANSI color accent

[96mHELLO TERMINAL[0m

Copy with ANSI enabled when pasting into compatible shells or logs.

Compact profile heading

ＡＳＣＩＩ ＧＬＹＰＨ
ᴛᴇxᴛ ᴀʀᴛ ғᴏʀ ᴅᴇᴠs

Compact Unicode styles fit better in bios, profile summaries, and community pages.

Documentation section marker

01 │ #####  #####  #####  #   #
02 │ #      #        #    #   #
03 │ ####   ####     #    #   #
04 │ #          #    #    #   #
05 │ #####  #####    #     ###

Ladder or scanline styles can make generated docs easier to skim without using color.

Example recipes

Open-source package: Use Slant or ANSI Block for the package name, then place installation commands underneath in a regular code block. This gives the README personality while preserving readability.

Deployment script: Use Rounded Box for status messages and Matrix Green for successful terminal-only output. Avoid color if the script writes to log files consumed by other tools.

Community profile: Use Fullwidth or Small Caps for compact headings. Large ASCII banners can be clipped by profile layouts, while compact Unicode styles tend to fit better.

Internal dashboard: Use Box Sign, Ladder, or Scanline to separate sections in monospaced terminal dashboards. Clear separators reduce scanning time during operations work.

Copy-paste checklist

Before publishing an example, check it in the same environment where readers will see it. Markdown pages usually need fenced code blocks to preserve spacing. Terminal output can use ANSI color, but documentation should usually stay plain. Social profiles may collapse extra spaces, so compact styles often work better there.

If an example looks too wide, shorten the message before changing the font. The clearest ASCII art usually communicates one idea at a time: a project name, a status, a section label, or a small decorative signature.

Before and after

Weak use	Better use	Reason
A full sentence rendered as a giant banner.	A two-word status rendered in a rounded box.	Shorter text keeps the shape legible and avoids horizontal scrolling.
ANSI escape codes pasted into a README.	Plain ASCII in a fenced code block.	Markdown readers see clean characters instead of raw control sequences.
A decorative header with no normal title nearby.	A normal heading followed by optional ASCII art.	Search, accessibility tools, and skimmers still understand the content.

How to adapt these examples

Start by replacing the words, not the style. If the result becomes too wide, change only one setting at a time: reduce spacing, choose a narrower font, then remove color if the destination is not a terminal. This makes it easier to understand which choice improved the final output.

For production use, keep the generated art close to the ordinary text it describes. A deployment banner should sit near the deployment command. A README logo should sit near the project title and installation command. Context turns text art from decoration into a useful navigation cue.