Pablo: Chrome extension that extracts HTML and CSS from any website element

What it does

Pablo is a Chrome extension that captures the HTML and CSS code from any website element. Users hover over a component, click it, and the underlying code copies to their clipboard. The tool extracts computed styles, font files (including @font-face declarations and Google Fonts links), CSS keyframes, and animation properties from libraries like GSAP and Framer Motion. The extracted code is formatted to paste directly into Claude Code, Cursor, or other development environments.

Who it is for

Web designers and developers who want to rebuild UI components they find on live websites. The tool targets people working with modern design tools and frameworks who need to reverse-engineer visual components quickly rather than rebuild them from scratch. Anyone doing competitive research or component exploration on the web could benefit.

Pricing

The site does not show prices. The extension is described as free with no backend or host permissions required.

How it stands out

Pablo focuses on the extraction and clipboard workflow rather than a cloud-based service. By running entirely as a Manifest v3 Chrome extension with no backend, it avoids dependencies and permissions issues. The tool explicitly handles modern animation frameworks (GSAP, Framer Motion, Webflow IX2) that many simpler inspector tools miss. Formatting output for AI code editors like Claude Code suggests a specific workflow: extract, paste, regenerate in your own stack.

What a founder should check

First, verify the actual scope of what can be extracted. The homepage shows comparison sliders with "Original" and "Copied with Pablo" examples, but it is unclear how reliably the tool handles complex nested components, dynamic content, or CSS-in-JS approaches beyond the listed frameworks. Second, assess switching costs: competitors like browser DevTools, design inspection plugins, and manual code copying are already built-in or free, so the value proposition relies entirely on speed and output quality. Third, understand the moat: if extraction is straightforward for modern components, similar tools could emerge quickly. The positioning around AI code editors may be temporary if those platforms build extraction features natively.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.