Report a bug
Open a structured GitHub issue with your Chrome version, operating system, and safe reproduction steps.
Create bug reportProduct support
Find quick troubleshooting steps or report a reproducible issue. UIRecast never needs your private page content to diagnose a public bug report.
Open a structured GitHub issue with your Chrome version, operating system, and safe reproduction steps.
Create bug reportReview exactly what website content is handled, where it is processed, and why each Chrome permission is needed.
Read privacy policyIf UIRecast helps your work, you can make an optional contribution through Stripe.
Make a contributionContributions do not unlock features, licenses, or priority support. Payments are processed by Stripe.
http:// or
https:// webpage. Chrome internal pages, the Chrome
Web Store, and other protected pages cannot be inspected.
chrome://extensions for a runtime error and
include only the non-sensitive technical message in your report.
Chrome blocks extension scripting on internal pages,
chrome:// pages, the Chrome Web Store, and certain
protected documents. Open a regular website and invoke the
extension from that tab's toolbar icon.
The output is a safe reconstruction of the selected rendered DOM. Responsive context, inherited page styles, pseudo-elements, dynamic states, animations, custom fonts, and external assets can require manual adjustment. Review the fidelity diagnostics shown in the side panel.
No. Browsers receive rendered output, not a site's private source project. UIRecast generates equivalent reusable code from the sanitized rendered element.
No. Selection, sanitization, preview generation, conversion, and ZIP creation happen locally in the browser. See the privacy policy for the complete disclosure.
Focus the side panel and press Esc, use the panel's close button, or choose the cancel action while selection is active.