Gerador de QR Code

How letters become block art

An ASCII art generator turns ordinary text into oversized letters drawn out of smaller characters. The trick is a bitmap font: each letter is stored as a small grid of "on" and "off" cells, and the generator paints every "on" cell with a block character and leaves the rest blank. Lay those grids side by side, one row at a time, and a word emerges as a banner you can paste into a terminal, a code comment, a README, or a chat message — anywhere a monospaced font keeps the columns aligned.

This tool ships three hand-built fonts, each a different size and personality, and renders them instantly as you type. The output uses the solid block character █ for the filled cells, which reads as crisp dark shapes on a light background or glowing letters on a dark one.

The three fonts, and when to use each

Every character is uppercased before rendering — the bundled fonts cover A–Z, the digits 0–9, and a handful of marks (! ? . - _). Input is capped at 30 characters so a single banner stays a reasonable width.

A worked example

Type HI with the Standard font and the generator stacks six rows. For the letter H it reads a 6-row bitmap where the left and right columns are filled and the middle row connects them, producing the familiar two uprights with a crossbar; I is a narrow stack. Side by side you get something like:

• ██ ██ ███
• ██ ██ ██
• █████ ██
• ██ ██ ██
• ██ ██ ██
• ██ ██ ███

Each letter's grid is padded with a space column so neighbouring letters don't collide. The exact glyphs are illustrative here, but the principle is exact: row by row, cell by cell, the block font is assembled into the word.

The width limit explained

The Width Limit slider (40 to 200 characters, default 120) caps how wide each output line may be. The generator builds the full banner, then trims every row to that width. This is what stops a long word from overflowing a narrow terminal or a fixed-width comment block. If your banner looks cut off on the right, raise the slider; if it wraps awkwardly when pasted, lower it to match your target width.

Real use cases

• Code comments and section headers. A block banner above a function or config section is far easier to spot when scrolling than a one-line comment.
• README and CLI splash screens. Many command-line tools print an ASCII logo on startup; this is a quick way to draft one.
• Server message-of-the-day (MOTD). Greet anyone who SSHes in with a project name in big letters.
• Plain-text contexts. Emails, forum posts, and chat channels that strip formatting still render ASCII art perfectly, because it's just text.

Practical tips

• Use the "All Fonts Preview" button to render your text in Standard, Small, and Banner at once, then copy whichever fits best.
• Always paste into a monospaced font. ASCII art only aligns when every character is the same width. In a proportional font the columns drift and the picture falls apart — keep it in code blocks, terminals, or <pre> tags.
• Keep words short. The Standard font is wide; one or two words per banner reads best. Stack multiple banners for multi-word titles.
• Mind comment delimiters. If you paste a banner into a block comment, make sure none of the block characters clash with your language's comment syntax.

Common mistakes

• Expecting lowercase to look different. The fonts are uppercase-only, so mixed-case input renders all caps.
• Pasting where whitespace gets collapsed. Some editors and chat apps trim trailing spaces or tabs, which can shear the right edge of the art. Test in the destination before relying on it.

Privacy

The fonts and rendering live entirely in your browser. The text you type is converted to ASCII art on your device and copied to your clipboard locally — nothing is uploaded or stored on a server.