⌘ K
GFM → Jira wiki · h1. · {code:lang} · [text|url] · bq.

Convert Markdown to Jira wiki markup

Reformat Markdown for Atlassian Jira tickets — h1./h2. headings, {code:lang} blocks, [text|url] links, {{inline}} code, and bq. blockquotes.

Markdown → Jira
Input
192 B
15 lines
Output
200 B
15 lines
Status
ready
live
Ratio
1.04×
out/in
input · markdown
output · jira wiki
h1. Bug report

_Bold_ and _italic_ description.

* repro step one
* repro step two
* expected vs actual

{{inline}} snippet:

{code:js}
console.log("hi");
{code}

See [docs|https://example.com/docs].
Quick Start

How to convert Markdown for Jira

Jira wiki markup predates Markdown and uses different sigils — h1. for headings, {code} for fences, [text|url] for links. This converter remaps every common form in one pass.

  1. 01

    Paste Markdown

    From your PR, RFC, or bug report draft.

    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 headings

    # Title → h1. Title; ## → h2. and so on.

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

    headingsoft-breaksoptionsconfiglive
    fix · optionsjira · live
    h1. Title
    options applied · livelive
  3. 03

    Map inline + code

    [text](url) → [text|url]; `x` → {{x}}; fences become {code:lang} 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.

    mappreviewscoped CSSrenderstable
    out · renderedwiki · ready
    {code:js}…{code}
    rendered · liverendered
  4. 04

    Paste into Jira

    Use the wiki markup toggle in the comment box.

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

    exportclipboard.md.htmlblob
    OK · exportedjira · done
    shipped
    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 toolsConfluenceSlackNotionHTMLBBCodeEditor
Use Cases

When to convert for Jira

Bug reports, RFCs, release notes, audit trails.

Bug reports

Convert reproducible-bug write-ups for the issue tracker. 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

RFC tickets

Mirror RFC content from Markdown into a Jira epic. 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

Release notes

Repost engineering release notes onto release tickets. 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

Support escalations

Tidy customer-facing reports for engineering tickets. 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

Sprint planning

Convert sprint outlines to Jira-friendly markup. 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

Bulk import

Pre-format issues before bulk import via the Jira API. 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

Only with the Wiki Markup editor toggle, or when imported via the legacy REST API. The new editor uses ADF — copy / paste should still render most of it.
Markdown tables are left as-is. Jira's wiki syntax uses || header || cell ||. Convert by hand if you need exact tables.
Yes — ![alt](url) becomes !url!, the Jira inline image macro.
Yes — [text](url) becomes [text|url], the Jira link macro.
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!