Fumadocs

Documentation framework for Next.js that treats the docs site as an application rather than a static export

As of 31 August 2026, Fumadocs is free to use. Fumadocs is a set of Next. Softwr lists it under Documentation. Fumadocs is available on Web, macOS, Windows, Linux.

Visit siteVisit Fumadocs

Overview

What Fumadocs does

Fumadocs provides content sourcing, MDX compilation, search, and an unstyled and a styled UI layer for building documentation inside a Next.js application. Content can come from local MDX files, from a headless content management system, or from an OpenAPI document, and the layout components are consumed as React components rather than configured through a theme file. What distinguishes it commercially is that the documentation is not a separate site. Because it runs as Next.js routes, docs pages can sit behind the same authentication as the product, read the signed in user to show plan specific content, and deploy in the same pipeline. Teams that currently maintain a marketing site, an application and a third party documentation host can collapse three deployments into one. Nothing else in this category makes that straightforward. The buyers are product teams already committed to Next.js and the React Server Components model, particularly those needing gated or personalised documentation. The trade off is twofold. It is a library, so you own more of the assembly than a themed generator would ask of you; and the project is driven by a small maintainer group, so the bus factor is low in a way that a corporate backed alternative is not.

What people use it for

Documentation that must sit behind login and show different content to different customer plans
A Next.js product team that wants docs to deploy in the same pipeline as the application
API reference pages generated from an OpenAPI document alongside hand written guides in one navigation tree
A design system site where the component documentation must render the live components from the same codebase

Where it falls short

Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about Fumadocs.

It is a library rather than a finished theme, so the initial setup is meaningfully longer than a generator that ships a working site from one command.
Maintenance is concentrated in a very small group, so an unresponsive week is a blocked upgrade and there is no support contract to escalate to.
It only targets Next.js, so adopting it commits the documentation to that framework and a later migration means rewriting the site rather than swapping a theme.
Breaking changes have arrived across minor versions during rapid development, so pinning versions and reading migration notes is a recurring cost rather than a one off.
Running docs inside the application means docs traffic hits your application infrastructure and shares its failure modes, where a separate static site would have stayed up.

Cross-shopped

What people choose instead of Fumadocs

Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.

Fumadocsvs
Docusaurus
Docusaurus: A finished themed site out of the box and corporate backing, if you do not need docs inside the application
Fumadocsvs
Mintlify
Mintlify: Hosted, with a writer friendly editor, when authentication gated docs are not a requirement
Fumadocsvs
GitBook
GitBook: Fully hosted and framework independent, so the docs stay up even when your application does not

Pricing

What Fumadocs costs

Taken from the vendor's own pricing page. Prices move, so check before you buy.

Open source

Free

MIT licence
All packages included
Self hosted or deployed with your Next.js application
Community support via GitHub and Discord

Capabilities

Features

Next.js App Router native
Docs render as server components inside your existing application routes
Multiple content sources
Local MDX, headless CMS or OpenAPI documents through pluggable source adapters
OpenAPI page generation
Renders operation pages, schemas and an interactive request playground from a spec
Built in search
Orama powered static or server search, with Algolia supported as an alternative
Headless and styled layers
Use the unstyled core with your own design system, or the supplied UI package
Type safe frontmatter
Zod schemas validate page metadata at build time rather than failing in production
Code and content colocation
Docs deploy with the application, so a feature and its documentation ship together