All work
Browser extension · 2026

Smart UI Decompiler

A Chrome extension that decompiles any web UI component into standalone, Tailwind-compatible HTML that runs 100% offline — WebGL and 3D backgrounds intact.

Type
Browser extension
Year
2026
Stack
JavaScript · Chrome Extension APIs · DOM
JavaScriptChrome Extension APIsDOMWebGLCSP / background workers
Smart UI Decompiler
The problem

Reusing a UI component from a modern site means fighting dynamic styles, CSS variables, CSP policies, and WebGL/3D backgrounds that never survive a copy-paste. Extracted components collapse or break the moment they leave the original page.

Constraints
  • 01

    Sites actively resist extraction: CSP blocks fetches, WebGL scenes check origins, 3D backgrounds live in hidden iframes.

  • 02

    Dynamic layouts (Framer-style animations) don't survive static export.

  • 03

    The output must run from a local file with zero network.

What was built
  1. 01

    A picker that isolates exactly the targeted element (no sibling fetch), reads live dimensions via getBoundingClientRect, and freezes layout into static inline styles.

  2. 02

    Environmental shock protection: the extractor carries custom CSS variables, root classes, and html/body styles into the compiled document so dark mode and typography survive.

  3. 03

    Unicorn Studio WebGL scenes are intercepted, their scene JSON packaged into the document, and rendered locally; Spline 3D backgrounds are detected in hidden iframes, cloned, and re-stacked.

  4. 04

    Full-document sandbox mode for extracting inside Webflow/Framer canvases, plus a one-click full-page downloader.

Engineering decisions

CSP bypass via message passing

Content scripts can't fetch scene JSON when the page's CSP blocks it — the fetch is delegated to the background service worker, which isn't bound by the page's CSP, then the result is embedded as a local script.

Every decision documented

The repo includes a written case study covering the five core challenges (origin protection, WebGL recovery, style flattening, layout freezing, iframe re-stacking) — engineering decisions are written down, not just shipped.

Result
  • ✓

    Extracts from sites that actively resist extraction (Framer, Webflow, Unicorn-powered pages, Spline 3D) into single offline HTML files.

  • ✓

    Case study committed alongside the code documents each challenge and its solution.