Only workspace IDs are saved in this browser—never files or input.
LOCAL TOOL / JSON-DATA

GraphQL Schema Compatibility Diff

Paste the released schema definition language document.

Paste, type, or drag & drop a text file 75 chars · 7 lines · 75 B

Paste the proposed schema to compare against existing clients.

Paste, type, or drag & drop a text file 60 chars · 6 lines · 60 B
Runs locally in this browserPreview updates after 240 ms · Nothing is uploaded. Passwords are stored only when you explicitly choose Remember on this device.
02
Tool outputA path-addressed breaking-change and addition table.
Run toolNothing is uploaded. Passwords are stored only when you explicitly choose Remember on this device.
About this utility

How to use GraphQL Schema Compatibility Diff

Compare GraphQL SDL for removed types and fields, changed field types, newly required arguments, and compatible additions.

What to provide

Paste the released schema definition language document.

Paste the proposed schema to compare against existing clients.

  1. Paste, type, or drag and drop a supported text file into the input area.
  2. Place the second value or file in the adjacent panel. Sensitive fields are masked by default.
  3. Review the input and the clearly labeled output behavior.
  4. Select “Run tool” or press Ctrl/Command + Enter, then copy, download, or move the result back into the first input for another pass.

Use “Swap inputs” to reverse the comparison without copying either value.

What the result means

A path-addressed breaking-change and addition table.

Privacy and safety

This utility is loaded as browser code and processes your input only in this tab. OmniCastConverter has no upload endpoint and never stores your content, filenames, tokens, or secrets. Generated markup and code are shown as inert text and are never executed.

Limitations

  • Everything is processed in this browser tab. Input, filenames, keys, and output are never uploaded or saved. Directives, federation composition, custom validation, resolver behavior, and semantic nullability still require schema-aware integration tests.

Try the included example

Select “Load example” at any time to restore this tested sample.

type Query {
  user(id: ID!): User
}
type User {
  id: ID!
  name: String
}
type Query {
  user(id: ID!): User
}
type User {
  id: ID!
}