react-markdown vs markdown-to-jsx vs remark-react vs react-markdown-editor-lite
Markdown Rendering and Editing in React Applications
react-markdownmarkdown-to-jsxremark-reactreact-markdown-editor-liteSimilar Packages:

Markdown Rendering and Editing in React Applications

markdown-to-jsx, react-markdown, react-markdown-editor-lite, and remark-react are all npm packages that help integrate Markdown processing into React applications, but they serve different purposes and use distinct underlying technologies. markdown-to-jsx and react-markdown are focused on rendering Markdown as React components, with the former using a custom parser and the latter built on the unified/remark ecosystem. react-markdown-editor-lite is a full-featured WYSIWYG Markdown editor component that includes both editing and preview capabilities. remark-react is a legacy renderer for the remark ecosystem that converts Markdown ASTs to React elements but has been deprecated in favor of more modern alternatives like react-markdown.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
react-markdown13,117,47115,53952.6 kB3a year agoMIT
markdown-to-jsx3,949,7772,3424.74 MB312 days agoMIT
remark-react11,804524567 B0a year ago-
react-markdown-editor-lite01,122494 kB542 months agoMIT

Markdown in React: Rendering vs. Editing vs. Legacy Tools

When you need to display or edit Markdown in a React app, you have several options — but they solve different problems. Let’s compare markdown-to-jsx, react-markdown, react-markdown-editor-lite, and the deprecated remark-react based on real engineering needs.

🧱 Core Purpose: What Each Package Actually Does

markdown-to-jsx is a standalone Markdown-to-React compiler. It parses Markdown strings and outputs React elements without external dependencies.

import Markdown from 'markdown-to-jsx';

function App() {
  return (
    <Markdown>
      {`# Hello

This is **bold**.`}
    </Markdown>
  );
}

react-markdown is a remark-based renderer. It uses the unified ecosystem (remark-parseremark-rehyperehype-react) to convert Markdown to React safely and extensibly.

import ReactMarkdown from 'react-markdown';

function App() {
  return (
    <ReactMarkdown>
      {`# Hello\n\nThis is **bold**.`}
    </ReactMarkdown>
  );
}

react-markdown-editor-lite is a full Markdown editor component, not just a renderer. It includes a textarea, toolbar, and live preview pane.

import MdEditor from 'react-markdown-editor-lite';
import 'react-markdown-editor-lite/lib/index.css';

function App() {
  const handleEditorChange = ({ text }) => console.log(text);
  return <MdEditor value="# Hello\n\nEdit me!" onChange={handleEditorChange} />;
}

remark-react was an early renderer for remark ASTs, but it’s deprecated. The npm page says: “Use react-markdown instead.” Do not use it in new code.

// ❌ DO NOT USE — deprecated
import remark from 'remark';
import reactRenderer from 'remark-react';

const result = remark().use(reactRenderer).processSync('# Hello');
// Returns React element, but package is unmaintained

🔒 Security: How They Handle Unsafe Content

markdown-to-jsx does not sanitize HTML by default. If your Markdown comes from untrusted sources, you must either disable HTML entirely or sanitize input beforehand.

// Disable HTML to prevent XSS
<Markdown options={{ disableParsingRawHTML: true }}>
  {userContent}
</Markdown>

react-markdown sanitizes by default using hast-util-sanitize. It strips dangerous attributes and tags unless you explicitly allow them.

// Safe by default — no extra config needed for basic use
<ReactMarkdown>{userContent}</ReactMarkdown>

react-markdown-editor-lite uses react-markdown under the hood for preview, so it inherits the same safe defaults.

remark-react had no built-in sanitization, making it risky for user-generated content — another reason it’s deprecated.

⚙️ Customization: Overriding Elements and Adding Features

All active packages let you customize how elements render, but their approaches differ.

markdown-to-jsx uses a flat overrides object:

<Markdown
  options={{
    overrides: {
      h1: {
        component: CustomHeading,
        props: { className: 'fancy-heading' }
      },
      code: CodeBlock // custom component
    }
  }}
>
  {content}
</Markdown>

react-markdown uses the components prop with direct component mapping:

<ReactMarkdown
  components={{
    h1: ({ node, ...props }) => <CustomHeading {...props} className="fancy-heading" />,
    code: CodeBlock
  }}
>
  {content}
</ReactMarkdown>

react-markdown-editor-lite allows customization of the preview renderer via the renderHTML prop, which typically wraps react-markdown:

<MdEditor
  renderHTML={(text) => (
    <ReactMarkdown components={{ code: CodeBlock }}>{text}</ReactMarkdown>
  )}
/>

For advanced features like syntax highlighting, react-markdown integrates cleanly with rehype-highlight or rehype-prism-plus:

import ReactMarkdown from 'react-markdown';
import remarkGfm from 'remark-gfm';
import rehypeHighlight from 'rehype-highlight';
import 'highlight.js/styles/github.css';

<ReactMarkdown
  remarkPlugins={[remarkGfm]}
  rehypePlugins={[rehypeHighlight]}
>
  {content}
</ReactMarkdown>

markdown-to-jsx requires manual handling of code blocks for syntax highlighting since it doesn’t support rehype plugins.

📦 Bundle Impact and Dependencies

markdown-to-jsx has zero production dependencies. It’s a single file with minimal footprint.

react-markdown pulls in the unified ecosystem: remark, remark-parse, remark-rehype, rehype-react, etc. This adds weight but enables powerful transformations.

react-markdown-editor-lite bundles both an editor UI and a renderer (usually react-markdown), so it’s the heaviest option — only use it when you actually need editing.

remark-react required manual setup of the entire remark pipeline and is no longer maintained.

🛑 Deprecation Status: What’s Safe to Use Today

  • markdown-to-jsx: Actively maintained.
  • react-markdown: Actively maintained, recommended by the unified team.
  • react-markdown-editor-lite: Actively maintained as of 2024.
  • remark-react: Deprecated. The npm page states: “This package is no longer maintained. Please use react-markdown instead.”

If you see remark-react in a codebase, replace it:

- import remark from 'remark';
- import reactRenderer from 'remark-react';
- const result = remark().use(reactRenderer).processSync(md);
+ import ReactMarkdown from 'react-markdown';
+ const result = <ReactMarkdown>{md}</ReactMarkdown>;

🧪 Real-World Decision Guide

Scenario 1: Displaying Trusted Documentation

You’re showing internal docs (e.g., README files) that you control.

  • Good fit: markdown-to-jsx — fast, small, no need for sanitization.
  • Also fine: react-markdown if you want GFM tables or future extensibility.

Scenario 2: Rendering User Comments or Posts

Content comes from end users; security is critical.

  • Best choice: react-markdown — built-in sanitization prevents XSS.
  • Avoid: markdown-to-jsx unless you add your own sanitizer.

Scenario 3: Building a Blog CMS Editor

Authors need to write and preview Markdown in the same view.

  • Only choice: react-markdown-editor-lite — it’s a complete editor.
  • Don’t cobble together separate textarea + renderer unless you need extreme customization.

Scenario 4: Migrating from Old Code

You inherited a project using remark-react.

  • Action: Replace with react-markdown — same ecosystem, active support.

📊 Summary Table

PackageTypeSanitizes by Default?Extensible via Plugins?Editor UI?Maintenance Status
markdown-to-jsxRenderer❌ (opt-in)✅ Active
react-markdownRenderer✅ (remark/rehype)✅ Active
react-markdown-editor-liteEditor + Renderer✅ (via react-markdown)Limited✅ Active
remark-reactRenderer✅ (manual setup)❌ Deprecated

💡 Final Advice

  • Need only rendering? Pick between markdown-to-jsx (minimalist) and react-markdown (robust).
  • Need an editor? react-markdown-editor-lite saves weeks of work.
  • See remark-react? Replace it immediately — it’s a liability.

Choose based on your actual requirements: simplicity, safety, or editing capability. Don’t over-engineer, but don’t compromise on security for user content.

How to Choose: react-markdown vs markdown-to-jsx vs remark-react vs react-markdown-editor-lite

  • react-markdown:

    Choose react-markdown when you need robust, standards-compliant Markdown parsing with extensibility through the remark and rehype plugin ecosystems. It’s the best choice for applications requiring accessibility, security (via built-in HTML sanitization), or advanced transformations like syntax highlighting, math rendering, or custom node handling. Use it when you value correctness and future-proofing over minimalism.

  • markdown-to-jsx:

    Choose markdown-to-jsx if you need a lightweight, zero-dependency Markdown renderer that’s easy to configure with custom component overrides. It’s ideal for simple rendering scenarios where bundle size matters and you don’t require the full power of the unified/remark ecosystem. Its syntax handling is solid for common cases but may not support every edge case or plugin that remark-based tools handle.

  • remark-react:

    Do not choose remark-react for new projects — it is officially deprecated. The package page on npm states it has been superseded by react-markdown, which offers better performance, active maintenance, and improved compatibility with modern React. If you encounter it in legacy code, plan a migration to react-markdown.

  • react-markdown-editor-lite:

    Choose react-markdown-editor-lite when your application requires a ready-to-use Markdown editor with live preview, toolbar controls, and image upload support. It bundles both editing and rendering logic, making it suitable for content management interfaces, note-taking apps, or any feature where users author Markdown directly. Avoid it if you only need rendering without editing capabilities.

README for react-markdown

react-markdown

Build Coverage Downloads Size

React component to render markdown.

Feature highlights

  • safe by default (no dangerouslySetInnerHTML or XSS attacks)
  • components (pass your own component to use instead of <h2> for ## hi)
  • plugins (many plugins you can pick and choose from)
  • compliant (100% to CommonMark, 100% to GFM with a plugin)

Contents

What is this?

This package is a React component that can be given a string of markdown that it’ll safely render to React elements. You can pass plugins to change how markdown is transformed and pass components that will be used instead of normal HTML elements.

When should I use this?

There are other ways to use markdown in React out there so why use this one? The three main reasons are that they often rely on dangerouslySetInnerHTML, have bugs with how they handle markdown, or don’t let you swap elements for components. react-markdown builds a virtual DOM, so React only replaces what changed, from a syntax tree. That’s supported because we use unified, specifically remark for markdown and rehype for HTML, which are popular tools to transform content with plugins.

This package focusses on making it easy for beginners to safely use markdown in React. When you’re familiar with unified, you can use a modern hooks based alternative react-remark or rehype-react manually. If you instead want to use JavaScript and JSX inside markdown files, use MDX.

Install

This package is ESM only. In Node.js (version 16+), install with npm:

npm install react-markdown

In Deno with esm.sh:

import Markdown from 'https://esm.sh/react-markdown@10'

In browsers with esm.sh:

<script type="module">
  import Markdown from 'https://esm.sh/react-markdown@10?bundle'
</script>

Use

A basic hello world:

import React from 'react'
import {createRoot} from 'react-dom/client'
import Markdown from 'react-markdown'

const markdown = '# Hi, *Pluto*!'

createRoot(document.body).render(<Markdown>{markdown}</Markdown>)
Show equivalent JSX
<h1>
  Hi, <em>Pluto</em>!
</h1>

Here is an example that shows how to use a plugin (remark-gfm, which adds support for footnotes, strikethrough, tables, tasklists and URLs directly):

import React from 'react'
import {createRoot} from 'react-dom/client'
import Markdown from 'react-markdown'
import remarkGfm from 'remark-gfm'

const markdown = `Just a link: www.nasa.gov.`

createRoot(document.body).render(
  <Markdown remarkPlugins={[remarkGfm]}>{markdown}</Markdown>
)
Show equivalent JSX
<p>
  Just a link: <a href="http://www.nasa.gov">www.nasa.gov</a>.
</p>

API

This package exports the identifiers MarkdownAsync, MarkdownHooks, and defaultUrlTransform. The default export is Markdown.

It also exports the additional TypeScript types AllowElement, Components, ExtraProps, HooksOptions, Options, and UrlTransform.

Markdown

Component to render markdown.

This is a synchronous component. When using async plugins, see MarkdownAsync or MarkdownHooks.

Parameters
Returns

React element (ReactElement).

MarkdownAsync

Component to render markdown with support for async plugins through async/await.

Components returning promises are supported on the server. For async support on the client, see MarkdownHooks.

Parameters
Returns

Promise to a React element (Promise<ReactElement>).

MarkdownHooks

Component to render markdown with support for async plugins through hooks.

This uses useEffect and useState hooks. Hooks run on the client and do not immediately render something. For async support on the server, see MarkdownAsync.

Parameters
Returns

React node (ReactNode).

defaultUrlTransform(url)

Make a URL safe.

Parameters
  • url (string) — URL
Returns

Safe URL (string).

AllowElement

Filter elements (TypeScript type).

Parameters
Returns

Whether to allow element (boolean, optional).

Components

Map tag names to components (TypeScript type).

Type
import type {ExtraProps} from 'react-markdown'
import type {ComponentProps, ElementType} from 'react'

type Components = {
  [Key in Extract<ElementType, string>]?: ElementType<ComponentProps<Key> & ExtraProps>
}

ExtraProps

Extra fields we pass to components (TypeScript type).

Fields

HooksOptions

Configuration for MarkdownHooks (TypeScript type); extends the regular Options with a fallback prop.

Extends

Options.

Fields
  • fallback (ReactNode, optional) — content to render while the processor processing the markdown

Options

Configuration (TypeScript type).

Fields
  • allowElement (AllowElement, optional) — filter elements; allowedElements / disallowedElements is used first
  • allowedElements (Array<string>, default: all tag names) — tag names to allow; cannot combine w/ disallowedElements
  • children (string, optional) — markdown
  • components (Components, optional) — map tag names to components
  • disallowedElements (Array<string>, default: []) — tag names to disallow; cannot combine w/ allowedElements
  • rehypePlugins (Array<Plugin>, optional) — list of rehype plugins to use
  • remarkPlugins (Array<Plugin>, optional) — list of remark plugins to use
  • remarkRehypeOptions (Options from remark-rehype, optional) — options to pass through to remark-rehype
  • skipHtml (boolean, default: false) — ignore HTML in markdown completely
  • unwrapDisallowed (boolean, default: false) — extract (unwrap) what’s in disallowed elements; normally when say strong is not allowed, it and it’s children are dropped, with unwrapDisallowed the element itself is replaced by its children
  • urlTransform (UrlTransform, default: defaultUrlTransform) — change URLs

UrlTransform

Transform URLs (TypeScript type).

Parameters
  • url (string) — URL
  • key (string, example: 'href') — property name
  • node (Element from hast) — element to check
Returns

Transformed URL (string, optional).

Examples

Use a plugin

This example shows how to use a remark plugin. In this case, remark-gfm, which adds support for strikethrough, tables, tasklists and URLs directly:

import React from 'react'
import {createRoot} from 'react-dom/client'
import Markdown from 'react-markdown'
import remarkGfm from 'remark-gfm'

const markdown = `A paragraph with *emphasis* and **strong importance**.

> A block quote with ~strikethrough~ and a URL: https://reactjs.org.

* Lists
* [ ] todo
* [x] done

A table:

| a | b |
| - | - |
`

createRoot(document.body).render(
  <Markdown remarkPlugins={[remarkGfm]}>{markdown}</Markdown>
)
Show equivalent JSX
<>
  <p>
    A paragraph with <em>emphasis</em> and <strong>strong importance</strong>.
  </p>
  <blockquote>
    <p>
      A block quote with <del>strikethrough</del> and a URL:{' '}
      <a href="https://reactjs.org">https://reactjs.org</a>.
    </p>
  </blockquote>
  <ul className="contains-task-list">
    <li>Lists</li>
    <li className="task-list-item">
      <input type="checkbox" disabled /> todo
    </li>
    <li className="task-list-item">
      <input type="checkbox" disabled checked /> done
    </li>
  </ul>
  <p>A table:</p>
  <table>
    <thead>
      <tr>
        <th>a</th>
        <th>b</th>
      </tr>
    </thead>
  </table>
</>

Use a plugin with options

This example shows how to use a plugin and give it options. To do that, use an array with the plugin at the first place, and the options second. remark-gfm has an option to allow only double tildes for strikethrough:

import React from 'react'
import {createRoot} from 'react-dom/client'
import Markdown from 'react-markdown'
import remarkGfm from 'remark-gfm'

const markdown = 'This ~is not~ strikethrough, but ~~this is~~!'

createRoot(document.body).render(
  <Markdown remarkPlugins={[[remarkGfm, {singleTilde: false}]]}>
    {markdown}
  </Markdown>
)
Show equivalent JSX
<p>
  This ~is not~ strikethrough, but <del>this is</del>!
</p>

Use custom components (syntax highlight)

This example shows how you can overwrite the normal handling of an element by passing a component. In this case, we apply syntax highlighting with the seriously super amazing react-syntax-highlighter by @conorhastings:

import React from 'react'
import {createRoot} from 'react-dom/client'
import Markdown from 'react-markdown'
import {Prism as SyntaxHighlighter} from 'react-syntax-highlighter'
import {dark} from 'react-syntax-highlighter/dist/esm/styles/prism'

// Did you know you can use tildes instead of backticks for code in markdown? ✨
const markdown = `Here is some JavaScript code:

~~~js
console.log('It works!')
~~~
`

createRoot(document.body).render(
  <Markdown
    children={markdown}
    components={{
      code(props) {
        const {children, className, node, ...rest} = props
        const match = /language-(\w+)/.exec(className || '')
        return match ? (
          <SyntaxHighlighter
            {...rest}
            PreTag="div"
            children={String(children).replace(/\n$/, '')}
            language={match[1]}
            style={dark}
          />
        ) : (
          <code {...rest} className={className}>
            {children}
          </code>
        )
      }
    }}
  />
)
Show equivalent JSX
<>
  <p>Here is some JavaScript code:</p>
  <pre>
    <SyntaxHighlighter language="js" style={dark} PreTag="div" children="console.log('It works!')" />
  </pre>
</>

Use remark and rehype plugins (math)

This example shows how a syntax extension (through remark-math) is used to support math in markdown, and a transform plugin (rehype-katex) to render that math.

import React from 'react'
import {createRoot} from 'react-dom/client'
import Markdown from 'react-markdown'
import rehypeKatex from 'rehype-katex'
import remarkMath from 'remark-math'
import 'katex/dist/katex.min.css' // `rehype-katex` does not import the CSS for you

const markdown = `The lift coefficient ($C_L$) is a dimensionless coefficient.`

createRoot(document.body).render(
  <Markdown remarkPlugins={[remarkMath]} rehypePlugins={[rehypeKatex]}>
    {markdown}
  </Markdown>
)
Show equivalent JSX
<p>
  The lift coefficient (
  <span className="katex">
    <span className="katex-mathml">
      <math xmlns="http://www.w3.org/1998/Math/MathML">{/* … */}</math>
    </span>
    <span className="katex-html" aria-hidden="true">
      {/* … */}
    </span>
  </span>
  ) is a dimensionless coefficient.
</p>

Plugins

We use unified, specifically remark for markdown and rehype for HTML, which are tools to transform content with plugins. Here are three good ways to find plugins:

Syntax

react-markdown follows CommonMark, which standardizes the differences between markdown implementations, by default. Some syntax extensions are supported through plugins.

We use micromark under the hood for our parsing. See its documentation for more information on markdown, CommonMark, and extensions.

Compatibility

Projects maintained by the unified collective are compatible with maintained versions of Node.js.

When we cut a new major release, we drop support for unmaintained versions of Node. This means we try to keep the current release line, react-markdown@10, compatible with Node.js 16.

They work in all modern browsers (essentially: everything not IE 11). You can use a bundler (such as esbuild, webpack, or Rollup) to use this package in your project, and use its options (or plugins) to add support for legacy browsers.

Architecture

                                                           react-markdown
         +----------------------------------------------------------------------------------------------------------------+
         |                                                                                                                |
         |  +----------+        +----------------+        +---------------+       +----------------+       +------------+ |
         |  |          |        |                |        |               |       |                |       |            | |
markdown-+->+  remark  +-mdast->+ remark plugins +-mdast->+ remark-rehype +-hast->+ rehype plugins +-hast->+ components +-+->react elements
         |  |          |        |                |        |               |       |                |       |            | |
         |  +----------+        +----------------+        +---------------+       +----------------+       +------------+ |
         |                                                                                                                |
         +----------------------------------------------------------------------------------------------------------------+

To understand what this project does, it’s important to first understand what unified does: please read through the unifiedjs/unified readme (the part until you hit the API section is required reading).

react-markdown is a unified pipeline — wrapped so that most folks don’t need to directly interact with unified. The processor goes through these steps:

  • parse markdown to mdast (markdown syntax tree)
  • transform through remark (markdown ecosystem)
  • transform mdast to hast (HTML syntax tree)
  • transform through rehype (HTML ecosystem)
  • render hast to React with components

Appendix A: HTML in markdown

react-markdown typically escapes HTML (or ignores it, with skipHtml) because it is dangerous and defeats the purpose of this library.

However, if you are in a trusted environment (you trust the markdown), and can spare the bundle size (±60kb minzipped), then you can use rehype-raw:

import React from 'react'
import {createRoot} from 'react-dom/client'
import Markdown from 'react-markdown'
import rehypeRaw from 'rehype-raw'

const markdown = `<div class="note">

Some *emphasis* and <strong>strong</strong>!

</div>`

createRoot(document.body).render(
  <Markdown rehypePlugins={[rehypeRaw]}>{markdown}</Markdown>
)
Show equivalent JSX
<div className="note">
  <p>
    Some <em>emphasis</em> and <strong>strong</strong>!
  </p>
</div>

Note: HTML in markdown is still bound by how HTML works in CommonMark. Make sure to use blank lines around block-level HTML that again contains markdown!

Appendix B: Components

You can also change the things that come from markdown:

<Markdown
  components={{
    // Map `h1` (`# heading`) to use `h2`s.
    h1: 'h2',
    // Rewrite `em`s (`*like so*`) to `i` with a red foreground color.
    em(props) {
      const {node, ...rest} = props
      return <i style={{color: 'red'}} {...rest} />
    }
  }}
/>

The keys in components are HTML equivalents for the things you write with markdown (such as h1 for # heading). Normally, in markdown, those are: a, blockquote, br, code, em, h1, h2, h3, h4, h5, h6, hr, img, li, ol, p, pre, strong, and ul. With remark-gfm, you can also use del, input, table, tbody, td, th, thead, and tr. Other remark or rehype plugins that add support for new constructs will also work with react-markdown.

The props that are passed are what you probably would expect: an a (link) will get href (and title) props, and img (image) an src, alt and title, etc.

Every component will receive a node. This is the original Element from hast element being turned into a React element.

Appendix C: line endings in markdown (and JSX)

You might have trouble with how line endings work in markdown and JSX. We recommend the following, which solves all line ending problems:

// If you write actual markdown in your code, put your markdown in a variable;
// **do not indent markdown**:
const markdown = `
# This is perfect!
`

// Pass the value as an expression as an only child:
const result = <Markdown>{markdown}</Markdown>

👆 That works. Read on for what doesn’t and why that is.

You might try to write markdown directly in your JSX and find that it does not work:

<Markdown>
  # Hi

  This is **not** a paragraph.
</Markdown>

The is because in JSX the whitespace (including line endings) is collapsed to a single space. So the above example is equivalent to:

<Markdown> # Hi This is **not** a paragraph. </Markdown>

Instead, to pass markdown to Markdown, you can use an expression: with a template literal:

<Markdown>{`
# Hi

This is a paragraph.
`}</Markdown>

Template literals have another potential problem, because they keep whitespace (including indentation) inside them. That means that the following does not turn into a heading:

<Markdown>{`
    # This is **not** a heading, it’s an indented code block
`}</Markdown>

Security

Use of react-markdown is secure by default. Overwriting urlTransform to something insecure will open you up to XSS vectors. Furthermore, the remarkPlugins, rehypePlugins, and components you use may be insecure.

To make sure the content is completely safe, even after what plugins do, use rehype-sanitize. It lets you define your own schema of what is and isn’t allowed.

Related

Contribute

See contributing.md in remarkjs/.github for ways to get started. See support.md for ways to get help.

This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.

License

MIT © Espen Hovlandsdal