⌘ K
GFM → AsciiDoc · headings · lists · blocks · links

Convert Markdown to AsciiDoc

Translate Markdown into AsciiDoc — the format used by Asciidoctor, GitLab, and many open-source documentation sites. Handles headings, lists, code blocks, links, images, and blockquotes.

Markdown → AsciiDoc
Input
109 B
12 lines
Output
117 B
13 lines
Status
ready
live
Ratio
1.07×
out/in
input · markdown
output · asciidoc
= Title

_Bold_ and _italic_ with `code`.

* One
* Two

https://example.com[Link]

[source,js]
----
const x = 1;
----
Quick Start

How to convert Markdown to AsciiDoc

Maps every Markdown structural element to its AsciiDoc counterpart in one pass — code blocks are preserved with [source,lang] attributes so syntax highlighting still works.

  1. 01

    Paste Markdown

    CommonMark or GFM source.

    Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.

    inputGFMmarkedCommonMarklive
    input · markdownmd · GFM
    # Title
    loaded · GFMGFM · ready
  2. 02

    Map syntax

    Headings → =, bold → *, italic → _.

    Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.

    mapsoft-breaksoptionsconfiglive
    rules · optionsadoc · live
    = Title
    options applied · livelive
  3. 03

    Wrap code

    Fenced code becomes [source,lang]\n---- blocks.

    The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.

    srcpreviewscoped CSSrenderstable
    code · renderedsrc · ready
    [source,js]
----
    rendered · liverendered
  4. 04

    Save .adoc

    Drop into your Asciidoctor / Antora pipeline.

    Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.

    exportclipboard.md.htmlblob
    ✓ · exported.adoc · done
    ✓ adoc
    shipped · ready to shipsuccess
Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Related toolsreSTOrg-modeTextileLaTeXPandocEditor
Use Cases

When to convert to AsciiDoc

Better tables, callouts, and includes than vanilla Markdown.

Antora docs

Author docs for the Antora SSG. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

GitLab repos

Render .adoc directly on GitLab. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

Tech books

AsciiDoc is the format of choice for many O'Reilly titles. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Includes

Migrate a doc set that needs cross-file includes. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

PDF / EPUB

Asciidoctor can output PDF and EPUB. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Open-source projects

Standard in many open-source ecosystems. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly
FAQ

Frequently asked questions

Markdown pipe tables pass through unchanged; AsciiDoc requires |=== syntax — convert manually for full coverage.
GFM > blockquotes become ____ delimited quotes. AsciiDoc admonition blocks (NOTE:, TIP:) aren't auto-generated.
Indentation is preserved; AsciiDoc uses repeated markers (**, ***) for nesting — review after conversion.
Yes — the output is valid AsciiDoc. Run asciidoctor file.adoc to render to HTML / PDF.
No. Conversion runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!