Comparison · target: swagger codegen vs openapi generator

Swagger Codegen vs OpenAPI Generator for Petstore-style client fixture

User migrating a generator and worried about output differences.

Direct answer

For the Petstore-style client fixture, Swagger Codegen and OpenAPI Generator are built for generating code from the schema, not for 9 constraints that decide whether the output loads.

The comparison holds for a schema of this size — 2 tables — and does not claim anything about runtime, community size or pricing.

A compatibility table below scores Swagger Codegen and OpenAPI Generator against the same Petstore-style client fixture; the foreign key row is decisive, because a document carries a dangling reference without any tool objecting until load time.

Data as of 2026-11-18 · source: 3 Stack Overflow questions, @asteasolutions/zod-to-openapi at 30,999,512 monthly downloads · negative-case messages reproduced by executing the fixture against a local SQL engine (Node.js v24.22.0, engine 3.53.4) at 2026-11-18T11:53:54.233Z

The scorecard — Petstore-style client

The scorecard is scored against one shared fixture: Petstore-style client fixture, 2 tables and 7 columns. Each row states what a tool has to do for the output to load, and the note column says which property of the fixture decided the row. Rows are not weighted by preference; a row is decided by whether the output would load.

Where Swagger Codegen wins

Swagger Codegen is the better choice when the deliverable is an application rather than a fixture: it generates a typed client or a server from the schema, which is what the codebase needs before it has any test data. The Petstore-style client fixture is the shared reference for every row in the table above.

Where OpenAPI Generator wins

OpenAPI Generator is the better choice when the deliverable is an application rather than a fixture: it generates a typed client or a server from the schema, which is what the codebase needs before it has any test data. Neither of the two reads 9 constraints of this fixture as a database contract, which is the part a seed has to satisfy before a single row can be inserted.

How the rows were decided

Every row in the scorecard is decided by a property of the fixture, not by reading documentation. For Petstore-style client fixture, the deciding fixture properties were the pets to categories reference, the pets.status range declaration, the NOT NULL columns. A tool that misses any one of those produces output that a database will refuse.

A note on what this comparison does not cover

This comparison measures output correctness on one fixture. It does not measure runtime, community size, documentation quality or long-term maintenance, and it does not claim that either tool is wrong for your project. It also does not compare pricing, because every row is decided by the schema rather than by a price list: what a tool charges says nothing about whether its output loads.

What the Petstore-style client fixture requires: schema-to-SQL vs document generationEight criteria, each decided by a property of the fixture rather than by preference. The left column is what a schema-to-SQL generator does with it; the right column is what document generation leaves unresolved.
CriterionSchemaSeedDocument generationWhat decided it
Reads a multi-file OpenAPI documentyespartialboth resolve local $ref chains
Honours NOT NULLyespartialboth read the required array
Honours enum, range and length declarationsyespartialthe fixture declares pets.status with status IN ('available','pending','sold'); the declaration is read out of the schema, the DDL carries it as a CHECK constraint and the value that breaks it ships as a negative case
Honours enum membersyespartialthe enum array is copied verbatim
Produces SQL, not just JSONyesnooutput format is the difference
Resolves foreign keys across schemasyesnothe fixture has pets.category_id pointing at categories, and the second tool never reads that table
Emits deliberately invalid instancesyesnonegative cases are a separate output
Same seed produces the same bytesyesyesboth are seedable
The four checks that decide whether a schema tool is enough for Petstore-style clientApplied to Petstore-style client fixture.
CheckResult on this fixtureConsequence
More than one table references anotheryes — pets → categoriesthe generator must resolve cross-table references
Output has to be SQL, not JSONyes — the target is PostgreSQLa document generator produces the wrong artefact
Tests must assert the API rejects bad inputyes — a negative case for every declaration in the schemanegative instances have to be generated separately
Same seed must reproduce the same bytesyes — seed 42 is fixedfixtures can be committed and diffed
cmp_petstore.openapi.yaml

npx --yes @wenlu8848/schemaseed validate --input ./cmp_petstore.openapi.yaml

Download cmp_petstore.openapi.yaml

openapi: "3.0.3"
info:
  title: "Petstore-style client fixture"
  version: "1.0.0"
  description: "The pet status enum is the field that every OpenAPI tutorial uses to demonstrate an enum. The photo_urls column is a space-separated list rather than a JSON array, which is a deliberate oddity. The category reference is the part that breaks when a client library is asked to produce database rows. A code generator emits a client, not rows, so the comparison is about what artefact each tool produces."
paths: {}
x-domain-id: "cmp_petstore"
x-dialect: "postgres"
components:
  schemas:
    categories:
      type: "object"
      x-primary-key: "id"
      required: ["id", "name"]
      properties:
        id:
          type: "integer"
        name:
          type: "string"
          x-unique: true
    pets:
      type: "object"
      x-primary-key: "id"
      required: ["id", "category_id", "name", "status", "photo_urls"]
      properties:
        id:
          type: "integer"
        category_id:
          $ref: "#/components/schemas/categories"
        name:
          type: "string"
        status:
          type: "string"
          enum: ["available", "pending", "sold"]
        photo_urls:
          type: "string"

Frequently asked questions

Which one should I pick?
If the output has to load into a database and the schema has relationships, take the schema-to-SQL tool. On Petstore-style client fixture the deciding constraint was pets.category_id.
How many criteria were compared?
Eight, each decided by a property of the Petstore-style client fixture: 2 tables and 7 columns.
Was this a benchmark?
No. It is one 2-table fixture of 7 columns measured on whether the produced rows satisfy the schema, not on speed, memory or price.
Do both tools produce deterministic output?
Both are seedable, which is why the Petstore-style client fixture rows can be committed and diffed; on this fixture that is the one property the two share.

Run it against your own schema

SchemaSeed is MIT licensed and free: unlimited local generation, no account, no telemetry and no usage limit. It reads your schema file on your own machine, so nothing is uploaded anywhere. If it saves you time, you can support the project.

Get SchemaSeed — free Support the project

Questions: support@schemaseed.drz8848.win