Движок 3D-трансформаций и анимации
Tool guide
You type a short line and get the same words spelled out in characters, using a figlet-style font template. Headings like this go into GitHub README files, into the greeting of a CLI tool, into a server motd banner or at the top of a config file where you want a visual divider without images. Everything renders in the page, and the output stays plain text you can paste into any editor. See also: make ASCII art from a photo, animate the letters frame by frame, play the banner as typed output.
Render the project name, copy the result and wrap it in a fenced code block. Without the fence Markdown collapses the runs of spaces and the shape falls apart. Keep an eye on width: anything past 80 columns wraps awkwardly on narrow screens, so long names are better split across two renders.
Figlet-style fonts define glyphs for the Latin alphabet, digits and common punctuation. Characters outside that set have no template and are passed through or dropped. Transliterate names written in other scripts, and keep the original spelling for the caption next to the artwork.
Standard is the widest and most readable, roughly six lines tall, and suits a main heading. Slant keeps that width but leans the letters for a more dynamic look. Small is about half the height and much narrower, which is what you want inside a code comment or a cramped console.
No. The glow, scanlines, typing effect and 3D rotation are CSS applied to the preview only. What lands on your clipboard is characters and line breaks. If you need the animated look itself, screen-record it or build the motion in the frame-by-frame ASCII editor instead.
Almost always a proportional font. In a word processor, an email client or a chat message without a code block, characters have different widths and the columns drift. Paste into a monospaced context or a code block and the shape survives.
There is no hard cap, but each letter takes 6-10 columns, so a ten-letter word in Standard already overflows the classic 80-column terminal. In practice, one short word or an acronym works best; longer phrases should be rendered line by line.
Before: LINUX
After: _ ___ _ _ _ ___ __ | | |_ _| \ | | | | \ \/ / | | | || \| | | | |\ / | |___ | || |\ | |_| |/ \ |_____|___|_| \_|\___//_/\_\
Before: DB
After: # ____ ____ # | _ \| __ ) # | | | | _ \ # |____/|____/ — database settings block
Your rating and feedback help decide what to improve next.