Website profiles · Technology insights · Alternatives

marp.app

Marp (also known as the Markdown Presentation Ecosystem) provides an intuitive experience for creating beautiful slide decks. You only have to focus on writing your story in a Markdown document.

No paid content found
Visit website
Profile views 15 Outbound visits 4 Normal
Marp Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
No paid content foundObserved
Registered
2018
Hosting
NetlifyInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Marp?

Marp is a Markdown-based presentation tool: you write a plain Markdown document, separate slides with ---, and Marp converts that file into a slide deck. Its format is based on CommonMark, so anyone comfortable with ordinary Markdown already knows most of what they need. The main addition is the horizontal rule as a page break.

What it does

  • Markdown-first authoring. Slides are just text, which makes them easy to version, diff and review in Git.
  • Directives and extended syntax. Per-deck settings such as theme, pagination, background colour or image can be declared in front matter or applied per slide. Marp also supports image sizing/positioning, math typesetting and auto-scaling content.
  • Themes. Three built-in themes — default, gaia and uncover — plus the option to write your own theme in plain CSS.
  • Export formats. Decks can be exported to HTML, PDF or PowerPoint. PDF and PowerPoint export relies on Chrome/Chromium.
  • Tooling. Marp for VS Code gives you editing and live preview inside the editor; Marp CLI converts files from the command line. The ecosystem is built on the Marpit framework and supports plugins.

Who it suits

If you are… Marp is a good fit because… Main trade-off
A developer or technical writer Slides live in the same repo as your docs and code Visual fine-tuning is CSS work, not drag-and-drop
Someone producing many similar decks Themes and directives keep styling consistent Unusual one-off layouts take more effort
A team reviewing content Markdown diffs are readable in pull requests Non-technical colleagues may prefer a graphical editor
A speaker needing a quick PDF Conversion to PDF/HTML is part of the workflow PDF/PowerPoint output depends on Chrome/Chromium

A concrete next step

Take a short document you already have — a README, a meeting agenda, a lecture outline — and paste it into Marp for VS Code, inserting --- where each slide should break. Add a small front-matter block to set the theme and page numbers, preview it, then export to PDF to see how it reads as a deck. That one pass will tell you quickly whether the Markdown workflow matches how you actually prepare presentations.

How do I create a slide deck in Markdown using Marp?

Write your deck as a single Markdown file and separate slides with a horizontal rule (---). Marp's format is based on CommonMark, so ordinary Markdown syntax — headings, bold, lists, images, code blocks — carries over directly; the ruler is the one addition that matters most.

A minimal deck looks like this:

# Slide 1
Some text

---

# Slide 2
More text

Adding structure and styling. Marp supports directives and extended syntax for things plain Markdown cannot express: math typesetting, image sizing and positioning, auto-scaling text, and per-deck settings. Directives go in a YAML front matter block at the top of the file or inside a slide, which is how you set a theme, page numbers, or a background:

---
theme: gaia
paginate: true
---

Three themes ship with the core engine: default, gaia, and uncover. You can adjust styling from within Markdown or write a full custom theme in plain CSS if the built-in look does not fit.

Choosing how to work. The ecosystem offers more than one entry point, and the right one depends on how you prefer to write:

Approach Good for Trade-off
Marp for VS Code Live preview while you type, theming inside the editor Requires VS Code as your editor
Marp CLI Scripted or automated conversion from a terminal No visual preview; you check output after rendering
Marp Core / Marpit Building your own tooling or plugins Developer-level effort

Exporting. When the deck is finished, Marp converts the Markdown into presentation-ready HTML, PDF, and PowerPoint files. The conversion is powered by Google Chrome / Chromium, so that browser engine needs to be available on the machine doing the export.

Start with the VS Code extension if you want to see slides update as you write, then switch to the CLI once you want repeatable exports. The official toolset lives at Marp and on GitHub, where the CLI, VS Code extension, and the underlying Marpit framework are published.

What export formats does Marp support for my presentations?

Marp exports finished Markdown decks to HTML, PDF, and PowerPoint. The page lists all three as direct outputs, with the conversion powered by Google Chrome or Chromium, so the rendering pipeline is browser-based rather than a separate office engine.

The practical differences matter more than the format list:

Format Best for Trade-off to expect
HTML Web sharing, embedding, links, self-contained viewing Not a native slide file; recipients open it in a browser
PDF Handouts, printing, fixed layout, email attachments Static; no presenter view or animations
PowerPoint Editing or presenting in PowerPoint, corporate handoff Converted output may need cleanup if you used custom CSS

A concrete scenario: if you keep your talk in Markdown and want a version for a projector plus a handout, write once and export PDF for the handout and HTML for the projector. If your organization requires .pptx files, export PowerPoint and expect to check theme fidelity, especially with custom CSS theming.

Next step: decide your delivery channel first. Browser-based sharing points to HTML; printing or archival points to PDF; collaborative editing in PowerPoint points to PPTX. For the toolset that performs these conversions, see Marp and its VS Code extension or CLI, both described on the same page.

How can I customize the look of my Marp slides with themes and CSS?

Marp gives you three levels of visual control: built-in themes, per-deck directives, and full CSS theming.

Start with the built-in themes

Marp Core ships with three themes: default, gaia, and uncover. You switch themes with a directive at the top of your Markdown file, so the fastest way to change the whole feel of a deck is a one-line edit rather than a redesign.

Tweak a single deck with directives

Directives let you adjust appearance without writing CSS. In the example on Marp, a deck sets theme: gaia, _class: lead, paginate: true, a background color, and a background image — all in the front-matter block before the first ---. This is the right layer for one-off changes: a title slide with a different background, page numbers turned on, or a lead class for centered text.

Write your own theme in plain CSS

When directives aren't enough, Marp lets you create a custom theme with plain CSS. Themes are registered and then selected by name, just like the built-ins, so a custom theme is reusable across every deck you write. This is the layer to reach for when you need brand colors, a specific font stack, or consistent styling across a team.

Approach Effort Best for
Built-in theme One directive line Quick restyling, personal decks
Directives A few lines per deck One-off layout and background changes
Custom CSS theme Write and register a theme Brand consistency, repeated reuse

A practical next step

Take one existing deck and add a front-matter block with theme: gaia and paginate: true. If that gets you close, stop there. If you find yourself repeating the same overrides in every deck, that repetition is the signal to promote them into a custom CSS theme instead.

If you'd rather stay inside your editor, Marp's ecosystem includes a VS Code extension for editing and previewing slide Markdown and custom theming, plus a CLI for converting decks. Both are documented through the Marp project.

What directives and extended syntax can I use in Marp for advanced slides?

Marp supports a set of directives and extended Markdown syntax that let you control slide structure, layout, and styling without leaving your Markdown document. The page evidence names directives, image syntax, math typesetting, and auto-scaling as the main extensions, and it shows a front-matter block using theme, _class, paginate, backgroundColor, and backgroundImage.

H3 Directives

Directives are written as key–value pairs, either in a YAML-style front-matter block at the top of the file for deck-wide settings, or inside a slide to affect that page. The example on the page places them between --- fences:

---
theme: gaia
_class: lead
paginate: true
backgroundColor: #fff
backgroundImage: url('...')
---
  • theme selects a built-in theme; the page names default, gaia, and uncover.
  • _class applies a CSS class to the slide, such as lead for a title-style opening slide.
  • paginate toggles page numbers.
  • backgroundColor and backgroundImage set the slide background, with the image given as a URL.

H3 Extended syntax

  • Page splitting with a horizontal ruler (---) is the core structural rule. Everything else is ordinary CommonMark.
  • Image syntax is extended for sizing and positioning; the page shows an example like ![bg left:40% 80%](...), which places an image as a background on the left at 40% width and 80% height.
  • Math typesetting is supported for formulas and technical content.
  • Auto-scaling adjusts content to fit the slide, which matters when you have more text than a fixed layout would hold.

H3 Themes and CSS

You can tweak styles with Markdown or write a full theme in plain CSS. That is the practical path when a built-in theme is close but not exact: start from default, gaia, or uncover, then override only the properties you need rather than designing from scratch.

H3 Choosing between directives and CSS

Need Use
Change theme, page numbers, or background for a deck or slide Directives
Place an image as a background or control its size Extended image syntax
Write formulas Math typesetting
Fit variable amounts of content Auto-scaling
Match a brand or adjust typography across all slides Custom CSS theme

A practical next step: write a short deck with only theme and paginate set, then add one background image and one formula. If the result still does not match your design, move that decision into a CSS theme instead of scattering per-slide directives.

For tooling around the format, the official ecosystem includes Marp itself, plus the VS Code extension and CLI mentioned on the page for editing, previewing, and converting decks.

How do I edit and preview Marp slides in Visual Studio Code?

Install the Marp for VS Code extension, open a Markdown file, and use the preview pane to see slides as you write. The extension is described in Marp's own toolset as letting you "edit and preview slide Markdown and custom theming within VS Code." So the workflow is: write in .md, watch the preview update, adjust, repeat.

A practical first file

Create a file such as deck.md and write ordinary Markdown, using --- on its own line to split slides:

---
theme: gaia
paginate: true
---

# Slide 1

Hello from Marp.

---

# Slide 2

- Write in Markdown
- Split pages with `---`

The --- block at the top is a directive block for deck-wide settings, not a slide break; the later --- separates slides. Marp's page notes that its format is based on CommonMark, so headings, lists, links, emphasis and code blocks behave as you already expect. The one difference worth remembering is that horizontal ruler.

Previewing and theming

Open the Markdown preview in VS Code to see rendered slides. Marp supplies three built-in themes — default, gaia and uncover — selectable through the theme directive. For a custom look, you can tweak styles with Markdown directives or write a theme in plain CSS; the VS Code extension is specifically noted as supporting custom theming in the editor, which makes it the easiest place to iterate on a design before exporting.

If you prefer a terminal-based route for conversion, Marp CLI is the companion tool. And the underlying engine exports to HTML, PDF and PowerPoint, powered by Chrome/Chromium, so the preview you approve in VS Code can become the file you hand out.

When this approach fits

Situation Why the VS Code route works
Developer talks, code-heavy decks Markdown and code fences are native; preview shows the result immediately
Slides that live in a Git repo Plain text diffs and reviews cleanly
Reusing one deck in several formats Same source can be exported to HTML, PDF or PowerPoint
Precise visual design control Built-in themes help, but expect to write CSS for anything distinctive

For a quick start, open VS Code, install the Marp extension, and paste the sample above into a new .md file. If you want the official toolset overview first, see Marp.

Related questions

More questions →
What is marp.app?
Marp (also known as the Markdown Presentation Ecosystem) provides an intuitive experience for creating beautiful slide decks. You only have to focus on writing your story in a Markdown document.
Does marp.app offer paid content?
Unknown.
What languages does marp.app support?
Primary language: English.
How can I visit marp.app?
Use the Visit website link to open the website in a new tab.
What are some alternatives to marp.app?
Related websites include zzzcode.ai, zyte.com, zustand.docs.pmnd.rs, zustand-demo.pmnd.rs, zulko.github.io, zmk.dev. Compare their features and pricing for your needs.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality.

Domain and Registration

Registered in 2018, this domain has about 8 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is CloudFlare, Inc., a widely used domain service provider. The domain uses the common .app extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Cloudflare Email Routing email service. DNSSEC is enabled, allowing validating resolvers to authenticate signed DNS data. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Referrer-Policy, clickjacking protection. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies Next.js, Tailwind CSS, Cloudflare, Netlify without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The meta description has 194 characters and may be shortened in search results. Twitter Card metadata is configured. The title has 37 characters, within a common display range. The observed directives allow indexing and link following. No Generator meta tag is publicly exposed.

Hosting and Email

DNSCloudflare
HostingNetlify
EmailCloudflare Email Routing
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.21.34.225

Registration details

RDAP / WHOIS

RegistrarCloudFlare, Inc.
Registered2018-05-08
Expires2027-05-08
Domain statusclient transfer prohibited
Nameserverskiki.ns.cloudflare.com、lewis.ns.cloudflare.com
DNSSECsigned

DNS records

DNS

TypeNameValueTTLPriority
Amarp.app104.21.34.225300—
Amarp.app172.67.165.238300—
AAAAmarp.app2606:4700:3037::6815:22e1300—
AAAAmarp.app2606:4700:3037::ac43:a5ee300—
MXmarp.approute1.mx.cloudflare.net30017
MXmarp.approute3.mx.cloudflare.net30032
MXmarp.approute2.mx.cloudflare.net30056
NSmarp.appkiki.ns.cloudflare.com86400—
NSmarp.applewis.ns.cloudflare.com86400—
TXTmarp.appv=spf1 include:_spf.mx.cloudflare.net ~all300—
DSmarp.app2371 13 2 915e48d8e7e87819e55ec34ccfb3e31204caa2645adfb4b0158ceede554884261800—
DMARC_dmarc.marp.appv=DMARC1; p=none; rua=mailto:[email protected]300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectmarp.app
IssuerGoogle Trust Services
Valid until2026-11-27T06:34 · Remaining when checked: 54 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
cache-controlpublic,max-age=0,must-revalidate
servercloudflare
strict-transport-securitymax-age=31536000
permissions-policyinterest-cohort=()

Identified technologies

Next.jsTailwind CSSCloudflareNetlify

Pages, Search and Sharing

Meta descriptionMarp (also known as the Markdown Presentation Ecosystem) provides an intuitive experience for creating beautiful slide decks. You only have to focus on writing your story in a Markdown document.
Canonical URLhttps://marp.app/
LanguageEnglish (default)
Twitter Cardsummary_large_image

No rules found

No sitemaps found

Recent Updates

  • Website images
  • Screenshots
  • Network details
  • Website Technologies
  • Pages and Search Information

User reviews (0)

  • No reviews yet.