ASCIIForge FAQ
Answers about image conversion, text banners, privacy and where ASCII output works best.
Is ASCIIForge free to use?
Yes. Every tool on ASCIIForge is free and runs entirely in your browser. No signup, no watermark, no usage limit.
Do you upload or store my images?
No. Image-to-ASCII conversion happens locally in your browser using the canvas API. Your photos never leave your device and are never sent to a server.
How do I use ASCII output on Discord?
Wrap the output in a triple-backtick code block so Discord renders it in monospace. Keep banners under about 40 characters wide so they do not wrap on mobile.
Can I put ASCII art in a GitHub README?
Yes. Paste the output inside a fenced code block in your README.md to preserve alignment. Aim for 80 to 100 columns for desktop readability.
Why do some images convert badly?
Low contrast, busy backgrounds, tiny subjects, and noisy photos produce muddy ASCII. Use a clear subject with strong light and dark separation, and crop tightly before converting.
What output width should I use?
For general sharing, 80 to 120 characters works well. Use 35 to 45 for Discord, 80 to 100 for README files, and 120 for terminal banners. Narrower output reads better on mobile.
Can I download or copy the ASCII art?
Yes. Both tools include copy-to-clipboard and TXT download. The image tool also exports PNG and SVG.
Which fonts work for the text banner tool?
The text generator uses FIGlet fonts such as Standard, Slant, and Doom, plus built-in block styles. If a FIGlet font cannot load, the tool falls back to a clean style automatically.