Jira Markdown to ADF Converter
Atlassian Document Format (ADF) is the JSON structure Jira Cloud uses for rich text. Wiring up the Jira REST API means you can’t send Markdown — you need valid ADF. Paste your Markdown to get ADF JSON for a description field, or convert an ADF payload back into readable Markdown. Everything runs in your browser.
Runs entirely in your browser — nothing you paste is uploaded or stored.
This tool fixes the symptom. BugScreen fixes the cause.
Hand-formatting Jira tickets is busywork. BugScreen’s mobile SDKs capture a screenshot and device context, then file a fully-formatted Jira issue (in ADF) automatically — no copy-paste.
Start freeHow it works
Pick a direction
Choose Markdown → ADF to generate Jira-ready JSON, or ADF → Markdown to read an ADF payload as plain Markdown.
Paste your content
Type or paste into the left pane. Conversion runs live as you type — there is no button to press.
Copy the result
Copy the output straight into a Jira REST API call (the description field) or into your editor.
Frequently asked questions
What is Atlassian Document Format (ADF)?
ADF is the JSON document format Jira Cloud uses for rich-text fields like issue descriptions and comments. Instead of HTML or Markdown, the Jira Cloud REST API expects a structured tree of nodes shaped like { "type": "doc", "version": 1, "content": [ … ] }. This tool builds that tree from Markdown for you.
Does Jira accept Markdown?
The Jira Cloud REST API does not accept Markdown for rich-text fields — it expects ADF JSON. So when you create or update issues programmatically, you convert your Markdown to ADF first, which is exactly what this converter does.
Is my data sent anywhere?
No. The conversion runs entirely in your browser using client-side JavaScript. Nothing you paste is uploaded, logged, or stored — once the page has loaded it even works offline.
Which Markdown features are supported?
Headings, bold, italic, inline code, strikethrough, links, ordered and nested lists, fenced code blocks with a language, blockquotes, horizontal rules, and hard line breaks — the common GitHub-flavored Markdown you would use in a bug report. Unknown or unsupported nodes are skipped gracefully rather than breaking the conversion.
Can it convert ADF back to Markdown?
Yes. Flip the direction toggle and paste ADF JSON to get Markdown back — handy for reading an issue description pulled from the Jira API. Some formatting is normalized (for example, bold always returns as **…**), so a round-trip produces clean, canonical Markdown.
Try BugScreen on your app.
Screenshot → ticket in your issue tracker, with logs and device context. Free to start — no credit card.
Get started