Best Mermaid integration for Slack: compare the options

Direct answer: The best Mermaid integration for Slack depends on what should happen after the first render. For a one-off PNG, Mermaid Preview is a straightforward Slack app: its Marketplace listing documents a slash command and says it does not retain diagram copies on its servers. For diagrams teammates will revise in Slack, Arialine stores editable Mermaid source and version history with the board, with thread edits linked to the request. If Git is the source of truth, Mermaid CLI can render repository-owned files in a pipeline. Mermaid Live Editor is useful for editing and exporting outside Slack; a Slack code block only shows the source.

Slack’s message-formatting documentation lists a code block as a text format; it does not document a Mermaid renderer. To put a rendered diagram in a channel, use a Slack app or post an image generated elsewhere.

What to compare

The first image is only one part of a diagram workflow. Before choosing a tool, answer four questions:

1. Where does the editable source live? In a Slack board, a repository, a browser, or nowhere the next editor can find?
2. What does the next edit look like? Does a teammate revise the same board, regenerate an image from source, or change a file and rebuild it?
3. What history survives? A new image is not automatically a record of which version came before it or why the diagram changed.
4. What is retained and billed? Distinguish a provider’s storage from the PNG Slack keeps, and compare workspace limits with any per-seat or infrastructure costs.

The comparison below uses vendor documentation, repositories, product pricing, and current Arialine implementation details checked on September 29, 2026. We verified Arialine’s board and plan claims against its live product pages and repository. Mermaid Preview, Mermaid Live Editor, and Mermaid CLI are assessed from their official documentation; this is not a paid head-to-head benchmark. Mermaid’s community integrations directory lists Mermaid Preview as its Slack integration. Installing a Slack app may require workspace approval; Slack’s Add Apps guide explains that process.

Quick comparison

Option	What appears in Slack	Source and follow-up edit	Retention and cost	Best fit
Slack code block	Mermaid text only	The message contains the source; edit the text or move it to a Mermaid renderer	No separate Mermaid app; Slack workspace policies still apply	Sharing syntax with teammates who can read it
Mermaid Live Editor	Nothing automatically; export and upload an image or Markdown yourself	Edit source in the browser, export PNG, SVG, or Markdown; Mermaid’s site says the Live Editor needs no account, and its history is stored in that browser	Mermaid documents browser-only history, with the last 30 edits viewable; no Slack team board	Authoring or checking a diagram outside Slack
Mermaid Preview	A PNG uploaded by the /mermaid Slack command	Its documented flow ends at the posted PNG. The repository README still lists editing a posted diagram as a wishlist item, so keep the source elsewhere and rerender after changes	Marketplace says source and generated PNGs are not persisted on its servers; the PNG posted to Slack remains subject to Slack retention. Mermaid Preview describes itself as a free, open-source Slack integration	A quick Slack image when the source is maintained elsewhere
Mermaid CLI in Git or CI	Whatever image or link your team’s pipeline uploads	Keep the .mmd file in Git and render outputs during a build; the team owns the change process and Slack posting	The CLI is open source; CI, hosting, and maintenance may have costs	Reproducible diagrams owned by a repository or release pipeline
Arialine	A PNG preview and interactive HTML file on a board	Source and versions stay associated with the board; request an edit in its thread. Applied changes link to the requesting Slack message	Free: 3 boards per workspace, 8 versions per board, 10 AI generations per workspace each day, and unlimited renders of valid pasted Mermaid. Team is $79 per workspace per month, plus tax, regardless of member count	A diagram the team discusses and revises in Slack

These options solve different jobs. Mermaid Preview and Arialine are the direct Slack apps in this comparison. Mermaid Live Editor and Mermaid CLI are source-editing or build workflows that can supply an artifact to Slack; they do not create a shared Slack board by themselves.

Test the second edit, not just the first image

Use the same small flow in every tool:

flowchart LR
    Client --> API
    API --> Database

Now ask a teammate to add a cache between the API and the database. That simple change shows who can update the diagram, where the change is recorded, and whether the old state remains available.

• Slack code block: The source is visible, but Slack still shows code. The author must edit the message or take the source to a renderer; there is no generated image or diagram history.
• Mermaid Live Editor: Edit the source in the browser and preview it immediately, then export a new image or Markdown file for Slack. Mermaid’s documentation says editor history lives in browser storage and exposes the last 30 edits; it is not a shared Slack revision trail.
• Mermaid Preview: Run /mermaid with the revised source to publish a PNG. The Marketplace listing documents rendering and upload, while the project README lists editing an already-posted diagram as a wishlist item. Keep your editable source in Git or another editor so you can reproduce the next image.
• Mermaid CLI: Commit the source change, run the renderer in CI, and post the new artifact through automation your team maintains. The official CLI converts Mermaid files to SVG, PNG, or PDF; the Slack posting step is custom work.
• Arialine: Mention @Arialine in the board thread with the change. In the default proposal mode, inspect the Mermaid and preview before choosing Apply; a channel in direct mode applies an addressed edit immediately. The new version retains the request link. That link explains which Slack message prompted the change; it does not certify the diagram as correct or formally approved.

This is a repeatable evaluation procedure, not a claim that every option was benchmarked in a customer workspace. For a fair trial, use source your team understands and check both the render and the revised Mermaid.

What each workflow gives up

Mermaid Preview: less state to maintain

Mermaid Preview’s official Slack listing describes a /mermaid command that accepts Mermaid, renders a PNG, and uploads it to a channel. Its data-retention statement says its servers do not retain the diagram or generated PNG. The Slack upload is still a copy in your workspace, and generating it still uses the app’s service; “not retained on the provider’s server” does not mean the source never leaves your environment.

This is a good fit when one readable picture is enough and your canonical source is already in a repository or document. It is less convenient when the Slack image itself must be updated with an in-thread edit or carry a version trail. The project’s README currently lists editing an already-posted diagram as a wishlist item. Treat the PNG as a snapshot, and keep the editable .mmd file where the team can find it.

Mermaid Live Editor: preview and export outside Slack

The Mermaid Live Editor guide describes editing Mermaid in a code panel, previewing the result, and exporting PNG, SVG, or Markdown. It also documents an edit history stored only in browser storage, with the last 30 edits available. That helps one person iterate, but it is not shared board history for a Slack team.

Use it when you want a fast browser preview or need to prepare an artifact manually. If the diagram changes later, keep the source in a repository or another shared location; a browser history on one device is not a substitute for team-owned source.

Mermaid CLI: source-controlled rendering

The official Mermaid CLI accepts a Mermaid definition and generates SVG, PNG, or PDF. A build can render a checked-in .mmd file every time the source changes, which makes Git the record of the diagram’s revisions. The trade-off is operational ownership: someone must maintain the runner, decide when to publish, and connect the output to Slack.

This is often the better fit when code review, repeatable builds, and repository history matter more than editing a diagram conversationally. It is a renderer, not a turnkey Slack board or thread-edit workflow.

Arialine: keep the edit in the Slack conversation

Arialine is designed for the case where the discussion and the diagram change together. A valid Mermaid paste is rendered as written without an AI model call; a plain-language description uses AI to draft the source. A board includes a PNG and interactive HTML, and teammates can ask for an edit in its Slack thread. In proposal mode, someone must review and apply the proposed edit; applied revisions become new versions associated with the request. Read the diagram review guide for the version and review workflow.

That convenience depends on retaining board source and history. Arialine’s pricing page lists the current Free limits and Team price. Workspace owners or admins can also run /arialine privacy save off to stop saving pasted Mermaid: valid source rendered as written is posted once without an editable board, while invalid source is reported without AI repair or retention. See the workspace privacy guide. With saving disabled, you give up the saved-board workflow for that pasted source.

Renderer support can differ by version. Arialine’s diagram-type gallery documents Mermaid 12 types plus ZenUML; Mermaid Preview’s Marketplace listing describes Mermaid.js support but does not state a renderer version. Test the exact source and diagram type you plan to use in each candidate.

Choose by workflow

• Choose Mermaid Preview when you need a PNG in Slack, already keep the source elsewhere, and prefer the publisher’s stated no-server-retention policy.
• Choose Arialine when people need to revise the same diagram from the Slack discussion and want its source and versions to stay with the board. Start on Free with one board.
• Choose Mermaid Live Editor when an individual needs an immediate browser preview and export, but Slack does not need to host a live editable board.
• Choose Mermaid CLI with Git or CI when the repository is the source of truth and your team is willing to maintain rendering and Slack posting.
• Use a code block when the audience needs the Mermaid source itself and a rendered image would not help.

If you are comparing only Slack apps, read the Arialine vs Mermaid Preview comparison for setup and data-retention details, then use the same Mermaid source in each app. The Slack Mermaid setup guide covers the Arialine steps; does Slack support Mermaid? explains what Slack displays natively.

FAQ

Does Slack render Mermaid code by itself?

No. Slack’s formatting guide lists code blocks as a message-formatting option; it does not document a built-in Mermaid renderer. Use an app that posts a rendered image or render Mermaid outside Slack and upload the result.

Does Mermaid Preview let teammates edit a posted diagram?

Its current Marketplace description documents a command that renders Mermaid and uploads a PNG. The project README lists editing a posted diagram as a wishlist item. Keep the source in a separate shared location and rerender after changing it.

Which Mermaid tool is best for a diagram that changes in Slack?

Arialine fits that workflow because it keeps the source on a board and associates applied versions with thread requests. If the diagram should remain owned by Git or should not be retained as an Arialine board, use a repository-based renderer such as Mermaid CLI instead.

Does Arialine send valid pasted Mermaid to AI?

No. Valid pasted Mermaid is validated and rendered without an AI call. AI is used for plain-language generation and may be used to repair invalid Mermaid when the workspace’s save and validation settings allow it.

Review date: September 29, 2026. Product behavior, app documentation, and prices can change; confirm current vendor pages and your workspace policies before standardizing on an integration.