GraphQL Query Tester vs GraphQL Formatter
The formatter focuses on whitespace for operations and schema SDL. This tester focuses on operation documents, variables JSON, AST inspection, and request-preparation checks without schema fetching.
Paste a GraphQL operation and variables to format, validate syntax, inspect the AST, and prepare requests without calling an API.
Paste a query, mutation, subscription, or fragment. This tester never executes it.
Syntax, operation details, variables JSON, directives, fragments, and AST.
Paste an operation or load a sample. The tester parses text locally and never connects to an endpoint.
Tip: Press Ctrl+Enter or Command+Enter in either editor to validate immediately.GraphQL Query Testing Guide
Use this tester when you need to review GraphQL operations, fragments, variables JSON, directives, and AST shape before moving text into your own client or API workflow.
The formatter focuses on whitespace for operations and schema SDL. This tester focuses on operation documents, variables JSON, AST inspection, and request-preparation checks without schema fetching.
The parser checks GraphQL syntax for queries, mutations, subscriptions, and fragments. It reports line and column details for malformed braces, strings, arguments, and variable definitions.
GraphQL variables are supplied separately as JSON. This page validates and formats that JSON locally, then warns when an operation declares variables but the variables object is empty.
Missing selection-set braces, extra commas, unterminated strings, invalid variable syntax, misplaced directives, and unfinished fragments are common issues caught before a query reaches an API.
The AST view shows the parsed document structure with location metadata removed. It is helpful for understanding operations, selections, fragment definitions, directives, and variable nodes.
This tool has no endpoint field and performs no introspection, schema loading, remote validation, query execution, mutation execution, subscriptions, or network requests.
No. It treats GraphQL as text, parses syntax locally, formats the document, and validates variables JSON. It never connects to a GraphQL endpoint.
No. Schema-aware validation requires a schema. This tool intentionally avoids introspection and remote schema fetching, so it checks syntax and local structure only.
Yes. Parsed fragment definitions, operation variables, and directive usage are listed in the results panel when the GraphQL document is syntactically valid.
Paste the JSON object your own GraphQL client would send as variables. The tester validates JSON syntax and formats it, but it does not compare values against schema types.