Swagger UI Preview

It supports OpenAPI 3.0.x, OpenAPI 3.1.x, and Swagger 2.0, in both YAML and JSON format. The spec version is auto-detected from the 'openapi' or 'swagger' field at the root of your spec.

The preview renders: API title, version, description, and contact info; server URLs; all endpoints grouped by tag with color-coded HTTP method badges (GET=blue, POST=green, PUT=orange, PATCH=yellow, DELETE=red); path, query, and header parameters with types and required markers; request body content types; and all response codes with descriptions. Click any endpoint to expand its details.

This is a lightweight browser-based preview, not a full Swagger Editor replacement. It's designed for quick visual inspection — seeing how your API is structured, verifying tags, checking parameter lists, and reviewing response codes — without needing to run a local server or upload your spec anywhere. For full JSON Schema validation, use the OpenAPI Spec Validator tool.

No. All parsing and rendering runs 100% in your browser using JavaScript. Your OpenAPI spec — which may contain internal endpoint names and data models — never leaves your machine.

This tool is faster for a quick read-through of an API — no setup, no local server, works offline. It's useful for reviewing a spec in a PR, sharing a quick preview with a non-technical stakeholder, or checking if a spec looks structurally correct before feeding it to a code generator.

Yes. Swagger 2.0 specs (with 'swagger: "2.0"') are parsed and rendered. The server URL is reconstructed from the 'host', 'basePath', and 'schemes' fields. Paths and operations render the same way as OpenAPI 3.x.