Inspect. Create. Check. Capture.

A browser toolkit for web development and design

61 tools for reading, changing and capturing a web page, in one extension. No account, no upload, and nothing running on a page until you open it.

Not installable yet. InspectDock has not been submitted to any browser store, so there is no install button to give you. You can build it from source and load it unpacked today.

How to build and load it See the 61 tools

What it is for

Read the page

Computed styles, box measurements, fonts, colours, metadata, structured data and the stack a site is built on.

Change the page

Edit text in place, swap fonts, force dark mode, try a background, and inject your own CSS, to see a change before you write it.

Capture the page

Viewport, a region, a single element, or a full-page stitch, then annotate or blur before you share it.

What it looks like

These are screenshots of the real tools, taken from the build in this repository with the output their engines actually produced. Nothing here is a mockup.

The Gradient Builder tool showing three colour stops, a live preview of the gradient, and the generated CSS declaration. — Gradient Builder, with the live preview and the CSS it produced.

The Regex Tester tool matching two email addresses in a line of text and reporting their offsets. — Regex Tester, matching two addresses and skipping the one that is not.

The Contrast Checker tool reporting a 4.76 to 1 ratio with a separate verdict for each WCAG threshold. — Contrast Checker, with a verdict per threshold rather than one pass or fail.

The JSON and CSV Converter turning a two-row JSON array into quoted CSV. — JSON and CSV Converter, with spreadsheet-safe quoting.

How it treats your data

No always-on script. Nothing is injected into a page until you open the toolbar there.
Permissions asked one at a time. Cookie access and access to other domains are optional. The extension starts with neither and asks only when a tool genuinely needs it, for that one site.
No analytics, no crash reporting. There is nothing to opt out of, because nothing is collected.
Your screenshots stay yours. Captures, exports and extracted data never leave the device.
Bring your own AI key. The assistant is off until you configure it, the key is held by the extension rather than the page, and page text is sent only when you send a message with context switched on.

Read the privacy page

Where the project actually is

Being straight about this matters more than a launch banner:

Tools built	61
Tools verified in a browser	0
Store listings	None yet
Paid tier	Not built
Browsers tested	Chrome only

"Built" means the code exists and its tests pass. It does not mean a human has sat down and confirmed each tool behaves correctly in a real browser, which is the work happening now. We would rather tell you that than round it up.

Questions

Can I install it yet?: No. InspectDock has not been submitted to any browser store, so there is no install link. You can build it from source and load it unpacked in developer mode today. When a listing exists this page will link to it.
What does it send to a server?: Nothing, by default. Screenshots, extracted data and exports stay on your device. There is no analytics and no crash reporting. The AI Assistant is the one exception, it is off until you configure it, it uses your own API key, and it only sends page text when you send a message with page context switched on.
Why does it ask for permissions one at a time?: Because it does not need them until you use the tool that needs them. Cookie access and access to other domains are optional: the extension starts without either and asks when a specific tool actually requires it, for that site. If you refuse, the tool explains what it cannot do instead of failing silently.
Does it run on every page I visit?: No. There is no always-on content script. Nothing is injected into a page until you open the toolbar there.

All questions