Markdown parsing
marked is a fast, low-level JavaScript markdown parser/compiler that converts CommonMark/GFM markdown to HTML, usable in browsers, Node.js, and the CLI.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Pick when you want a modern, actively maintained JS parser with a plugin ecosystem and near-drop-in API similar to marked.
Markdown parser, done right. 100% CommonMark support, extensions, syntax plugins & high speed
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Pick this for .NET applications; it's a full-featured CommonMark/GFM processor with a different ecosystem.
A fast, powerful, CommonMark compliant, extensible Markdown processor for .NET
Pick for PHP projects; solid CommonMark and GFM spec support with an extension API.
Highly-extensible PHP Markdown parser which fully supports the CommonMark and GFM specs.
Pick for JVM projects; provides CommonMark parsing with AST and rendering.
Java library for parsing and rendering CommonMark (Markdown)
Pick when you want markdown rendered directly to JSX/AST for React or other UI libs rather than an HTML string.
A very fast and versatile markdown toolchain. Output to AST, React, React Native, SolidJS, Vue, HTML, and more!
Pick for Rust projects; a fast, spec-compliant parser with GFM support and a clean API.
CommonMark + GFM compatible Markdown parser and renderer
Pick when you need a unified/plugin-based markdown pipeline with AST manipulation; it's more than a simple compiler.
markdown processor powered by plugins part of the @unifiedjs collective
Pick for C or Ruby bindings if you need a battle-tested markdown renderer; note it hasn't been updated in over a year.
The safe Markdown parser, reloaded.
Pick for Go projects; it's an extensible, CommonMark-compliant parser and a strong performer.
:trophy: A markdown parser written in Go. Easy to extend, standard(CommonMark) compliant, well structured.
Pick for Rust projects; a memory-efficient parser focused on CommonMark.
An efficient, reliable parser for CommonMark, a standard dialect of Markdown
Pick for Java projects needing source-level AST and support for multiple syntax extensions.
CommonMark/Markdown Java parser with source level AST. CommonMark 0.28, emulation of: pegdown, kramdown, markdown.pl, MultiMarkdown. With HTML to MD, MD to PDF, MD to DOCX conversion modules.
Pick for building your own parser pipeline; it's a low-level CommonMark tokenizer with a small footprint.
small, safe, and great commonmark (optionally gfm, mdx) compliant markdown parser
Pick for Rust projects if you want a parser+AST with extensions, from the unified ecosystem.
CommonMark compliant markdown parser in Rust with ASTs and extensions
Pick for C projects; a small, fast, SAX-like CommonMark parser.
C Markdown parser. Fast. SAX-like interface. Compliant to CommonMark specification.
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
Choose for legacy projects or if you need a mature plugin system; it's a capable JS parser but unmaintained.
Markdown parser, done right. Commonmark support, extensions, syntax plugins, high speed - all in one. Gulp and metalsmith plugins available. Used by Facebook, Docusaurus and many others! Use https://github.com/breakdance/breakdance for HTML-to-markdown conversion. Use https://github.com/jonschlinkert/markdown-toc to generate a table of contents.
A very old JS parser; only useful for maintaining legacy code that already relies on it.
A Markdown parser for javascript
Does the same job, but ships as an app. Useful to a person, not swappable into a codebase.
Pick when you need to render markdown inside React Native; it's a UI component, not a general parser.
React Native 100% compatible CommonMark renderer
Pick when you need a Svelte component to render markdown; it's an end-user component, not a parser library.
Svelte component to render markdown.
These projects were analysed and named marked among their alternatives. The relationship is not symmetric — how marked rates them is a separate judgement, made when marked is analysed in its own right.
calls marked “choose for a smaller, faster JavaScript Markdown-to-HTML parser with fewer plugin hooks and less CommonMark completeness than markdown-it.”
Markdown parser, done right. 100% CommonMark support, extensions, syntax plugins & high speed
calls marked “Choose for an actively maintained, high-speed JavaScript Markdown parser/compiler.”
A Markdown parser for javascript
calls marked “Choose if you want a fast, widely-used Markdown parser with direct HTML output and no React dependency.”
Markdown component for React
calls marked “Same markdown-parsing job for the JavaScript/Node ecosystem; choose it when your stack cannot use PHP.”
Better Markdown Parser in PHP
calls marked “Choose when you need a minimal, extremely fast Markdown parser without an AST or plugin system.”
markdown processor powered by plugins part of the @unifiedjs collective
calls marked “choose for JavaScript projects needing a lightweight, fast markdown compiler.”
:trophy: A markdown parser written in Go. Easy to extend, standard(CommonMark) compliant, well structured.