Softwr

Documentation · head to head

Fumadocs vs Scalar

Fumadocs logo

Fumadocs

Documentation

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

From
Free
Rated
-
Full reviewWebsite
Scalar logo

Scalar

Documentation

Open source API reference renderer and request client generated entirely from an OpenAPI document

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Scalar it documents only what an OpenAPI document can express, so guides, authentication walkthroughs and conceptual pages need a second tool and a second navigation.
  • They diverge on capability: Fumadocs covers Next.js App Router native, Scalar covers OpenAPI driven reference.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Fumadocs and Scalar actually diverge.

Attributes where Fumadocs and Scalar differ
AttributeFumadocsScalar

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), platforms (Web, macOS, Windows, Linux), user rating (Not yet rated), category (Documentation).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Fumadocs

  • Next.js App Router native
  • Multiple content sources
  • OpenAPI page generation
  • Built in search
  • Headless and styled layers
  • Type safe frontmatter
  • Code and content colocation

Only in Scalar

  • OpenAPI driven reference
  • Embedded API client
  • Generated code samples
  • Framework adapters
  • Themeable renderer
  • Self hostable
  • Spec validation

What people use each for

The jobs each tool is most often brought in to do.

Fumadocs

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

Scalar

  • Replacing default Swagger UI on a public API without moving to a hosted documentation vendornot Fumadocs
  • A framework that already emits an OpenAPI document and needs a reference page mounted on a routenot Fumadocs
  • An internal API portal that must run inside a private network with no external callsnot Fumadocs
  • A team that wants readers to make authenticated test calls without leaving the reference pagenot Fumadocs

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

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.

Scalar

  • It documents only what an OpenAPI document can express, so guides, authentication walkthroughs and conceptual pages need a second tool and a second navigation.
  • The output is only as good as the spec, so an API with thin descriptions and missing examples produces a thin reference and the tool cannot compensate.
  • Deep visual customisation goes beyond the theme variables quickly, and matching an existing brand often means overriding styles against internal class names that can change.
  • Running the embedded client against a production API invites readers to send real requests, which means rate limits, test accounts and CORS configuration become your problem.
  • The open source renderer and the hosted platform advance at different rates, so a feature seen in a demo is not necessarily in the package you self host.

Pricing, plan by plan

Fumadocs

Free
  • Open sourceFree
    • MIT licence
    • All packages included
    • Self hosted or deployed with your Next.js application

Scalar

Free
  • Open source rendererFree
    • MIT licence, no fee for the renderer
    • Embedded request client
    • Framework adapters

Which should you pick?

Choose Fumadocs if

  • You need next.js app router native.
  • You want to start without paying.
  • You work on Web, macOS, Windows, Linux.
  • You also want multiple content sources.
Fumadocs review

Choose Scalar if

  • You need openapi driven reference.
  • You want to start without paying.
  • You work on Web, macOS, Windows, Linux.
  • You also want embedded api client.
Scalar review

Questions people ask

Is Fumadocs or Scalar better?
Neither clearly leads. Fumadocs starts at Free and Scalar at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Fumadocs or Scalar?
Fumadocs starts at Free and Scalar at Free.
Does Fumadocs or Scalar run on more platforms?
Both run on Web, macOS, Windows, Linux, so platform support will not decide this one for you.
Can I use Fumadocs for free?
Both have a free tier, so you can try either at no cost before committing.
What is Fumadocs best used for?
Fumadocs is most often used 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. Of those, documentation that must sit behind login and show different content to different customer plans and a next.js product team that wants docs to deploy in the same pipeline as the application are not what Scalar is typically brought in for.
What can Fumadocs do that Scalar cannot?
Fumadocs covers Next.js App Router native, Multiple content sources, OpenAPI page generation, Built in search. Scalar covers OpenAPI driven reference, Embedded API client, Generated code samples, Framework adapters.

Answered from the vendors’ own pages

Fumadocs: Can I put documentation behind authentication?

Yes. Pages are Next.js server components, so the same session and authorisation checks the rest of the application uses apply.

Scalar: Can I use it without paying anything?

Yes. The renderer is open source and self hostable. The hosted platform is a separate paid product.

Fumadocs: Does it work outside Next.js?

No. The UI layer depends on the Next.js App Router.

Scalar: Does it replace a full documentation site?

No. It covers API reference. Guides and concepts need a general documentation generator alongside it.

Fumadocs: Can it generate pages from an OpenAPI spec?

Yes, including operation pages, schema rendering and an interactive request playground.

Scalar: Will my reference go out of date?

Only if your OpenAPI document does. The reference is generated, so there is no second copy to forget.

Fumadocs: Who maintains it and is that a risk?

A very small maintainer group. For a long lived commercial documentation set, treat the low bus factor as a real risk and budget for owning a fork.

Scalar: Does the embedded client send real requests?

Yes, from the reader browser. Plan for CORS, rate limits and a sandbox environment before publishing.

Fumadocs: Do I still need a separate docs deployment?

No, and avoiding one is the main reason to choose it. The cost is that docs share your application uptime.

Scalar: What if my API has no OpenAPI document?

Then this is the wrong tool. Producing an accurate spec is the prerequisite, not an optional step.

Share

Related pages

More on Fumadocs

More on Scalar

Keep looking

Other head to heads