OpenAPI to Postman

What this tool does

Paste, upload, or load an example OpenAPI (3.x) or Swagger (2.0) document and get back a Postman Collection v2.1 file — ready to import into Postman, ready to hand to a teammate, no Postman account or login required to generate it.

What gets converted

• Folders by tag. Endpoints are grouped into Postman folders the same way they're grouped by tag in the spec.
• URLs, with path variables. A path like /pets/{petId} becomes {{baseUrl}}/pets/:petId, with petId set up as a Postman path variable — the first server URL in the spec becomes the baseUrl collection variable, so switching environments in Postman is a one-line change.
• Query and header parameters, added to each request's Params and Headers tabs with their descriptions carried over.
• Request bodies, with a generated example. Instead of an empty body, each request with a JSON body gets a realistic example generated from its schema — using the schema's own example or default value where one is provided, and a sensible placeholder otherwise (format-aware for strings, e.g. an actual-looking email or UUID for format: email / format: uuid).

Cookie parameters aren't converted — Postman handles cookies separately from a collection file.

FAQ

Does this call Postman's API or need an account?

No — this generates a standard Postman Collection v2.1 JSON file entirely in your browser. Import it into Postman (or any tool that reads the same format) via drag-and-drop or the Import button; nothing is sent anywhere first.

My spec looks fine but the export seems off

Run it through the OpenAPI Validator first — broken $refs or malformed operations can produce incomplete requests here without necessarily showing up as a parse error.

I just want to browse the spec, not export it

The OpenAPI Viewer renders the same document as a readable, searchable list of endpoints instead.