FIGlet fonts and text banner formatting
What is text to ASCII art?
FIGlet turns supported characters into text banners. Try the text generator to compare fonts with your own words.
Create ASCII text art
Choose a font and inspect the result before sharing.
Open the text generator and enter text to preview every bundled FIGlet font. Type or paste your text; Enter adds a line. Visible font previews update after a short pause. If a font lacks a character, use another result or edit the text. Filter fonts by name or scroll to compare styles. No Generate button is needed. Copy or download the result you prefer. Unlike the image tool, FIGlet uses font definitions rather than sampling pixels.
Find and compare fonts
Enter your text once in the text generator to apply it to every font. Filter fonts by name or scroll through the complete library. Previews generate near the viewport rather than loading every font at once. Each result has its own copy and download actions; unsupported characters produce a local warning instead of an incomplete banner. The text examples gallery also offers the full catalog with prepared sample text.
Open the full font galleryCopy and download a result
The font gallery and text generator both offer Copy, Copy as Markdown, TXT and PNG for each available preview. Copy as Markdown includes a fenced code block to preserve spacing. If clipboard access is denied, use the manual-copy text or download TXT.
PNG uses black text on white at 14 px monospace, at least 1.2 line spacing and 20 px padding. Preview the file before sharing. Font-specific output and PNG size limits still apply.
Already have a banner or diagram as text? Use ASCII to PNG to paste it directly, choose size, padding and a black or white background, and inspect the exact image before downloading.
In the text generator, choose an optional Terminal color to preview a single-color banner on black and enable each ASCII font's ANSI download. Terminal themes can change the palette. Copy, Markdown, TXT and PNG remain uncolored; non-ASCII fonts cannot use ANSI. Read the terminal viewing instructions before displaying the .ans file as data, never as a script.
Input, results and wrapping target are not saved automatically. An ordinary font link starts with Hello at 80 columns unless a gallery edit action carries text in this tab. The compact examples below reopen their published text and font at 80 columns, not your later edits. Copy or download your work before leaving.
How FIGlet fonts work
FIGlet fonts are stored in .flf (FIGlet Font) files. Each font file contains a header with metadata followed by character definitions that specify exactly how each letter, number, and symbol should be rendered.
- Character mapping: Each printable ASCII character (codes 32–126) is mapped to a multi-line pattern of sub-characters that form its visual representation.
- Height consistency: All characters within a font share the same height (number of lines), ensuring rows align properly when characters are placed side by side.
- Smushing rules: Each font declares "smushing" rules that let adjacent characters overlap or merge by one column, so letters sit closer together.
- Hardblank characters: Special placeholder characters ensure proper spacing within character designs without being collapsed by smushing rules.
The rendering process reads each character of your input, retrieves the corresponding multi-line pattern from the font file, and concatenates them horizontally. Where the font allows it, smushing merges the touching edges of neighboring letters.
Compare five FIGlet fonts
These five specimens render "Hello" with the installed FIGlet library: Horizontal Layout Default, Vertical Layout Default, Max Width 80. They are generated at build time, not drawn by hand.
Standard
_ _ _ _
| | | | ___| | | ___
| |_| |/ _ \ | |/ _ \
| _ | __/ | | (_) |
|_| |_|\___|_|_|\___/
Big
_ _ _ _
| | | | | | |
| |__| | ___| | | ___
| __ |/ _ \ | |/ _ \
| | | | __/ | | (_) |
|_| |_|\___|_|_|\___/
Slant
__ __ ____
/ / / /__ / / /___
/ /_/ / _ \/ / / __ \
/ __ / __/ / / /_/ /
/_/ /_/\___/_/_/\____/
Banner
# #
# # ###### # # ####
# # # # # # #
####### ##### # # # #
# # # # # # #
# # # # # # #
# # ###### ###### ###### ####
Shadow
| | | |
| | _ \ | | _ \
___ | __/ | | ( |
_| _| \___| _| _| \___/
Common uses
Typical places for a FIGlet banner:
Development and DevOps
- CLI welcome banners and startup messages for command-line tools
- README headers and project branding in Git repositories
- Code comment separators and section dividers
- Log output headers for distinguishing application phases
Creative and social
- Email signatures with personalized ASCII text branding
- Social media posts and profile decorations
- Forum signatures and message board headers
- Chat messages and Discord server announcements
Documentation and presentation
- Title pages for plain-text documentation
- Section headers in configuration files
- Decorative elements in terminal-based presentations
- Branding for retro-themed projects and games
Tips for readable banners
Character coverage depends on the FIGlet font. Unsupported or blank glyphs stop generation with a local, font-specific warning, including in all-font previews. Edit your text or explicitly choose another font; no characters are silently removed or transliterated. Supported accents are preserved. Input limit: 4,096 UTF-16 units. Some emoji and combined characters count as more than one unit. Each font result is limited to 200,000 output characters.
Every preview uses the font's default horizontal and vertical layout. In the text generator, choose a wrapping target from 20 to 200 columns; the default is 80 columns. This re-renders the banner, not its display size. A glyph wider than the target can still exceed it. The font gallery and prepared examples keep their 80-column target. Keep phrases short or add line breaks, then inspect the complete output before sharing.
- Choose the right font: Simpler fonts like Standard work best for longer text, while decorative fonts like Shadow or Block are better suited for short words or titles.
- Keep text short: Each letter is several columns wide, so long phrases wrap. One to three words per line is a practical starting point.
- Use a monospaced font for viewing: ASCII art relies on fixed-width characters to maintain alignment. View and share it in a monospaced font such as Courier, Consolas or your terminal's default font.
- Test across platforms: Different terminals and text editors may render characters slightly differently. Preview your art in the environment where it will be displayed.
- Mind the width: Standard terminal windows are typically 80 characters wide. Choose fonts and text lengths that fit within this limit to avoid line wrapping.
- Check non-ASCII input: Every FIGlet font covers printable ASCII. Accented letters work only in fonts that define them; the generator warns instead of dropping a character. Emoji are not FIGlet glyphs.
Create your own ASCII text art
Type a word or short phrase, compare the fonts, then copy the version you want.
Related Pages
- The ASCII Standard - Learn about the ASCII character encoding
- How It Works - Understand how ASCII art conversion works
- Examples Gallery - Browse ASCII art examples
- Frequently Asked Questions - Common questions about ASCII art
Questions about ASCII text art
What is a FIGlet font?
A FIGlet font defines multi-line character patterns. The text generator joins patterns for the characters that the selected font supports into a banner. Some fonts use Unicode output rather than only printable ASCII.
How do I convert text to ASCII art?
Open the text generator and enter text to preview every bundled FIGlet font. Type or paste your text; Enter adds a line. Visible font previews update after a short pause. If a font lacks a character, use another result or edit the text. Filter fonts by name or scroll to compare styles. No Generate button is needed. Copy or download the result you prefer.
Which FIGlet fonts can I compare here?
Compare the same input in Standard, Big, Slant, Banner and Shadow above. The text generator lets you search the rest of the bundled font library.
Can I use ASCII text art in my code or README?
Copy and TXT preserve characters, spaces and line breaks, not the receiving app's styling. Use a fenced code block in a README or chat, or a preformatted monospace text area. Keep leading/trailing spaces and disable wrapping. Unicode blocks, lines and emoji need suitable fonts and may occupy different widths.