GraphQL Schema Explorer
Browse matching GraphQL types in the page, then open the details table to inspect fields, arguments and relationships. Paste SDL or introspection JSON and search by name or kind.
Accepts up to 1,000,000 characters of SDL or introspection JSON, at most 100,000 tokens or 50,000 JSON values and 10,000 types, with a search of up to 200 characters. Very large schemas whose report would pass 4,000,000 characters are rejected. Everything runs in your browser in a background worker. Downloads are a JSON report and a Markdown reference. SDL text, or introspection JSON with a __schema object. Up to 1,000,000 characters. Review the settings before running.
Your result
How to use GraphQL Schema Explorer
- Paste the schema as SDL or introspection JSON.
- Optionally enter search text or choose one type kind.
- Run the explorer. Browse matching types, then open Fields and relationships to search the full member list.
- Download the complete JSON report or Markdown reference for the current filters.
Useful next steps
Accepts up to 1,000,000 characters of SDL or introspection JSON, at most 100,000 tokens or 50,000 JSON values and 10,000 types, with a search of up to 200 characters. Very large schemas whose report would pass 4,000,000 characters are rejected. Everything runs in your browser in a background worker. Downloads are a JSON report and a Markdown reference.
What you see
Matching types appear by name and kind in the page. Open Fields and relationships to inspect their fields and arguments, input fields, enum values, implemented interfaces, implementers, union members and referring fields. Search the details table or move between its pages for larger schemas. The JSON and Markdown downloads retain all details for the current filters, including descriptions and deprecation reasons. Built-in scalars and directives are left out.
Search and filters
Search keeps types whose name, field names, input field names or enum values contain your text, ignoring case. The kind filter keeps only objects, interfaces, unions, enums, input objects or scalars. Counts for the whole schema stay in the report.
Problems in the schema
The explorer still loads a schema that has mistakes, such as a field type that is not defined, a duplicate field or a type that misses an interface field, and lists them as problems to review. Schema extensions are merged into their types.