Which OpenAPI versions are supported?

OpenAPI 3.0.x (JSON or YAML). Swagger 2.0 is not supported, convert to 3.0 first using a tool like swagger2openapi.

How do I import the result into Postman?

Download the .json file, open Postman, click Import, and select the file. All folders, requests, and examples will be populated.

Are $ref schema references resolved?

Inline schemas and example / examples values are used directly. $ref pointers to #/components/schemas are not resolved, the schema is used as-is for type inference.

Can I go the other direction?

Yes, use the Postman to OpenAPI tool.

OpenAPI / Swagger to Postman

Converts an OpenAPI 3.0 spec (JSON or YAML) to a Postman Collection v2.1. Operations are grouped into folders by tag, request bodies are populated from examples or inferred schemas, and saved responses are generated from the responses object. Nothing leaves your browser.

Private by architecture: All processing is 100% client-side memory. Your data never leaves this browser tab.

OpenAPI 3.0 JSON or YAML

0 lines · 0 chars YAML / JSON

Postman Collection v2.1 JSON

0 chars JSON

About This Tool

Converts an OpenAPI 3.0 spec (JSON or YAML) into a Postman Collection v2.1, grouping operations into folders by tag and populating request bodies, headers, and saved responses from the spec's examples and schemas. Useful for turning a maintained OpenAPI spec into a ready-to-import Postman workspace without rebuilding every request by hand.

This is the OpenAPI → Postman direction, and only OpenAPI 3.0.x input is supported (not Swagger 2.0). For the reverse, use Postman to OpenAPI / Swagger.

Key Features

Convert on edit: output regenerates as soon as the input changes.
Swap direction: the ⇌ button sends the current output to the Postman to OpenAPI tool, pre-filled.
File upload & drag-and-drop: load a .yaml, .yml, or .json spec directly.
Download .json: saves the generated collection as postman-collection.json, ready for Postman's Import button.
Keyboard-driven: Cmd/Ctrl+Enter to convert, Cmd/Ctrl+Shift+C to copy the output.
Sample spec: one click loads a 4-operation Users API example covering path params, bodies, and multiple responses.

What gets converted

Tags → Folders: operations with the same tag are grouped into a Postman folder
Path parameters - {id} becomes :id with a variable entry on the URL
Query & header parameters: added to the request URL and headers respectively
Request bodies: JSON, form-urlencoded, and multipart bodies are populated from example values or schema inference
Saved responses: each responses entry generates an example response in Postman
Security schemes: bearer, basic, and API key schemes become collection-level auth
Servers: the first servers[0].url is used as the base URL

FAQ

Which OpenAPI versions are supported?: OpenAPI 3.0.x (JSON or YAML). Swagger 2.0 is not supported, convert to 3.0 first using a tool like swagger2openapi.
How do I import the result into Postman?: Download the .json file, open Postman, click Import, and select the file. All folders, requests, and examples will be populated.
Are $ref schema references resolved?: Inline schemas and example / examples values are used directly. $ref pointers to #/components/schemas are not resolved, the schema is used as-is for type inference.
Can I go the other direction?: Yes, use the Postman to OpenAPI tool.