How to turn Markdown into PowerPoint slides (Pandoc, Marp, or AI)

What a converter can and cannot do

Markdown describes structure, not layout. A heading says “this is a heading”; it says nothing about where on a slide it goes, how large it is or what sits beside it. Every route has to make those decisions, and the three below make them differently.

• A converter can map structure: headings to slide titles, bullets to bullets, tables to tables, code to monospaced text, images to pictures.
• A converter cannot decide what matters. If your Markdown has 40 bullets under one heading, a faithful conversion gives you one slide with 40 bullets.
• A converter keeps your wording exactly. That is a strength for documentation and a weakness for raw notes, which rarely read well on a slide.

Route 1: Pandoc

Pandoc is a free, open-source command-line tool that converts between dozens of document formats, PowerPoint among them. Once it is installed, a single command converts a file: “pandoc notes.md -o deck.pptx”.

• Slides: Pandoc picks a slide level, by default the highest heading level that is followed directly by content. So if every top-level heading is followed directly by a second-level heading, each second-level heading starts a slide; if any top-level heading has text directly beneath it, the slide level is 1. The “--slide-level” option sets this explicitly, and a horizontal rule also starts a new slide.
• Editable output. Titles, bullets and tables arrive as real PowerPoint text and tables.
• Speaker notes: wrap text in a “::: notes” block and Pandoc puts it in the slide's notes.
• Styling: the default look is plain. To use your company template, pass a reference file with “--reference-doc”, and Pandoc takes the layouts, fonts and colors from it.
• Limits: no charts, no judgment about what to cut, and long sections overflow the slide. Pandoc converts; it does not edit.

Pandoc suits documentation, internal training and anyone who wants an exact, editable conversion that can be scripted and repeated, for example as part of a build process.

Route 2: Marp

Marp is an open-source presentation toolkit built on Markdown. You write slides in a single file, separated by “---” lines, and control the look with themes written in CSS and short directives at the top of the file. Its VS Code extension shows a live preview, and Marp CLI exports to HTML, PDF and PowerPoint.

• Strong for developer talks, conference slides and anything with code: syntax highlighting, math and full control of the design in CSS.
• The PowerPoint export is image-based by default. Each slide arrives as a picture, so it looks right but the text cannot be edited in PowerPoint.
• Marp CLI also offers an experimental editable PowerPoint export (the “--pptx-editable” option), which needs LibreOffice installed. Results vary, so test it on your own deck.
• Presenter notes come from HTML comments in the Markdown, although the editable export leaves them out.
• Like Pandoc, it presents what you wrote. Structure and wording are up to you.

Marp suits people who want to stay in Markdown and present from HTML or PDF. If the goal is a .pptx that colleagues will edit, it is the weaker fit unless the editable mode works for your slides.

Route 3: rewrite it with an AI presentation tool

The third route treats the Markdown as source material rather than as slides. Much of the Markdown people want to present is AI-generated notes, research summaries or meeting write-ups: accurate, but organized as a document, with long bullets and no clear argument. A faithful conversion of that gives you a faithful copy of the problem.

An AI presentation tool reads the whole text and drafts a deck with its own structure: slide titles that state points, numbers pulled out as key figures or charts, and the detail moved to speaker notes. Arcdeck works this way, with two limits worth knowing. You paste the Markdown as text, because it does not accept .md file uploads, and it rewrites the content into a storyline of action titles rather than converting it line by line, so your exact wording will not survive. That is the point when you start from rough notes, and the wrong choice when you need an exact conversion.

When to use which

• Use Pandoc when you need an editable .pptx that matches your Markdown exactly, want your company template applied, or want to script the conversion.
• Use Marp when you present code or technical material, want full control of the design, and will present from HTML or PDF.
• Use an AI presentation tool when the Markdown is notes or a document rather than slides, the audience needs an argument rather than a transcript, and you are happy for the wording to change.
• Combine them if it helps: restructure the notes first, by hand or with AI, then convert the cleaned-up Markdown with Pandoc.

An exact conversion and a good presentation are different goals. Decide which one you need before you choose a tool.

Preparing Markdown for any route

• One heading per intended slide, with no more than five or six bullets beneath it.
• Long paragraphs turned into short points, or moved into notes.
• Tables checked for width: more than five or six columns rarely fits on a slide.
• Image paths that resolve from the folder where you run the conversion.
• Links that only work inside your notes app, such as Obsidian's double-bracket links, removed or replaced with plain text.

If the Markdown came from an AI assistant, read it once for accuracy before converting. A conversion carries every mistake straight onto the slides, and a rewrite can make a wrong number look more authoritative.