GraphQL Inspector

Inspect GraphQL requests and responses without leaving Chrome DevTools. GraphQL Inspector helps developers understand and debug the GraphQL traffic generated by a website while its DevTools panel is open. It works with queries, mutations, subscriptions, batched requests and persisted queries. It also includes "GraphQLi", a small client for editing and sending GET or POST operations from the inspected page. What it does - Find and filter GraphQL queries, mutations and subscriptions. - Inspect formatted queries, variables, responses, headers and events. - Split batched operations and show persisted-query details. - Follow WebSocket and EventSource subscription messages. - Search requests or show only responses with GraphQL errors. - Copy requests as cURL, `fetch` or JSON. - Edit and send operations with GraphQLi. How to use it 1. Open the website you want to inspect. 2. Open Chrome DevTools. 3. Select the "GraphQL" tab. 4. Reload the page if no requests appear. Select a request to view its query, variables, response, headers and timeline. Exports and copied commands remove credential headers by default; exporting credentials requires confirmation. Use "GraphQLi" to edit and resend a captured request or write one from scratch. Requests include credentials available to the inspected page and remain subject to its origin and CORS rules. Privacy While the GraphQL DevTools panel is connected, GraphQL Inspector processes endpoints, request and response headers and bodies, and subscription events from the inspected tab. This data can contain website content, personally identifiable information, personal communications, financial details or authentication credentials, depending on the inspected application. Captured traffic remains temporarily in extension memory and is cleared when the panel is cleared, DevTools closes or the inspected tab closes. Only the "Preserve log" preference is stored in Chrome's local extension storage until it is changed or the extension is uninstalled. Exports are user initiated; default exports remove recognised credential headers, while including them requires confirmation. GraphQLi sends a request only when "Send request" is selected, from the inspected page to the chosen endpoint. Captured data is not sent to the developer, analytics services or other parties. Access to all sites and network requests is required to detect GraphQL traffic in the tab whose DevTools panel is open. The extension has no accounts, analytics, advertising, remote code or external services. Information received through Chrome APIs is used only for GraphQL Inspector's stated purpose and in accordance with the Chrome Web Store User Data Policy, including the Limited Use requirements. The privacy policy was last updated on 26 July 2026. [Contact the developer](https://nicholasgriffin.dev/contact) with privacy questions.