Generate TypeScript types and interfaces from GraphQL schema definitions and query documents.
GraphQL to TypeScript turns GraphQL schema definitions and operation documents into TypeScript declarations that mirror the types available to application code. Schema input can describe objects, inputs, enums, scalars, lists, and nullability; operation input narrows results to the fields a query actually selects. The important distinction is scope: a schema type represents the full GraphQL contract, while a query result represents one selection set. Users often expect those shapes to be identical, but an operation can omit fields, rename them with aliases, or define a separate variables shape.
Schema definitions establish the source type graph. GraphQL object and input fields become TypeScript properties, named GraphQL types become reusable declarations, and list wrappers become array-shaped types. Nullability applies at every wrapper level: String!, [String]!, and [String!]! express different contracts. Built-in scalars have conventional TypeScript counterparts, but the meaning of a custom scalar cannot be determined from its name alone.
Query documents define selection-specific types. A result shape follows the response keys in the operation's selection set, including aliases, instead of copying every field from the corresponding schema object. Variable declarations form a separate input shape. Fragment selections can contribute fields to the result, but determining those fields' TypeScript types still requires the schema definitions that declare their GraphQL return types.
Usually no. A query names fields but does not state each selected field's return type. The corresponding schema supplies whether a field returns a scalar, object, enum, list, or nullable value. Variable declarations provide GraphQL input type names, but those named input types also require schema definitions for complete TypeScript shapes.
No. TypeScript types and interfaces describe values for static checking and are not runtime validators. They cannot establish that a server response matches the pasted schema or operation after the TypeScript declarations have been erased. Runtime response validation requires a separate validation step based on an appropriate schema or explicitly defined runtime checks.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.