CLI tool
marp-team/marp avatar
marp-team/marp

Marp: the entrance repository of the Markdown presentation ecosystem

The entrance repository of Markdown presentation ecosystem

12,752 stars307 forksTypeScriptMIT

At a glance

What is it?
Marp turns plain Markdown into slide decks, but marp-team/marp itself is a landing page and coordination repo, not the converter. Here is what lives where, how to install the actual tooling, and where the ecosystem stops.
Who is it for?
Adopt Marp if you want slides that live in the same Markdown files and Git history as your notes, and install Marp CLI through npm or the VS Code extension rather than cloning marp-team/marp. Do not adopt it if you need a hosted editor, a slide DSL with animation primitives, or a package you can import from this repository, because package.json marks it private and contains no runtime code.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 8 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • marp-team/marp12,752 ★ · +201
Star history
Repository2026-09-222026-11-15
marp-team/marp12.6k12.8k

201 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What marp-team/marp actually is, and who ends up reading it

The repository describes itself in package.json as "The entrance repository of Markdown presentation ecosystem", and that phrase is the most accurate summary available. It is not the converter. The README states plainly that the project is spread over many repos so each one keeps a limited scope, and that this repo places the website in /website. The top-level listing backs that up: a website directory, a netlify.toml, a yarn workspace entry pointing at website, and a TypeScript build config, with no slide rendering code at the root.

So the audience splits. A developer evaluating Marp for a team will land here first, follow a link to Marp CLI or Marp Core, and never clone this repository. Someone who wants to contribute to marp.app itself is the actual user of this repo. If you came here expecting a library to install, you are one hop early. The README's Marp family table is the map: Marpit as the framework, Marp Core as the converter core with built-in themes, Marp CLI as the command line interface to HTML, PDF, PPTX and images, and Marp for VS Code as the editor integration.

The package.json confirms the scope from the other direction. The name is @marp-team/marp, the private flag is set, and the workspaces array contains exactly one entry: website. There is no published artifact, no bin field, and no main field. Anything you install from the Marp family comes from a different repository, and the npm badges in the README are the pointers to those packages rather than to this one.

The scripts in package.json tell the same story. There is a website script that runs the dev server for the workspace, plus format, format:write, lint:js, check:format and check:ts. Every one of them serves the website or the repository's own hygiene. None of them builds a slide deck, which is the clearest evidence that this repo is not where the rendering happens.

How the pieces fit: Marpit, Marp Core, CLI and the editor extension

The README gives a layered family rather than a single binary. Marpit is described as "the skinny framework for creating slide deck from Markdown", which suggests the parsing and slide-splitting rules live at the bottom. Marp Core sits above it as "the core of Marp converter with practical features and built-in themes", so the themes people search for are shipped there, not in this repository. Marp CLI wraps Marp Core and Marpit to convert into HTML, PDF, PPTX and image files. Marp for VS Code is the preview surface inside the editor.

That layering has a practical consequence worth stating: the output formats are a CLI concern. If you cannot find a rendering option, it is unlikely to be defined in marp-team/marp. The README also separates the family into Framework/Core, Apps and Integrations, then hides a third group behind a details block labelled "See outdated/inactive projects". That group contains Marp Web, Marp React and Marp Vue, with Marp Web badged as a tech demo. The React and Vue renderer components are filed under inactive, so treating them as supported integration paths would be a misread of the project's own labelling. The classic Marp app is referred to as a gravesite.

The split also decides where a bug report belongs. A theme rendering oddly is a Marp Core issue. A PDF export failing in a container is a Marp CLI issue. A preview pane not refreshing is a VS Code extension issue. None of those are fixed in this repository, and the README's structure is an explicit invitation to route questions to the right place. The discussion forum linked at the top is the shared channel across the family, which is the one piece of coordination this repo does provide beyond the website. The awesome list is the second, and it is where the ecosystem's third-party material is collected rather than in the README itself.

Getting the tooling: where the install steps actually live

This is the point where the entrance repo stops being useful. The README contains no install command for anything. It links @marp-team/marp-cli, @marp-team/marp-core and @marp-team/marpit as npm badges, and marp-team.marp-vscode as a Marketplace badge, but it never writes out a package manager invocation. The marp-cli repository is where the README says the CLI interface lives, so installation instructions belong to that project's documentation, not to this one.

What can be stated from this repository is the shape of the decision. There are two supported entry points: a command line tool published as @marp-team/marp-cli, and an editor extension published as marp-team.marp-vscode. The README lists the CLI as converting into HTML, PDF, PPTX and image files, so it is the path for producing artifacts. The extension is described as previewing the slide deck written in Marp Markdown, so it is the path for writing. A team that needs PDFs in CI needs the CLI. Someone drafting slides all day needs the extension. Neither is installed from marp-team/marp.

The repository does show its own development commands, and they are worth reading precisely because they are not slide commands. From package.json, the format script runs prettier across css, js, jsx, json, md, mdx, scss, ts, tsx, yaml and yml files, and the website script delegates to the @marp-team/marp-website workspace. A contributor running those is working on marp.app, not on a presentation. If you find yourself looking for a render command in this repository, you have followed the wrong link.

One practical consequence: any version number, flag or output option you read about should be checked against the marp-cli README, because nothing in this repository pins or documents them. The npm badges here resolve to the current published versions, which is the only version information this repo offers.

Where Marp is the wrong tool

Marp is a Markdown-to-slides pipeline, and the trade-off is that anything outside Markdown's reach becomes awkward. Fine-grained animation, timeline control, embedded interactive widgets and speaker-note tooling with live timing are not what the README advertises; the listed outputs are HTML, PDF, PPTX and images. If your deck depends on motion, a JavaScript presentation framework will fight you less.

There is a second, quieter limitation in this specific repository. Because marp-team/marp's package.json is marked private and the repository holds the website, its dependency set is editor and build tooling: eslint, prettier, typescript, lage, @types/node. A security scanner pointed at this repo reports on the website toolchain, not on the code that parses your Markdown. Teams that require a vulnerability review of the thing they ship will need to review @marp-team/marp-cli and @marp-team/marp-core separately.

A third case is worth naming because it catches people late. The README files Marp React and Marp Vue under outdated or inactive projects, so a team planning to embed a Marp renderer inside a React or Vue application is planning against a component the project itself no longer counts as current. The maintained surfaces are the CLI and the VS Code extension. If your architecture needs a renderer as a library, this is the point to stop and reconsider.

Finally, if you need a hosted collaborative editor where non-technical colleagues edit slides in a browser, Marp Web exists but is labelled a tech demo, so it is not a substitute for a product. The README also points to a gravesite repository for the classic Marp app, which is a reminder that the ecosystem has already retired one desktop incarnation.

Marp against Slidev, and what the difference really is

The most common comparison question puts Marp next to Slidev. The honest answer is that they are not the same kind of project, and the README does not discuss Slidev at all. Marp's stated position is Markdown first: plain Markdown in, HTML, PDF, PPTX or images out, with the conversion handled by a CLI. The deck is a document that happens to render as slides.

Slidev takes the other direction and treats the deck as a web application, which is why animation and layout control are natural there and why a build step is unavoidable. If your slides need to be diffed, reviewed in a pull request and exported to PDF by a script, Marp's model fits. If your slides are essentially a front end with routing and transitions, it does not.

The inactive Marp React and Marp Vue components hint that the team tried the component-renderer route and stopped; the maintained path is CLI and editor preview, not embedding a renderer in your app. That is a design boundary rather than a missing feature, and it is the clearest signal in the README about what Marp intends to be. It also means the comparison is not really Marp versus Slidev as products. It is a document pipeline versus an application framework, and the right question is which one your review process can absorb.

Maintenance, licence and the cost of upgrading

The repository is not archived, and the last push was on 2026-11-02. That is recent enough to call the project maintained, but note what is being maintained here: the website and the monorepo scaffolding. Release cadence for the parts you install is published per package through the npm badges in the README, and the repository has no published GitHub releases, which is consistent with its package.json being marked private.

Licensing is MIT according to package.json and the LICENSE file at the root. The README does not state whether every sub-project uses the same licence, so if you vendor Marp Core or Marp CLI, read that package's own licence file rather than assuming this one transfers.

Upgrade cost is the usual monorepo story. The root pins TypeScript ^4.9.4, eslint ^8.30.0 and @types/node ~18.11.18, and the workspace is yarn-based with lage orchestrating checks. A contributor updating the website inherits that toolchain and has to keep prettier, eslint and the TypeScript version in step, because the format and lint scripts run across css, js, jsx, json, md, mdx, scss, ts, tsx, yaml and yml. A user of Marp CLI inherits whatever the CLI package declares, which this repository does not show. The two upgrade paths never intersect, which is the main reason the entrance repo can move without affecting your build.

The resolutions block pinning json5 is a small reminder that the website workspace has its own dependency tree to keep aligned with the root, and that a contributor's first pull request is more likely to touch formatting than slide logic. The .nvmrc file at the root is the other signal: Node version is pinned for contributors, not for consumers of the published packages.

Editorial conclusion

Adopt Marp if you want slides that live in the same Markdown files and Git history as your notes, and install Marp CLI through npm or the VS Code extension rather than cloning marp-team/marp. Do not adopt it if you need a hosted editor, a slide DSL with animation primitives, or a package you can import from this repository, because package.json marks it private and contains no runtime code. Verify first that the CLI subcommand and output format you need are named in the marp-cli README, and check the licence file of whichever package you actually depend on.

Frequently asked questions

What does Marp do?

Marp is an ecosystem for writing presentations in plain Markdown. The conversion is handled by Marp CLI, which the README describes as converting Marp Core or Marpit output into HTML, PDF, PPTX and image files.

What is the Marp format?

Marp decks are Markdown files. The README does not document the directive syntax itself; it points to Marpit as the framework for creating a slide deck from Markdown and to Marp Core as the converter core with built-in themes.

What is the purpose of Marp?

Its purpose is to let you write a presentation with plain Markdown, then convert it. The marp-team/marp repository is the entrance to that ecosystem and hosts the website, while the actual conversion lives in Marp CLI and Marp Core.

What are the key differences between Slidev and Marp?

The README does not mention Slidev, so it makes no comparison. What it does state is Marp's scope: Markdown in, with HTML, PDF, PPTX and images as CLI outputs.

Official sources

  1. Issues
  2. License: MIT
  3. marp-team/marp on GitHub
  4. Project website
  5. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/marp-team-marp.svg)](https://hysenlabs.com/projects/marp-team-marp)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/marp-team-marp.svg)](https://hysenlabs.com/projects/marp-team-marp)

Was this useful?