How are JSON types mapped to GraphQL scalars?

Strings map to String, booleans to Boolean, and numbers to Int or Float depending on whether the value is a whole number. Nested objects become their own named GraphQL type, and arrays become list types based on their element type.

How does it decide which fields are non-null?

For an array of objects, a field is marked non-null (with a trailing exclamation mark) only if it appears in every element of the array. Fields present in just some elements stay nullable, which mirrors how optional fields usually behave in real data.

Will it detect IDs and dates automatically?

No — JSON has no native ID or date type, so an identifier shows up as Int or String and an ISO date shows up as String. The tool deliberately stays conservative; change these to ID or a custom DateTime scalar by hand after generating.

Does my JSON get sent to a server?

No. Parsing and type inference run entirely in your browser. The JSON you paste, which may contain real records, never leaves your machine.

What happens with an empty array or a null value?

An empty array cannot reveal its element type, so it defaults to a list of String. A null value also has no type information and defaults to a nullable String. Provide non-empty, non-null examples for the most accurate output.

JSON to GraphQL Schema Generator

The JSON to GraphQL Schema Generator turns a representative JSON document into a GraphQL Schema Definition Language (SDL) draft. It infers types from your data so you can bootstrap a schema in seconds, then refine the scalar choices by hand. Everything runs in your browser.

How it works

The generator walks the JSON value recursively and builds a type table:

Scalars — string becomes String, boolean becomes Boolean, and a number becomes Int when it is a whole number or Float otherwise.
Objects — every nested object becomes its own named type, with the type name derived by PascalCasing the field key (so a address field yields a type Address).
Arrays of objects — all elements are merged into one shape. A field is marked non-null (!) only when it appears in every element; fields seen in only some elements stay nullable. This is how genuinely optional fields are detected.
Arrays of scalars — become a list of the element scalar, e.g. [String!].

The top-level object becomes the Root type, which is emitted first, followed by every named type it references.

Example

Given an object whose posts array contains items with title and views, plus a pinned flag on only some of them, the tool produces a Post type where title and views are non-null and pinned is nullable — exactly reflecting the optionality observed in the sample.

Notes

Because JSON carries no semantic type beyond its primitive shape, the output is a starting point. Replace inferred String identifiers with ID, ISO date strings with a DateTime scalar, and split large Root objects into proper query and mutation types as your API design requires.