Text

Text to ASCII Art

Details

How to use Text to ASCII Art

What the tool does, how to run it, and what to expect from the result.

How to turn text into an ASCII art banner

Type a word and the tool maps each character to a 5-row glyph made of hash characters and joins them side by side with your chosen spacing. Unsupported characters become blanks, and everything is upper-cased first.

The result is plain text, so it can be pasted anywhere that renders in a monospace font.

  • Type a short word, ideally under about 12 characters.
  • Choose the letter spacing: Tight, Normal, or Wide.
  • Check the preview for blank gaps, which mean a character is not in the font.
  • Click Copy ASCII art to put the 5-line banner on your clipboard.
  • Paste it into a code block, a code comment, or a terminal, never into proportional-font text.

How wide the banner gets, and why that is the real limit

Every glyph in the font is four columns wide and five rows tall, and the spacing setting inserts one, two, or three blank columns between neighbouring glyphs. That makes the width predictable: roughly five columns per character at Tight, six at Normal, and seven at Wide. A seven-letter word at Normal spacing is about forty columns, which fits anywhere.

The input cap is forty characters, but forty characters is not a usable banner. At Normal spacing it is around 240 columns wide, which wraps in every terminal, in the GitHub file view, and in most editors, and a wrapped banner is unreadable noise rather than a header. Treat about twelve characters as the practical ceiling and one short word as the sweet spot.

  • Tight adds 1 blank column between glyphs, Normal 2, Wide 3.
  • Roughly 5, 6, or 7 columns per character respectively.
  • Keep the result under about 80 columns so it survives a default terminal.

Where an ASCII banner belongs

The output is plain text whose alignment depends entirely on every character occupying the same width. In a monospace context that holds and the letters read as intended: a fenced code block in a README, a block comment at the top of a source file, a shell script header, a MOTD, or a CLI splash screen.

Outside a monospace context it collapses. A word processor, an email body, an HTML paragraph, or a chat message posted outside a code fence will render each character at its natural width, and the vertical strokes of the letters shear apart into noise. If you cannot wrap it in a code fence or a pre block, do not use it there.

Tips

Getting a better result out of Text to ASCII Art

Specific settings and thresholds, not general advice.

  • The font is 5 rows tall and made of hash characters, so a banner is always exactly 5 lines regardless of how many characters you type. That is short enough for a README header and a code comment without dominating the file.
  • Everything is upper-cased before rendering: there is one glyph set, and lowercase input silently maps to the same capital letters. "Cleanor" and "CLEANOR" produce identical art.
  • The supported characters are A to Z, 0 to 9, the space, and the punctuation marks ! ? . , : - + = * / @ # and the parentheses ( ). Anything else, including the apostrophe, the underscore, the hyphenless dash characters, accented letters and emoji, falls back to a blank space glyph without any warning, so a word with an accent comes out with a hole in it.
  • Input is capped at 40 characters, and even that is too wide for most places you will paste it. A 40-character banner is over 200 columns wide at normal spacing, which will wrap and become unreadable in a terminal or a GitHub README. Keep it under about 12 characters.
  • The art only lines up in a monospace font. Paste it into a code block, a comment, or a terminal, never into a document body or a chat message that uses a proportional font, or the letters will shear apart.
Limits

What Text to ASCII Art does not do

The honest boundary, so you do not lose time finding it yourself.

  • One built-in 5-row font; no figlet fonts and no font selection.
  • Uppercase only, and no accented or non-Latin characters.
  • Maximum 40 characters of input.
  • No color, no image-to-ASCII conversion, and no output to a file.
At a glance

Who Text to ASCII Art is for

A quick way to understand who this helps, what it solves, and where it connects next.

Best fit

Developers making banners for READMEs and terminals.

Ideal for

Using the text to ascii art without installing anything or signing up.

FAQ

Common questions

Short answers for the questions people usually have before trying a utility like this.

Why did some of my characters come out blank?

Because they are not in the font. The glyph set covers A to Z, 0 to 9, the space, and fourteen punctuation marks: ! ? . , : - + = * / @ # ( ). Anything else, including apostrophes, underscores, quotes, accented letters, and emoji, is silently replaced with the blank-space glyph. There is no error message, so check the preview and substitute a supported character.

Can I use a different font, like the ones figlet has?

No. There is a single built-in 5-row font, chosen because it stays legible at a size that fits into a README or a code comment. Multi-font figlet-style output would need the font files bundled, and this tool deliberately has no dependencies.

What does the letter spacing option do?

It sets how many blank columns are inserted between glyphs: one for Tight, two for Normal, three for Wide. It does not change the glyphs themselves. Tight is worth using if your banner is long enough to be near the width limit of wherever you are pasting it.

Where does ASCII art like this break?

Anywhere that does not use a monospace font. In a Word document, an email body, a Slack message outside a code block, or an HTML paragraph, each character has a different width and the letters collapse into noise. Always wrap it in a code fence, a <pre> block, or a comment.

Is there a length limit?

Yes, 40 characters, but the practical limit is much lower. At normal spacing each letter is about 4 to 6 columns wide, so even 20 characters produces a banner over 100 columns wide, which wraps in most terminals and in the GitHub README view. Aim for a single short word.

Does lowercase input give lowercase letters?

No. The text is upper-cased before rendering because there is a single glyph set, so "Cleanor" and "CLEANOR" produce byte-identical art. That is worth knowing if you were hoping to mix cases for emphasis; the only levers you have are spacing and word choice.

How many lines will the banner be?

Always exactly five, no matter how long the word is. The font is five rows tall and letters are joined side by side rather than wrapped, so the banner grows horizontally only. That fixed height is what makes it safe to drop into a README without pushing the actual content off the first screen.

Is anything uploaded when I generate a banner?

No. The glyph table ships with the page and the banner is assembled in the browser as you type, so the word you enter never leaves your device and the tool keeps working with the network disconnected.

Is it free?

Yes, free with no account and no usage limit. There is nothing to install and no signup step between typing a word and copying the result.

Recommendations

You Might Also Like

Nearby tools from the catalog that fit the same job or workflow.

Cleanor app

Do it all on your device

Cleanor puts these tools in one app: compress and convert images, video, and audio, work with PDFs, and scan text right on your device. Plus free up storage and clear inbox clutter with Email Cleaner. Start with a free trial.

  • iPhone
  • Android
  • Macsoon
  • Windowssoon