Reading raw OpenAPI YAML means jumping between paths and $refs in components. Paste or open a spec and this viewer renders it as documentation: endpoints grouped by tag with colour-coded methods, parameters, request bodies and responses with their fields expanded, and every schema. It handles OpenAPI 3.0 and 3.1 and Swagger 2.0, in YAML or JSON, entirely in your browser.
What it shows
Operations: method, path, summary and description; deprecated endpoints are struck through.
Parameters: path, query, header and cookie parameters with types and required flags.
Bodies and responses: fields resolved through local $refs and allOf, nested several levels deep; recursive schemas are marked.
External references to other files or URLs aren’t fetched. Bundle a multi-file spec into one with npx @redocly/cli bundle openapi.yaml -o bundled.yaml first.
Private by design
Internal API specs often describe unreleased features. This viewer never uploads or fetches anything; the YAML is parsed in your browser with safety limits against malicious documents.
FAQ
How do I view an OpenAPI file?
Paste the YAML or JSON above, or click Open file. The documentation renders immediately.
Does it support Swagger 2.0?
Yes, as well as OpenAPI 3.0 and 3.1.
Can it load a spec from a URL?
No; to keep specs private, nothing is fetched. Download the file and open it, or paste its contents.
Are $ref references resolved?
Local references within the document (#/components/…) are. External files must be bundled into one document first.