Skip to main content
ASCII Art Generator

ASCII Divider Generator

Separate sections in a README, terminal transcript or plain-text note. Edit a labeled line or build a custom multi-line divider. The preview updates as you type, ready to copy without a Generate step.

Labeled and custom editors. Exact widths from 10-200 columns. No account needed.

Leave without saving your work?

Your input and artwork are not saved. Keep editing, or download the current result and check it before leaving.

The whole width, including ends and any comment markers.

One line of printable ASCII. Spaces are kept. Clear the label for an uninterrupted line.

10-200 columns for the whole line, including any end caps and comment markers. A label needs two padding spaces and at least one pattern character on each side.

Customize

Preview updates as you type. No Generate step needed.

Live preview

40 columns, 1 row

------------- Installation -------------

Plain text has no built-in heading semantics. Keep a normal heading too. In a README, use Copy as Markdown to preserve the divider in a fenced code block. PNG is black text on white, independent of the site theme.

Browse all 12 divider samples

Build a divider from three sections

Choose Custom divider to edit Start, Repeating content and End. The middle repeats across the available columns; Start and End stay intact. Empty ends are optional. A final partial repeat is cropped to keep the exact total width, but the ends are never truncated.

Each section can contain up to 64 printable ASCII columns and 8 rows. Every row within a section must have the same width, including trailing spaces. All non-empty sections must have the same row count as Repeating content. Add spaces to pad short rows or clear an end section you do not need. Invalid edits disable exports until corrected; they never copy an old result.

Explore the original divider samples gallery to open exact settings in either editor. Switching editor modes keeps your draft values. Loading a sample asks before replacing unexported custom work.

A 40-column installation divider

The initial example uses Installation, a total width of 40, and Dashes. The label takes 12 columns, its padding takes two, and the remaining 26 become 13 dashes on each side. Choose Copy as Markdown, then paste below a normal installation heading in your README and preview it.

Each character counts as one column in a monospace font. Labels may contain up to 196 printable ASCII characters if the chosen width has room; a label that does not fit is rejected, never truncated. Existing label spaces count too. An odd spare column goes on the right. Dash-dot restarts its pattern on each side and ends at the exact column limit. Clearing the label repeats the pattern across the entire width without padding. Left and right label positions keep three pattern characters before or after the label when there is room.

Keep the line intact where you paste it

Markdown may turn bare dashes or equals signs into a rule or heading. Copy as Markdown adds a fenced code block instead, so the literal characters remain visible. This is a visual separator, not a semantic heading. The Code comment option adds a prefix such as # or // inside the chosen width, so the line can sit in source code; check the result yourself, because comment-ending sequences in a label are not escaped.

Download TXT preserves the complete result without a final newline. Open it in a monospace editor with wrapping off. Shorten the width if it wraps in the destination. Labels cannot contain tabs, line breaks, emoji, accented letters or Unicode box-drawing characters. The Unicode line patterns need a font with box-drawing characters; choose an ASCII pattern for older terminals and plain email. Download PNG fixes the rendering as black text on white for destinations that collapse spaces. Need a frame around several lines instead? Use the ASCII box generator. For large letter banners, use the FIGlet text generator.

Formatting runs in your browser. This tool does not save the label or custom sections, or put them in links or analytics. Export work before leaving. Site analytics, storage and hosting are separate. See the README and CLI examples for related publishing workflows.