Scalar

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

As of 31 August 2026, Scalar is free to use. Scalar renders an API reference straight from an OpenAPI document with an embedded request client, so there is no prose to maintain alongside the spec and therefore nothing to drift. Softwr lists it under Documentation. Scalar is available on Web, macOS, Windows, Linux.

Visit siteVisit Scalar

Overview

What Scalar does

Scalar reads an OpenAPI or Swagger document and produces a browsable API reference with an integrated request client that sends real calls from the page, plus generated code samples in a range of languages. The renderer is an open source package that can be embedded in an existing site, dropped into a framework through an official adapter, or run as a standalone page, and the company also operates a hosted platform on top of it. The commercial argument is drift. Documentation tools split into those that generate from a machine readable spec and those that expect a human to keep prose in step with the API, and only the first kind cannot go stale. Scalar sits firmly in the generated camp: if an endpoint changes in the spec, the reference changes on the next build, and there is no separate document for someone to forget. Teams replacing hand written reference pages typically retire a recurring maintenance task rather than a licence. The buyers are API teams that already produce an accurate OpenAPI document, often from framework annotations, and want a reference better than the default Swagger UI without a hosted contract. The trade off is scope. Guides, tutorials, authentication walkthroughs and conceptual explanation do not live in an OpenAPI document, so most teams end up running Scalar for reference and a separate generator for everything else.

What people use it for

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

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 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.

Cross-shopped

What people choose instead of Scalar

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.

Scalarvs
Redocly
Redocly: More mature reference tooling with linting, versioning and governance features for large spec estates
Scalarvs
Swagger UI
Swagger UI: The reference implementation, already installed almost everywhere, if a plainer page is acceptable
Scalarvs
Stoplight
Stoplight: Spec design, mocking and governance in one product when the problem is authoring the spec, not rendering it

Pricing

What Scalar costs

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

Open source renderer

Free

MIT licence, no fee for the renderer
Embedded request client
Framework adapters
Self hosted with no service dependency
Paid hosted platform available separately

Capabilities

Features

OpenAPI driven reference
Every page is derived from the spec, so the reference cannot describe an endpoint that no longer exists
Embedded API client
Send authenticated requests from the reference page and see real responses
Generated code samples
Request examples in multiple languages produced from the operation definition
Framework adapters
Official integrations for Express, Fastify, NestJS, Hono, Laravel, .NET and others
Themeable renderer
CSS variable based themes and a configuration object rather than a fork
Self hostable
The renderer is an npm package or a single script tag with no service dependency
Spec validation
Flags malformed or incomplete OpenAPI documents before they reach readers