Postman to OpenAPI / Swagger

About This Tool

Converts a Postman Collection v2.1 export into an OpenAPI 3.0.3 YAML spec, walking folders, requests, and saved examples to rebuild paths, parameters, request bodies, and tags. Useful when a collection is the only documentation an API has, and that documentation needs to go into Swagger UI, Redoc, or a codegen pipeline.

This is the Postman → OpenAPI direction. For the reverse, use OpenAPI / Swagger to Postman.

Key Features

• Convert on edit: output regenerates as soon as the input changes, no separate run step.
• Swap direction: the ⇌ button sends the current output to the OpenAPI to Postman tool, pre-filled.
• File upload & drag-and-drop: load a .json collection export directly.
• Download .yaml: saves the generated spec as openapi.yaml.
• Keyboard-driven: Cmd/Ctrl+Enter to convert, Cmd/Ctrl+Shift+C to copy the output.
• Sample collection: one click loads a 3-endpoint Users API example to see the mapping.

What gets converted

• Folders → Tags: top-level Postman folders become OpenAPI tags
• Path variables - :id becomes {id} with a path parameter entry
• Query params: url.query items become in: query parameters
• Headers: custom request headers become in: header parameters (Content-Type, Authorization, and Accept are handled structurally)
• Request bodies: raw JSON, urlencoded, form-data, and GraphQL bodies are all converted with inferred schemas
• Auth: collection-level bearer / basic / API key auth becomes a securitySchemes entry
• Saved responses: example responses seed the responses object