Ispettore

A Chrome DevTools panel for debugging Three.js, WebGL, and WebGPU applications. It captures one frame of real GPU activity and lets you browse every draw, clear, blit, and copy in it — with the color output each one produced, the full render pipeline state, and (for Three.js apps) which object, material, and pass each draw belongs to.

Think of it as Spector.js's live GPU capture combined with a RenderDoc-style pipeline inspector, with Three.js scene awareness built in.

Ispettore isn't on the Chrome Web Store yet — install it from a release zip:

1. Download ispettore-v<version>.zip from the Releases page.
2. Unzip it.
3. Open Chrome → chrome://extensions, enable Developer mode.
4. Click Load unpacked and select the unzipped folder.

Ispettore needs to see http, https, and file pages to observe their GPU contexts, so Chrome will ask for access to all sites. Nothing is sent off your machine: captures are stored locally in the extension's own IndexedDB.

Open any WebGL/WebGPU page, press F12, choose the Ispettore tab, open the Frame sub-tab, and click Capture frame. (The side panel via the toolbar icon also works; DevTools is recommended.)

Arm the next animation frame (or an on-demand render burst) and get back every GPU event it contained, with a baked color image for each one.

Events are linked back to the mesh, material, and post-processing pass that produced them, so you can filter a capture down to one object in the scene tree.

For any event, step through Vertex Input, Vertex Shader, Rasterizer, Fragment Shader, and Output Merger: draw arguments, vertex/index buffer contents, uniform values, bound textures, blend/depth/stencil state, and viewport/scissor — each tagged as set, redundant, or disabled, the way Spector.js does.

Command name with its MDN documentation, CPU/GPU duration, call arguments, and the JavaScript stack trace that issued it.

Pass-final color images and texture-copy outputs, WGSL shader modules, bind groups, and compute dispatch details, with the same capture-then-inspect model as WebGL.

Per-event CPU issue time next to live GPU duration (WebGL, where the browser exposes a timer extension), instead of one conflated number.

Every capture survives page navigation and closure; save it as a portable JSON file, reload it later, or diff two captures side by side.

Inspecting a capture only reads back what was recorded live. It never re-executes shaders, recreates GPU resources, or replays your application — see src/README.md for the capture/inspection architecture.

Apache License 2.0 — see LICENSE.