Which is Better Markdown Parsing Libraries?
marked vs unified vs remark-parse vs markdown-it vs remark
1 Year
markedunifiedremark-parsemarkdown-itremarkSimilar Packages:
What's Markdown Parsing Libraries?

Markdown parsing libraries are essential tools in web development for converting Markdown text into HTML. They facilitate the rendering of Markdown content in web applications, enabling developers to provide rich text formatting options without the complexities of HTML. Each library offers unique features, performance characteristics, and extensibility options, catering to different use cases and developer preferences.

NPM Package Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
marked11,719,74033,205953 kB179 hours agoMIT
unified10,495,2534,486146 kB05 months agoMIT
remark-parse8,840,6377,70319.5 kB1a year agoMIT
markdown-it6,888,94618,317767 kB218 months agoMIT
remark1,974,1047,70315.7 kB1a year agoMIT
Feature Comparison: marked vs unified vs remark-parse vs markdown-it vs remark

Performance

  • marked: marked is known for its high performance and low memory footprint. It is optimized for speed, making it suitable for applications that need to render Markdown content quickly without compromising on performance.
  • unified: unified's performance can vary based on the complexity of the transformations applied. It is designed for flexibility and extensibility, which may introduce some overhead, but it excels in scenarios requiring multiple content transformations.
  • remark-parse: remark-parse is efficient for parsing Markdown into an AST, but its performance will depend on how the AST is used in subsequent processing. It is optimized for parsing rather than rendering, making it suitable for analysis and manipulation tasks.
  • markdown-it: markdown-it is designed for speed and efficiency, making it one of the fastest Markdown parsers available. It utilizes a streaming approach, allowing it to handle large documents with minimal overhead, which is crucial for performance-sensitive applications.
  • remark: remark is slightly slower due to its extensive processing capabilities, but it provides a robust framework for transforming Markdown content. It is best used in scenarios where performance is less critical than the need for advanced processing features.

Extensibility

  • marked: marked is relatively straightforward and does not have a built-in plugin system. However, it can be extended through custom implementations, making it less flexible compared to other libraries.
  • unified: unified is inherently extensible, allowing developers to create custom processors and integrate various plugins for different content types. This modular approach makes it suitable for projects requiring diverse content handling.
  • remark-parse: remark-parse is a part of the remark ecosystem and is designed to be used with other remark plugins. While it focuses on parsing, it can be easily integrated into a larger processing pipeline with other remark tools.
  • markdown-it: markdown-it offers a rich plugin architecture that allows developers to extend its functionality easily. You can add custom rules and plugins to enhance the parsing process, making it highly adaptable to specific needs.
  • remark: remark is highly extensible, with a vast ecosystem of plugins available for various transformations and enhancements. It allows for custom processing pipelines, making it ideal for complex Markdown manipulation.

Learning Curve

  • marked: marked is easy to learn and implement, making it a great choice for beginners. Its simple API allows developers to get started quickly with minimal setup.
  • unified: unified has a higher learning curve due to its modular architecture and the need to understand how to work with different processors and plugins. It is best suited for experienced developers looking for flexibility.
  • remark-parse: remark-parse is straightforward to use for parsing Markdown into an AST, but understanding how to manipulate the AST may require additional learning. It is best suited for developers familiar with abstract syntax trees.
  • markdown-it: markdown-it has a moderate learning curve, especially for developers familiar with Markdown. Its API is straightforward, but leveraging its plugin system may require additional understanding of its architecture.
  • remark: remark has a steeper learning curve due to its comprehensive nature and the need to understand its plugin architecture. However, it offers powerful capabilities for those willing to invest the time to learn.

Output Format

  • marked: marked also outputs HTML from Markdown and is designed for simplicity. It provides a clean and straightforward conversion process, making it easy to integrate into applications.
  • unified: unified can output various formats, including HTML, Markdown, and more, depending on the processors used in the pipeline. This versatility makes it suitable for projects that require different output formats.
  • remark-parse: remark-parse outputs an abstract syntax tree (AST) from Markdown, which can be further processed or transformed. It is not designed for direct HTML output, making it suitable for analysis and manipulation tasks.
  • markdown-it: markdown-it outputs HTML directly from Markdown, making it ideal for applications that require immediate rendering of Markdown content. It supports various options for customizing the output HTML.
  • remark: remark allows for outputting Markdown as an AST, which can then be transformed into various formats, including HTML. This flexibility is beneficial for projects that require multiple output formats.

Community and Support

  • marked: marked is popular and has a solid user base, providing ample resources and community support, although it may not have as extensive a plugin ecosystem as markdown-it.
  • unified: unified has a growing community and a strong ecosystem of plugins, making it a good choice for developers looking for support and extensibility in their content processing workflows.
  • remark-parse: remark-parse benefits from the larger remark community, providing access to a wealth of resources and plugins for Markdown processing.
  • markdown-it: markdown-it has a strong community and is widely used in various projects, ensuring good support and a wealth of plugins and resources available for developers.
  • remark: remark boasts a vibrant community with numerous plugins and extensive documentation, making it a great choice for developers looking for support and resources.
How to Choose: marked vs unified vs remark-parse vs markdown-it vs remark
  • marked: Select marked if you require a simple and efficient Markdown parser that is easy to use and has a straightforward API. It is suitable for projects where speed is essential, and you need a quick solution without the overhead of additional features.
  • unified: Choose unified if you want a versatile framework that allows you to work with different types of content transformations, including Markdown. It is ideal for projects that require a modular approach to content processing and the ability to integrate various plugins for different formats.
  • remark-parse: Use remark-parse if you need a specialized parser that focuses solely on converting Markdown to an abstract syntax tree (AST). This is beneficial for projects that require further processing or analysis of Markdown content before rendering it to HTML.
  • markdown-it: Choose markdown-it if you need a fast, extensible, and customizable Markdown parser that supports a wide range of plugins and features. It is ideal for applications where performance is critical and you want to leverage a rich ecosystem of plugins for additional functionality.
  • remark: Opt for remark if you are looking for a comprehensive Markdown processing toolchain that allows for extensive transformations and plugins. It is perfect for projects that need to manipulate Markdown content beyond simple parsing, offering a powerful ecosystem for custom processing.
README for marked

Marked

npm install size downloads github actions snyk

  • ⚡ built for speed
  • ⬇️ low-level compiler for parsing markdown without caching or blocking for long periods of time
  • ⚖️ light-weight while implementing all markdown features from the supported flavors & specifications
  • 🌐 works in a browser, on a server, or from a command line interface (CLI)

Demo

Checkout the demo page to see marked in action ⛹️

Docs

Our documentation pages are also rendered using marked 💯

Also read about:

Compatibility

Node.js: Only current and LTS Node.js versions are supported. End of life Node.js versions may become incompatible with Marked at any point in time.

Browser: Not IE11 :)

Installation

CLI:

npm install -g marked

In-browser:

npm install marked

Usage

Warning: 🚨 Marked does not sanitize the output HTML. Please use a sanitize library, like DOMPurify (recommended), sanitize-html or insane on the output HTML! 🚨

DOMPurify.sanitize(marked.parse(`<img src="x" onerror="alert('not happening')">`));

CLI

# Example with stdin input
$ marked -o hello.html
hello world
^D
$ cat hello.html
<p>hello world</p>
# Print all options
$ marked --help

Browser

<!doctype html>
<html>
<head>
  <meta charset="utf-8"/>
  <title>Marked in the browser</title>
</head>
<body>
  <div id="content"></div>
  <script src="https://cdn.jsdelivr.net/npm/marked/marked.min.js"></script>
  <script>
    document.getElementById('content').innerHTML =
      marked.parse('# Marked in the browser\n\nRendered by **marked**.');
  </script>
</body>
</html>

or import esm module

<script type="module">
  import { marked } from "https://cdn.jsdelivr.net/npm/marked/lib/marked.esm.js";
  document.getElementById('content').innerHTML =
    marked.parse('# Marked in the browser\n\nRendered by **marked**.');
</script>

License

Copyright (c) 2011-2022, Christopher Jeffrey. (MIT License)