Comparison

Variant vs Marp

Marp turns markdown files into slides, which makes it a natural fit for developers who keep everything in git. Variant keeps the code-first idea but uses HTML and CSS as the slide format, adds a visual editor, and gives AI agents MCP tools to create and edit decks.

Quick take: choose Marp when plain markdown files in your repo are the priority. Choose Variant when an AI agent should generate and keep editing the deck, and you want a visual canvas plus design control beyond what markdown allows.

1Agent drafts

Claude Code or Codex creates slides through MCP.

2You refine

Edit the exact HTML and CSS on a visual canvas.

3Export cleanly

Ship HTML, PDF, or PPTX when the deck is ready.

#Both are code-first

Marp and Variant both reject the idea that slides must live in a binary editor format. Marp's answer is markdown with directives, rendered to HTML or PDF by the Marp CLI or VS Code extension. Variant's answer is real HTML and CSS per slide, with a visual canvas and an MCP server on top.

That format choice drives everything else. Markdown is faster to type and diff. HTML is more expressive and gives an agent or a designer full control over layout.

#Choose Marp when

You want slides as plain text files in your repository, reviewed in pull requests like any other change. You're comfortable with theme CSS for styling, your decks are mostly headings, bullets, and code, and you want a free open-source tool with no account.

#Choose Variant when

You want Claude Code or Codex to generate the deck and keep editing it afterward. Variant's MCP tools let an agent read a slide, change one element, render a preview to check the result, and export to HTML, PDF, or PPTX — and a teammate can fix layout on the visual canvas without touching the source.

#What about agents writing Marp markdown?

Claude Code can write Marp markdown — it's a popular workflow and it works. The limitation is the loop after the first draft: the agent can't see a rendered slide, can't edit one element without rewriting the section, and there's no visual editor to hand off to. Variant's MCP tools exist to close that loop.

NeedVariantMarp
Source formatHTML and CSS per slideMarkdown with directives
Visual editingCanvas and inspector built inNone — edit text, re-render
Agent workflowMCP tools: previews, targeted edits, exportsAgents can write the markdown
Design controlAnything HTML and CSS can doThemes plus CSS, within markdown's structure
Lives in gitDeck versions in Variant; export HTML to commitPlain text files, ideal for git
ExportsHTML, PDF, PPTXHTML, PDF, PPTX via CLI
PriceFree tier, paid plansFree and open source

#Common questions

Is Marp free while Variant is paid?

Marp is open source and completely free. Variant has a free tier for solo decks, with paid plans for teams and hosted agent features. If budget decides it and markdown slides cover your needs, Marp is a fine answer.

Can Claude Code make slides with Marp?

Yes. Marp decks are markdown, so any coding agent can write them. The difference shows up after the first draft: with Marp the agent edits text blind, while Variant's MCP tools let it preview rendered slides and make targeted element-level edits.

Can I keep Variant decks in version control?

Variant keeps deck versions internally and you can export a self-contained HTML file to commit. If the requirement is that the deck source itself lives in your repo as plain text, Marp or Slidev fit that better.