vercel/streamdown — an AI tool — sits at 5.8k GitHub stars in the AI Tools space. A drop-in replacement for react-markdown, designed for AI-powered streaming.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
A drop-in replacement for react-markdown, designed for AI-powered streaming.
Overview
Formatting Markdown is easy, but when you tokenize and stream it, new challenges arise. Streamdown is built specifically to handle the unique requirements of streaming Markdown content from AI models, providing seamless formatting even with incomplete or unterminated Markdown blocks.
Streamdown powers the AI Elements Message component but can be installed as a standalone package for your own streaming needs.
🎨 Unterminated block parsing - Build with remend for better streaming quality
📊 GitHub Flavored Markdown - Tables, task lists, and strikethrough support
🔢 Math rendering - LaTeX equations via KaTeX
📈 Mermaid diagrams - Render Mermaid diagrams as code blocks with a button to render them
🎯 Code syntax highlighting - Beautiful code blocks with Shiki
🛡️ Security-first - Built with rehype-harden for safe rendering
⚡ Performance optimized - Memoized rendering for efficient updates
Installation
npm i streamdown
Then, update your Tailwind globals.css to include the following so that Tailwind can detect the utility classes used by Streamdown.
@source "../node_modules/streamdown/dist/*.js";
The path must be relative from your CSS file to the node_modules folder containing streamdown. In a standard Next.js project where globals.css lives in app/, the default path above should work.
If you install optional Streamdown plugins, add their matching @source lines from the relevant plugin docs (/docs/plugins/code, /docs/plugins/cjk, /docs/plugins/math, /docs/plugins/mermaid). Only include plugin @source entries for packages that are actually installed.
In a monorepo (npm workspaces, Turbo, pnpm, etc.), dependencies are typically hoisted to the root node_modules. You need to adjust the relative path to point there:
/* apps/web/app/globals.css → 3 levels up to reach root node_modules */
@source "../../../node_modules/streamdown/dist/*.js";
Adjust the number of ../ segments based on where your CSS file lives relative to the root node_modules. If you install Streamdown plugins, add their respective @source entries only when those packages are installed.
CSS Custom Properties (Design Tokens)
Streamdown components are built using shadcn/ui's design system and rely on CSS custom properties for colors, border radius, and spacing. Without these variables defined, components may render with missing backgrounds, borders, or incorrect spacing.
If you are already using shadcn/ui, these variables are set up automatically. If not, add the following minimal set to your global CSS:
fallbackComponent — fallback for missing map entries
Streamdown ships built-in renderers for common markdown tags. For tags that are
not in that map — and not overridden via components — you can provide a
fallbackComponent. Useful for allowedTags custom elements and uncovered HTML
tags like <span>, <em>, <div>, or <br>.
This is not a full unstyled mode: built-in entries (and any explicit
components overrides) still take precedence. To restyle tags that already have
defaults (e.g. h1, p, code), pass them in components.
import { createElement } from "react";
import { Streamdown } from "streamdown";
// Render missing map entries / allowedTags via a pass-through
<Streamdown
allowedTags={{ mention: ["user_id"] }}
fallbackComponent={({ node, children, ...props }) =>
createElement(node!.tagName, props, children)
}
>
{markdown}
</Streamdown>
Combine with explicit overrides when some tags need special treatment:
How does vercel/streamdown compare to other AI Tools projects?
vercel/streamdown is tracked by TopGit in the AI Tools category, with 5.8k GitHub stars and written in TypeScript. Browse the AI Tools topic page on TopGit to compare it against similar projects by stars and activity.
How many stars does vercel/streamdown have?
vercel/streamdown has 5.8k GitHub stars — refresh the page for the live number, or check github.com/vercel/streamdown. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is vercel/streamdown open source?
TopGit's metadata for vercel/streamdown does not record a license. Most public repositories on GitHub ARE open source, but the exact terms vary — verify by opening the LICENSE file directly.
What else is in the AI Tools space?
vercel/streamdown is tracked by TopGit under the AI Tools category, alongside 3 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is vercel/streamdown?
vercel/streamdown (vercel/streamdown) is a TypeScript project on GitHub. From the project's own README: A drop-in replacement for react-markdown, designed for AI-powered streaming.
Where can I see vercel/streamdown in action?
The project maintains a homepage at https://streamdown.ai. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about vercel/streamdown?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/vercel/streamdown is the definitive source.
Read full README in the tab above.
Is streamdown worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of streamdown.