⌘ K
GFM headings · emphasis · code · links → Org-mode

Convert Markdown to Emacs Org-mode

Translate Markdown to Org-mode syntax — headings (*), bold (*x*), italic (/x/), code blocks (#+BEGIN_SRC), and Org-style [[link][text]] references.

Markdown → Org
Input
85 B
8 lines
Output
85 B
8 lines
Status
ready
live
Ratio
1.00×
out/in
input · markdown
output · org-mode
* Title

/Bold/ and /italic/ with =code=.

- One
- Two

[[https://example.com][Link]]
Quick Start

How to convert Markdown to Org

Maps every Markdown structural element to its Org-mode counterpart in one pass — useful for moving notes into Emacs or feeding Pandoc-free Org pipelines.

  1. 01

    Paste Markdown

    CommonMark or GFM.

    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 structure

    Headings, emphasis, code, lists, and quotes are translated.

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

    mapsoft-breaksoptionsconfiglive
    rules · optionsorg · live
    * Title
    options applied · livelive
  3. 03

    Wrap code

    Fenced blocks become #+BEGIN_SRC / #+END_SRC.

    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
    #+BEGIN_SRC js
    rendered · liverendered
  4. 04

    Save .org

    Drop the file into your agenda or notes folder.

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

    exportclipboard.md.htmlblob
    ✓ · exported.org · done
    ✓ org
    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 toolsAsciiDocreSTTypstLaTeXPandocEditor
Use Cases

When to convert to Org

Move notes, tasks, and code into the Emacs ecosystem.

Emacs migration

Bring blog drafts into Emacs Org-mode. 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

Org-agenda tasks

Convert TODO checklists to Org agenda items. 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

Literate programs

Turn snippets into runnable Org Babel blocks. 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

Doc unification

Standardize team notes in one format. 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

Note archival

Long-term Org files outlast Markdown variants. 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

Org-publish

Feed Org Publish for blog generation. 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

Headings (# → *), bold (** → *), italic (* / _ → /…/), inline code (` → =…=), strikethrough (~~ → +…+), links, images, lists, blockquotes, and horizontal rules.
Markdown tables are passed through as-is; Org's pipe-table syntax mostly overlaps. Run M-x org-table-align in Emacs for cleanup.
Definition lists, footnotes, and task lists fall through unchanged. Use Pandoc for full coverage.
GitHub-style anchors aren't generated, but Org headings auto-anchor for internal links.
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!