Website profiles · Technology insights · Alternatives

mermaid-ascii.art

No paid content found
Visit website
Profile views 9 Outbound visits 1 Normal
Mermaid ASCII Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
No paid content foundObserved
Registered
2024
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Mermaid ASCII?

Mermaid ASCII converts Mermaid diagram code into plain-text ASCII diagrams. You paste or type Mermaid syntax into the "Mermaid Code" box, and the "ASCII Output" panel renders the diagram using ordinary characters instead of SVG or canvas graphics. The page itself shows version 1.6.1 and controls for horizontal and vertical padding plus an option to use extended characters.

Who it is for

  • Developers who want a diagram inside a terminal, code comment, README, or plain-text file where images cannot render.
  • People reviewing Mermaid syntax who want a quick visual check without opening a full diagramming tool.
  • Anyone working over SSH or in a chat tool that strips images but preserves text.

What you can try

The page includes several examples: nested subgraphs, a labelled arrow, styled text, and a sequence diagram. These are worth opening first because they show how much structure survives the conversion. Flowcharts and sequence diagrams are the main use case; heavily styled or very wide graphs are where ASCII output tends to get cramped, since character width and line wrapping constrain the layout.

Practical trade-offs

Mermaid ASCII Standard Mermaid rendering
Output Plain text characters Vector or raster image
Works in terminals Yes No
Fine visual styling Limited Full
Fits wide/complex graphs Can wrap awkwardly Scales better

Beyond the web page

The same project is available as a Git repository, and the page lists two alternatives: a cURL request that posts Mermaid code to the service, and running it locally with Go via go run main.go -f test.mermaid. The CLI route is the better choice if you want to generate diagrams in a build script or keep diagram source offline.

If you are new to Mermaid, start with the "Labelled Arrow" example to confirm the basic flow, then try the sequence diagram example to see how much detail the ASCII output preserves. Use the padding controls if the result looks too tight or too spread out.

How do I convert Mermaid code to ASCII art?

Paste your Mermaid code into the Mermaid Code box on Mermaid ASCII and read the result in the ASCII Output panel, which you can copy. The page also exposes padding controls (xPadding, yPadding) and a "Use extended characters" toggle, so you can tune spacing and choose between plain and richer box-drawing glyphs.

It handles the diagram types the page demonstrates: flowcharts with nested subgraphs, labelled arrows, styled text, and sequence diagrams. If your diagram renders as a mess, it is usually one of three things — labels too long for the column width, deep nesting, or characters the plain-ASCII mode can't draw. Widen the padding, shorten labels, or switch on extended characters.

When this approach fits

  • Terminal and plain-text output: README files, code comments, CLI help text, man pages, commit messages, chat messages, or anywhere Markdown renderers won't run Mermaid.
  • Reviewing diagrams in a diff: ASCII art survives git diff, email and plain-text review tools that would otherwise show raw Mermaid source.
  • Quick sanity check: converting is a fast way to see whether your Mermaid syntax is structurally sound before committing it.

Trade-offs: ASCII output is fixed-width and monospaced, so wide or heavily branched graphs get unwieldy, and it is a poor fit for anything you want to publish as a rendered image or interactive diagram.

Other ways to run the same converter

The site points to its Git repository for alternatives, useful if you want this in a script or CI step rather than a browser tab:

  • cURL: post your diagram as a mermaid field, e.g. curl https://mermaid-ascii.art -d mermaid="graph LR\nABC --> DEF".
  • Go CLI: clone the repo, then run it against a file, e.g. go run main.go -f test.mermaid.

For most one-off conversions, the web page is the shortest path. Reach for the CLI when you need repeatable, offline or automated conversion — for instance generating ASCII diagrams as part of a docs build. If you'd rather keep diagrams as source and render them elsewhere, Mermaid documents the syntax itself, and GitHub renders Mermaid in Markdown files directly.

Can I use Mermaid ASCII from the command line or via API?

Yes. Mermaid ASCII is not only a browser tool; the same project behind Mermaid ASCII offers two non-browser routes: an HTTP request that returns ASCII output, and a local Go program you run yourself.

The web page lists these under "Alternative Usage Methods." It shows a cURL request posting Mermaid source to the site, and a Go workflow that clones the GitHub repository, enters the directory, and runs go run main.go -f test.mermaid. The page also shows the format of the request body: a mermaid field containing the diagram definition, with newlines escaped.

Which route fits your situation

Route Best for Trade-off
cURL / HTTP request Quick checks, scripts, CI steps that can call an external service Depends on network access and on the remote service being available
Local Go program Offline use, private diagrams, repeatable local runs Requires a Go toolchain and cloning the repository
Browser editor Trying examples and seeing output immediately Manual copy/paste; less suited to automation

A concrete example

Suppose you keep architecture diagrams in a repository and want an ASCII version in a pull request comment. A script can send the Mermaid text to the endpoint and paste the returned ASCII into the comment. If the diagrams are confidential, run the Go version locally instead so the source never leaves your machine.

Decision criterion

Choose the HTTP route when convenience matters more than control, and the local Go route when the diagram content is sensitive or the environment has no reliable outbound access. For a first test, copy one of the page's examples — such as a simple graph LR with two nodes and an arrow — and run it through both routes to confirm the output matches before wiring either into a larger workflow.

What types of Mermaid diagrams does Mermaid ASCII support?

Mermaid ASCII converts Mermaid diagram source into plain-text ASCII or extended-character output, so you can read a diagram in terminals, code comments, plain-text docs and diffs where rendered graphics won't appear. The page lists examples for nested subgraphs, labelled arrows, styled text and sequence diagrams, so those are the diagram types and features you can expect it to handle. These examples also show that it preserves labels and styling cues rather than reducing everything to bare boxes and lines.

Its settings reinforce that text-first purpose. You can adjust xPadding and yPadding, and toggle Use extended characters. Extended characters give smoother lines and corners; turning them off gives a more portable but blockier result. That trade-off matters if the output will be pasted into systems that mangle Unicode or if you need maximum compatibility.

Besides the web page, the project's repository offers two alternative routes: a cURL request that posts Mermaid code to the site, and a Go CLI you can clone and run locally. The CLI is the better fit for repeated or automated conversion, while the web page suits quick one-off checks.

For a concrete test, start with a small graph LR and a labelled edge, then try a sequence diagram and a nested subgraph. If the ASCII output stays aligned and readable, it will likely serve your terminal or documentation use case; if not, enable extended characters or increase padding before giving up on it.

Next step: open Mermaid ASCII and paste one of your own diagrams, beginning with the simplest one you need to support.

How can I customize the ASCII output, such as padding or extended characters?

Mermaid ASCII exposes a small set of controls right above the code/output panes: xPadding, yPadding, and a "Use extended characters" toggle. Those are the levers for customizing the ASCII rendering of a Mermaid graph.

What each control does

Control Effect When to use it
xPadding Horizontal space added around the graph Widen gaps so boxes or labels don't visually collide
yPadding Vertical space added around the graph Give breathing room above/below, useful in terminals or docs blocks
Use extended characters Switches to box-drawing glyphs instead of plain ASCII Prettier diagrams in modern terminals; turn it off if the target font or system mangles Unicode

Practical workflow

  1. Paste your Mermaid code into the Mermaid Code pane.
  2. Adjust xPadding/yPadding and toggle extended characters.
  3. Watch the ASCII Output pane update, then hit Copy to take the result elsewhere.

A concrete scenario: if you're dropping a diagram into a plain-text README or an email that may be viewed in a monospaced font with limited Unicode support, keep extended characters off and bump padding slightly so arrows and labels stay legible. If you're rendering inside a modern terminal or a code block on a site that handles box-drawing glyphs, turn extended characters on for cleaner lines.

Note that padding changes spacing, not layout logic — it won't fix a diagram that's too wide for your target width. For that, simplify the graph structure itself.

Going beyond the web page

The page also lists alternative ways to run the same tool from the underlying Git repository, including a cURL request and running it via Go on the command line. Those are worth knowing if you want to script diagram generation rather than paste-and-copy by hand. The source project lives at GitHub under the mermaid-ascii repository.

If you only need a one-off diagram, the web page is the fastest path. If you're generating many diagrams or want this in a build pipeline, the CLI route is the better fit.

Is Mermaid ASCII free and open source?

Yes. Mermaid ASCII is free to use, and the underlying code is open source under the AlexanderGrooff/mermaid-ascii GitHub repository.

What that means in practice

  • Free: The website itself is a browser-based converter — paste Mermaid code, get ASCII output. The page shows no pricing, subscription or payment signals.
  • Open source: The page references the public GitHub repo and documents CLI usage (git clone, go run main.go -f test.mermaid), so you can inspect, modify, and self-host the tool.

Why that combination matters

Need Free web tool Open-source repo
Quick one-off diagram Yes — paste and copy Overkill
CI pipeline / scripted output Not ideal Yes — CLI
Offline or air-gapped use No Yes — self-host
Custom formatting or patches No Yes — fork it

Next step: If you only need a diagram now, paste your Mermaid code into the site and copy the ASCII output. If you need repeatable or automated output (docs builds, terminals, CI), clone the repo and run the CLI instead — that's the path the page itself documents.

Related questions

More questions →
What is Mermaid ASCII?

Mermaid ASCII is a tool that converts Mermaid diagram code into ASCII text diagrams. You paste or type Mermaid syntax into the "Mermaid Code" area, and it renders the result as plain-text ASCII in the "ASCII Output" area. The current version shown on the site is v1.6.1. It is useful when you need a diagram that survives in environments where images or rendered SVG won't display — plain text files, terminal output, code comments, or chat messages.

How it works

The tool takes standard Mermaid graph definitions and lays them out using ASCII characters. You control the spacing with two settings visible on the page:

  • xPadding (shown as 5) — horizontal spacing between elements
  • yPadding (shown as 3) — vertical spacing between elements
  • Use extended characters — a toggle for richer box-drawing characters instead of basic ASCII

The page includes several worked examples you can inspect directly:

  • Nested subgraphs
  • Labelled arrows
  • Styled text
  • Sequence diagrams

Each example pairs the Mermaid source with its ASCII output, so you can see exactly how a given construct translates before writing your own.

Using the web interface

  1. Enter Mermaid code in the Mermaid Code field. For example: graph LR\nABC --> DEF
  2. Adjust xPadding and yPadding if the default spacing doesn't suit your target width.
  3. Toggle Use extended characters if you want box-drawing glyphs rather than plain ASCII.
  4. Read the result in ASCII Output and use the Copy button to take it elsewhere.

The expected result is a text rendering of your graph that preserves direction and labels, sized according to your padding settings.

Alternative usage methods

The site notes that the same Git repository (AlexanderGrooff/mermaid-ascii) supports other ways to generate output.

cURL request — send Mermaid code to the service and get ASCII back:

curl https://mermaid-ascii.art -d mermaid="graph LR\nABC --> DEF"

Run the Golang tool locally — clone the repo and run it against a file:

git clone https://github.com/AlexanderGrooff/mermaid-ascii
cd mermaid-ascii
go run main.go -f test.mermaid

The local route needs a Go toolchain installed and a .mermaid file containing your diagram. The cURL route needs no local setup but depends on the hosted service being reachable.

When to choose it

Use Mermaid ASCII when the destination can only hold plain text — README files rendered without image support, terminal logs, commit messages, or documentation that must stay diff-friendly. If your target renders Mermaid natively or accepts images, a normal Mermaid renderer will give you cleaner output with less manual spacing tuning. The padding controls and extended-character toggle exist precisely because ASCII layout is width-sensitive, so expect to adjust them for narrow terminals or fixed-width documents.

Which Mermaid Diagram Types and Features Does Mermaid ASCII Support?

Mermaid ASCII (v1.6.1) converts Mermaid diagram code into ASCII art. Based on the examples shown on the site, it supports flowcharts with nested subgraphs, labelled arrows, and styled text, as well as sequence diagrams. If your diagram relies on features beyond these, the tool may not render them correctly.

Diagram Types and Features with Confirmed Support

The site provides four worked examples, each demonstrating a specific capability:

Example Feature demonstrated What it shows
Example 1 Nested Subgraphs Flowcharts where subgraphs are contained inside other subgraphs
Example 2 Labelled Arrow Edges with text labels (e.g. `A -->
Example 3 Styled Text Text styling applied within diagram nodes
Example 4 Sequence Diagram Sequence diagrams, not just graph-type diagrams

The cURL example on the page also uses a basic flowchart (graph LR\nABC --> DEF), confirming left-to-right graph direction is supported.

Flowcharts and graphs

Flowchart syntax (graph LR, graph TD, etc.) is the primary use case. The examples cover:

  • Nested subgraphs — subgraphs within subgraphs render as nested ASCII boxes.
  • Labelled arrows — edge labels appear alongside the connecting lines.
  • Styled text — styled node text is preserved in the ASCII output.

Sequence diagrams

Example 4 confirms sequence diagrams are supported, so the tool is not limited to node-and-edge graphs.

Rendering Options That Affect Output

The interface exposes a few settings that change how the ASCII output looks:

  • xPadding (shown as 5) — horizontal spacing.
  • yPadding (shown as 3) — vertical spacing.
  • Use extended characters — a toggle for using extended ASCII/Unicode box-drawing characters instead of plain characters.

These affect layout and appearance, not which diagram types are accepted.

Alternative Ways to Generate the Same Output

The page lists two additional methods beyond the web interface, both using the same GitHub repository (AlexanderGrooff/mermaid-ascii):

cURL request:

curl https://mermaid-ascii.art -d mermaid="graph LR\nABC --> DEF"

Run locally with Go:

git clone https://github.com/AlexanderGrooff/mermaid-ascii
cd mermaid-ascii
go run main.go -f test.mermaid

The Go CLI method reads from a file (test.mermaid), which is useful for batch conversion or offline use.

What to Check Before Relying on It

The page only demonstrates the four features above. If your diagram uses other Mermaid constructs — such as class diagrams, state diagrams, Gantt charts, or pie charts — there is no evidence on the site that these are supported. For those cases, test your specific diagram code in the tool first, or use the Go CLI locally to check the output before committing to it in a document or README.

How to Convert Mermaid Code to ASCII Output on mermaid-ascii.art

Paste your Mermaid diagram code into the Mermaid Code box on mermaid-ascii.art, and the ASCII Output panel updates with the text version of your diagram. You can then use the Copy button to grab the result. The site runs Mermaid ASCII v1.6.1 and works for anyone who needs a plain-text diagram for a terminal, README, code comment, or chat message where rendered graphics won't show.

Steps to convert a diagram

  1. Open mermaid-ascii.art in your browser.
  2. In the Mermaid Code area, type or paste valid Mermaid syntax. For example:
    graph LR
    ABC --> DEF
    
  3. Watch the ASCII Output area. It regenerates as you edit, showing the diagram drawn with text characters.
  4. Adjust the layout controls if the default spacing looks cramped or too loose:
    • xPadding — horizontal spacing (shown as 5 by default in the interface).
    • yPadding — vertical spacing (shown as 3 by default).
    • Use extended characters — toggle for richer box-drawing glyphs instead of basic ASCII.
  5. Click Copy to put the ASCII output on your clipboard.

The expected result is a block of monospaced text that mirrors your graph's structure and labels, ready to paste anywhere plain text is accepted.

What kinds of diagrams you can try

The site ships with several examples you can load or imitate:

  • Example 1: Nested Subgraphs — diagrams with grouped nodes.
  • Example 2: Labelled Arrow — edges that carry text labels.
  • Example 3: Styled Text — nodes using styling syntax.
  • Example 4: Sequence Diagram — message-passing diagrams, not just flowcharts.

If your diagram doesn't render as expected, the most common cause is invalid Mermaid syntax rather than a problem with the converter. Check that arrows, node brackets, and subgraph blocks are closed correctly.

Alternative ways to generate the same output

The same Git repository (AlexanderGrooff/mermaid-ascii) offers two non-browser methods.

cURL request — send Mermaid code to the endpoint and get ASCII back:

curl https://mermaid-ascii.art -d mermaid="graph LR\nABC --> DEF"

Run the Go program locally — clone the repo and run it against a file:

git clone https://github.com/AlexanderGrooff/mermaid-ascii
cd mermaid-ascii
go run main.go -f test.mermaid

Use the web interface when you want a quick visual check and manual copy. Use cURL or the CLI when you need to script the conversion or run it inside a build pipeline.

Choosing between the options

Method Best for Requires
Web interface One-off conversions, tweaking padding visually A browser
cURL Automating conversion in scripts Network access to the endpoint
Go CLI Local, offline, or CI use Go toolchain and the cloned repo

If you only need to convert a diagram occasionally, the web page is the fastest path. If the conversion is part of a repeatable process, the cURL or CLI route avoids manual copying.

What alternative ways does Mermaid ASCII offer to generate ASCII graphs?

Mermaid ASCII (v1.6.1) offers two alternative ways to generate ASCII graphs besides its web interface: a cURL request to https://mermaid-ascii.art and running the Go program from the AlexanderGrooff/mermaid-ascii repository in your CLI. Both are listed on the site under "Alternative Usage Methods" and are useful when you want to generate diagrams from a script, terminal, or automated workflow instead of pasting code into the browser.

Option 1: cURL request

Send your Mermaid code directly to the site as a POST parameter.

curl https://mermaid-ascii.art -d mermaid="graph LR\nABC --> DEF"
  • Input: the mermaid parameter containing your Mermaid definition (here a simple left-to-right graph with two nodes).
  • Action: cURL posts the data to the Mermaid ASCII endpoint.
  • Expected result: the ASCII rendering of the graph is returned as the response, which you can print in a terminal or pipe into a file.

This is the quickest option if you only need the output and don't want to install anything. It fits shell scripts, CI steps, or one-off conversions.

Option 2: Run the Go program in your CLI

Clone the repository and run the Go program locally.

git clone https://github.com/AlexanderGrooff/mermaid-ascii
cd mermaid-ascii
go run main.go -f test.mermaid
  • Input: a .mermaid file (the example uses test.mermaid) passed with the -f flag.
  • Action: go run main.go executes the program, reading the diagram definition from the file.
  • Expected result: the ASCII graph is printed to your terminal.

This option requires a Go toolchain and a local clone, but it keeps everything offline and lets you version your diagram files alongside your code.

Which one to choose

cURL request Go CLI
Setup None beyond cURL Go installed + repo cloned
Input Inline mermaid parameter .mermaid file via -f
Best for Quick conversions, scripts, CI Offline use, file-based workflows

If you just need a one-off conversion or want to call it from a script, use the cURL request. If you prefer working with diagram files locally and having the tool available offline, clone the repository and run the Go program.

The web interface itself also exposes settings such as xPadding, yPadding, and an option to use extended characters, and it includes examples like nested subgraphs, labelled arrows, styled text, and sequence diagrams — so you can preview a diagram there first, then switch to either alternative method once the output looks right.

Website Overview

Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The domain has about 2 years of registration history; its current configuration provides more context than age alone. The registrar is NameCheap, Inc., a widely used domain service provider. Registration contact information is publicly available through RDAP. The domain uses the common .art extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed. The lowest observed DNS TTL is 300 seconds.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, Referrer-Policy, Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray, via response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No homepage meta description was detected, leaving snippet selection more dependent on page text. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 13 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.21.64.186

Registration details

RDAP / WHOIS

RegistrarNameCheap, Inc.
Registered2024-10-03
Expires2026-10-03
Domain statusclient transfer prohibited
Nameserversdeborah.ns.cloudflare.com、kayden.ns.cloudflare.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Amermaid-ascii.art104.21.64.186300—
Amermaid-ascii.art172.67.154.80300—
AAAAmermaid-ascii.art2606:4700:3031::ac43:9a50300—
AAAAmermaid-ascii.art2606:4700:3034::6815:40ba300—
NSmermaid-ascii.artdeborah.ns.cloudflare.com86400—
NSmermaid-ascii.artkayden.ns.cloudflare.com86400—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectmermaid-ascii.art
IssuerGoogle Trust Services
Valid until2026-12-11T03:07 · Remaining when checked: 68 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
servercloudflare
strict-transport-securitymax-age=63072000
x-frame-optionsSAMEORIGIN
x-content-type-optionsnosniff

Identified technologies

Cloudflare

Pages, Search and Sharing

Meta descriptionNot detected
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

No rules found

No sitemaps found

Recent Updates

  • Website images
  • Screenshots
  • Network details
  • Website Technologies
  • Pages and Search Information
  • TLS and certificates

User reviews (0)

  • No reviews yet.