swagger-ui README

The project's README from github.com/swagger-api/swagger-ui. As one markdown file: README.md.

NPM version Build Status security scan total GitHub contributors

monthly npm installs docker registry monthly packagist installs gzip size

Introduction

Swagger UI allows anyone — be it your development team or your end consumers — to visualize and interact with the API’s resources without having any of the implementation logic in place. It’s automatically generated from your OpenAPI (formerly known as Swagger) Specification, with the visual documentation making it easy for back end implementation and client side consumption.

General

👉🏼 Want to score an easy open-source contribution? Check out our Good first issue label.

🕰️ Looking for the older version of Swagger UI? Refer to the 2.x branch.

This repository publishes three different NPM modules:

We strongly suggest that you use swagger-ui instead of swagger-ui-dist if you're building a single-page application, since swagger-ui-dist is significantly larger.

If you are looking for plain ol' HTML/JS/CSS, download the latest release and copy the contents of the /dist folder to your server.

Compatibility

The OpenAPI Specification has undergone 5 revisions since initial creation in 2010. Compatibility between Swagger UI and the OpenAPI Specification is as follows:

Swagger UI Version Release Date OpenAPI Spec compatibility Notes
5.32.0 2026-02-27 2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.1.0, 3.1.1, 3.1.2, 3.2.0 tag v5.32.0
5.19.0 2025-02-17 2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.1.0, 3.1.1, 3.1.2 tag v5.19.0
5.0.0 2023-06-12 2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.1.0 tag v5.0.0
4.0.0 2021-11-03 2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3 tag v4.0.0
3.18.3 2018-08-03 2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3 tag v3.18.3
3.0.21 2017-07-26 2.0 tag v3.0.21
2.2.10 2017-01-04 1.1, 1.2, 2.0 tag v2.2.10
2.1.5 2016-07-20 1.1, 1.2, 2.0 tag v2.1.5
2.0.24 2014-09-12 1.1, 1.2 tag v2.0.24
1.0.13 2013-03-08 1.1, 1.2 tag v1.0.13
1.0.1 2011-10-11 1.0, 1.1 tag v1.0.1

Anonymized analytics

SwaggerUI uses Scarf to collect anonymized installation analytics. These analytics help support the maintainers of this library and ONLY run during installation. To opt out, you can set the scarfSettings.enabled field to false in your project's package.json:

// package.json
{
  // ...
  "scarfSettings": {
    "enabled": false
  }
  // ...
}

Alternatively, you can set the environment variable SCARF_ANALYTICS to false as part of the environment that installs your npm packages, e.g., SCARF_ANALYTICS=false npm install.

Documentation

Usage

Customization

Development

Contributing

Integration Tests

End-to-end tests use Cypress. Run the full suite locally with npm run cy:ci, which starts the required servers, runs Cypress headless, and shuts the servers down afterwards - be sure you aren't running a dev server on the same ports when testing!

To debug or run individual specs interactively, use npm run cy:dev to open the Cypress runner.

To run a single spec headless, start the servers in one terminal and run that spec in another:

npm run cy:start
# in a second terminal:
npm run cy:run -- --spec "test/e2e-cypress/e2e/features/deep-linking.cy.js"

Browser support

Swagger UI works in the latest versions of Chrome, Safari, Firefox, and Edge.

Known Issues

To help with the migration, here are the currently known issues with 3.X. This list will update regularly, and will not include features that were not implemented in previous versions.

Security contact

Please disclose any security-related issues or vulnerabilities by emailing [email protected], instead of using the public issue tracker.

License

SwaggerUI is licensed under Apache 2.0 license. SwaggerUI comes with an explicit NOTICE file containing additional legal notices and information.

swagger-ui (swagger-api/swagger-ui)

Searching Database…

What is this?Swagger UI turns an OpenAPI (formerly Swagger) spec into interactive, visual API documentation: your team or end consumers can see and try the API's resources without any implementation logic in place.
Is it a hosted service or something I ship myself?Something you ship: a front-end library distributed as three npm packages — swagger-ui for bundler-based SPAs, dependency-free swagger-ui-dist, and swagger-ui-react as a React component — plus plain HTML/JS/CSS assets.
How do I get it running?Run npm install swagger-ui (or swagger-ui-dist if your setup can't resolve npm dependencies) and point it at your spec; for plain HTML/JS/CSS, download a release and copy the /dist folder contents to your server.
Do I need anything beyond a browser to view the docs?No — it's pure front-end, just assets to serve next to your spec. It works in the latest versions of Chrome, Safari, Firefox, and Edge.
Any known gaps I should know about?The 3.X line has documented known issues: only part of the previously supported parameters are available, the JSON Form Editor isn't implemented, collectionFormat support is partial, and l10n translations are missing.
Does the install phone home?Once: Scarf collects anonymized analytics, and only during npm installation. Opt out via scarfSettings.enabled=false in your package.json or the SCARFANALYTICS=false environment variable.
Is there an official Docker image?Yes — the repository ships Docker build-and-push CI workflows, so you can run Swagger UI as a container instead of copying dist assets onto a server yourself.
Can I customize how the documentation looks?Yes — beyond configuration, the docs cover a Plugin API and custom layouts, so you can extend or replace parts of the default rendering.
Does it work with OAuth2-secured APIs?Yes — OAuth2 is a documented usage topic, so protected endpoints can be tried out from the UI once configured.
Size
622.5 MB
Stars
29K
Age
15y
Commits · 90 Days