← Back to Product Feed

Product Hunt Open Inspector

Hover any website, get its design system. Open-source. Free.

112
Traction Score
6
Discussions
Oct 2, 2026
Launch Date
View Origin Link

Product Positioning & Context

A free, open-source browser extension for inspecting layout, styles, colour, type and assets on any page, and exporting its design tokens. Unlike the popular alternatives, it requests no site access and makes zero network requests. MIT, no account.
Chrome Extensions Open Source Developer Tools

Related Ecosystem & Alternatives

Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.

Deep-Dive FAQs

What is Open Inspector?
Open Inspector is a digital product or tool described as: Hover any website, get its design system. Open-source. Free.
Where did Open Inspector originate?
Data for Open Inspector was aggregated directly from the Product Hunt community ecosystem, representing raw developer and early-adopter sentiment.
When was Open Inspector publicly launched?
The initial public indexing or launch date for Open Inspector within our tracked developer communities was recorded on October 2, 2026.
How popular is Open Inspector?
Open Inspector has achieved measurable traction, logging over 112 traction score and facilitating 6 recorded discussions or engagements.
Which technical categories define Open Inspector?
Based on metadata extraction, Open Inspector is categorized under topics such as: Chrome Extensions, Open Source, Developer Tools.
How does the creator describe Open Inspector?
The original author or development team describes the product as follows: "A free, open-source browser extension for inspecting layout, styles, colour, type and assets on any page, and exporting its design tokens. Unlike the popular alternatives, it requests no site acces..."

Community Voice & Feedback

[Redacted] • Oct 2, 2026
the activeTab-only approach is the actual selling point here, not a footnote. one question on the design-token export - when a site is using CSS-in-JS with generated class names instead of a real design system, does it still manage to group colors/spacing into something coherent, or does the export turn into a huge flat list of one-off values with no naming to speak of?
[Redacted] • Oct 2, 2026
I like this a lot. Makes it very easy
[Redacted] • Oct 1, 2026
Hey Product Hunt 👋 I'm Patryk, and I built Open Inspector for myself. Sharing here as maybe someone will find it useful.

I kept installing CSS inspector extensions and every one asked to "read and change all your data on all websites". That's my staging environments, internal dashboards and anything I'm logged into, handed to a closed-source extension that I have no way to audit.

So I built one that asks for nothing:

🔒 No host permissions. Just activeTab, granted by your click for one tab and revoked when you navigate away. Chrome's install dialog shows no site access at all.
📡 Zero network requests. A build step scans the source and shipped bundles for fetch/XHR/WebSocket/beacon and fails if it finds one.
📐 Things DevTools doesn't tell you: the spacing scale a page really follows, its type scale, grid/flex anatomy, the font that actually rendered, and a page-wide WCAG contrast audit.
đŸ“Ļ Export the design system as CSS variables, Tailwind, SCSS, JSON, W3C tokens, or a Markdown handoff for Cursor/Claude.
â†Šī¸ Safe edits. Tweak any value live; closing reverts everything exactly.

It's MIT and free forever.

Try it on a site you like, press Alt+Shift+I, and tell me what's missing or wrong.

Discovery Source

Product Hunt Product Hunt

Aggregated via automated community intelligence tracking.

Tech Stack Dependencies

No direct open-source NPM package mentions detected in the product documentation.

Media Tractions & Mentions

No mainstream media stories specifically mentioning this product name have been intercepted yet.

Deep Research & Science

No direct peer-reviewed scientific literature matched with this product's architecture.