Postman Collection → OpenAPI 3, done properly

Export your collection from Postman (v2 or v2.1), then use Open file or Load URL in OASForge. The converter detects the collection automatically and produces an OpenAPI 3.0.3 document you can immediately validate, edit and preview.

What the conversion gets right

• Auth becomes securitySchemes — Bearer, Basic, API key and OAuth2 (each grant type mapped to its OpenAPI flow), with request-level auth taking precedence over collection-level, and raw Authorization headers recognized too.
• Saved responses become named examples — every saved response is kept: grouped by status code and media type, single responses as example, multiple as named examples entries, so nothing you saved in Postman is lost.
• Noise is removed at the source — Content-Type, Accept and transport headers that OpenAPI ignores are dropped instead of being emitted as broken parameters, while meaningful response headers are preserved as headers definitions.
• Postman variables survive — {{baseUrl}}-style variables become server variables and path parameters where they belong.

Then keep working in the same tab

The converted document opens in the editor with validation on: leftover issues surface immediately, most with one-click fixes. From there you can preview it in Swagger UI, exercise it against the built-in mock server, or export it back out — including as a self-contained HTML documentation file.

The conversion runs entirely in your browser: your collection — often full of internal URLs and tokens — is never uploaded anywhere.