Design system
h1color.accent#23465C
Aafont.displayIowan · Avenir
Inspect any live page like a design file. Tweak it in place, check it for accessibility and usability, and send your coding agent the exact change.
01Inspect
Click anything on a live page. Read its measured values, then change them in place.
img · 307 × 230 → 307 × 26402Responsive
See every device size at once.
1280 → 768 → 390 → 37503Localize
Open the site’s Arabic version, then check how it holds up.
lang="ar" dir="rtl"04Extract and Audit
Values read from the rendered page. Findings checked against WCAG 2.2 and the ten usability heuristics.
--color-accent: #2554C7;05AI mode
Pick an element and ask. Its measured styles go along as context.
Our AI, with no key, is coming soon.
button · padding 12px 20px → ask06And more
Pick a color and know everything about it.
Press ? for all 48 shortcuts.
#A797FF → 50 to 950 · 5.06:1Three example sites with the real toolbar on top. Click anything to change it, press K to scale, or open any tool. Each change is written below as code.
Your edits, as code
Change something above and it shows up here.
Inspecting needs a mouse or trackpad, so on a phone this demo is a preview. Open this page on a computer to select and edit the example site, or add the extension to try it on any site.
The extension’s real tools, on example sites. Nothing is sent, and edits reset when you reload.
@theme {:root { --color-accent: #23465C; --color-surface: #F4EFE7; --color-text: #221D18; --font-display: "Iowan Old Style"; --radius-button: 999px;}A spec, tokens and a prompt: the work leaves the browser as code.
One scan reads the rendered page into six tabs, with measured values. Below: the scan of Halden, the example site.
JSCSSWhat step 1 read, as tokens in the format your project uses. This is real exporter output for Halden.
/* color */
--color-accent: #23465C;
--color-surface: #F4EFE7;
--color-text: #221D18;Prompt from edits writes what you changed on the live page as a prompt tuned for the tool that builds it, with the exact before and after values. Pick a tool to see exactly what it gets.
Your edits
h1.hero__title font-sizea.button--primary radiusExample edits on the Halden demo site.
Prompt from edits
Your tool
7 DAYS OF EVERYTHING · THEN FREE OR PRO
Every install starts with the full extension and no card. After day 7, Free stays free and Pro unlocks the full power of each tool.
$0free forever
The essentials, with limited options in each tool.
Add to Chrome$12every 3 months
$49$39once · first 100 buyers
Cancel any time. Pro keeps working until the period you paid for ends.
One payment, every Pro feature as it grows. Then $49.
Start your 7 daysPrices are in US dollars. Payments, receipts and tax are handled by Polar. A license works on up to 3 browsers. Refunds within 14 days of the first payment: write to support. Lifetime covers Pro features of the extension; a hosted AI, if we ever offer one, would be priced separately. “Add to Chrome” opens the Chrome Web Store listing.
Scans, edits, audits and prompts run on the page in your tab. No account, and unless you use Your AI, nothing about the pages you open is uploaded.
Anonymous feature counts are on by default, after a notice: never URLs, page content or what you type. Switch them off in Settings, under Privacy.
AI mode and Audit with AI send your message and the context you keep on straight to your provider or server, after you agree once. Localize uses your AI only if you choose it.
Still curious?
Get in touch
Visible page structure, colors, typography, spacing, radii, shadows, visual assets, design tokens, technology signals, and detectable UX and accessibility concerns, the ten usability heuristics, and loading and stability measured on the page you have open. Results depend on what the browser can access: a very large page is read from its first 1,200 elements, and frames from other sites aren’t read. The extension says so wherever this applies.
Yes. The live inspector supports temporary, browser-side visual experiments. It does not change a website’s server, repository, or published content. Playground changes are contained in this page and reset on reload.
Yes. Copy element takes one element, with its look, from a site you open with Inspect, and Paste element puts it on another site, in your tab only. One click makes the paste take on that site’s colors, type and buttons, and another brings back the style it was copied with. Copy code gives you the element’s working HTML and CSS instead, with notes on what the page does with it. Nothing leaves your device.
Yes. Prompt from edits, in the panel, lists each change you made with the inspector, before and after, written for the AI tool you choose. In the playground it reads your edits to the example sites.
Yes, in your tab, never on the site itself. With your own key (Anthropic, OpenAI or Google Gemini) or your own server, pin notes or pick an element and ask. Your AI’s edits apply at once and one Undo reverts them all; it asks first when more than 10 elements would change or content would be hidden. If a model is busy, another from your key answers, and the answer says which. Copy as CSS or Create prompt takes the change to your code. Where your provider lists prices, Settings can limit AI to free models, and for OpenRouter it can ask for providers that don’t keep what you send, which leaves fewer free ones. Page details go only to the provider you choose, after you confirm. The playground here sends nothing: it previews the answers locally.
It is made and tested for Google Chrome 116 or later on a computer. Other Chromium browsers that install extensions from the Chrome Web Store may work but aren’t tested. Firefox and Safari aren’t supported. The interface is in English and Arabic (right to left).
Yes. Everything on this page is free today, including AI mode and Audit with AI on your own key or server. Our AI, which needs no key, is coming soon.
Anonymous usage counts are on by default, after a notice: which features you use, never URLs, page content or what you type. Switch them off in Settings, under Privacy. With Your AI, your message and the context you keep on go straight to your provider, only when you send. The privacy policy has the details.
No. Each finding is checked against a WCAG 2.2 criterion or a usability heuristic and linked to its element, but automated findings are assistance, not certification. Manual testing, assistive-technology testing, and contextual human review are still needed.
Open a page. Notice a detail. Try a direction.
Make Browser Extractor part of how you work.