Can I inspect a public website’s source?
Publicly delivered browser code is visible, but permission and acceptable-use rules still matter. Clean room provides a safer default when your task is to learn from visible behavior.
Website inspection · Updated November 2026
Inspect a website before rebuilding it by recording the visible page system first: layout, text, typography, color, responsive changes and interaction states. Switch to deeper source inspection only when you own the site or have explicit permission.

Inspect the page hierarchy, visible content, layout system, typography, colors, spacing, responsive changes and interactive states. These are the elements an AI agent needs to reconstruct behavior without relying on guesswork.
Start with the experience a visitor receives. Identify the primary navigation, page sections, calls to action and content order. Measure the widths at which the layout changes. Record which components collapse, hide, reorder or become scrollable on smaller screens.
Then examine states. Navigation menus may open, forms may validate, cards may filter and video may load. The default page view rarely shows these behaviors. Screenshots and notes for each important state give the coding agent a much better brief than a single polished hero image.
Use Clean room when you only have permission to view the website as a user. Use Deep mode only for software you own or are explicitly authorized to inspect internally.
Clean room keeps the work visible and supervised. It can capture screenshots, visible text, measured layout and interaction states but refuses tools that would read the original’s code or files. That constraint makes the rebuild more like a design study than a source-code copy.
Deep mode is appropriate for maintenance and migration work on an owned property. It can inspect JavaScript, files and internal implementation details with the supported tools. It is not a license to bypass authentication, DRM or access controls, and it is not an operating-system sandbox for the coding agent.
Record each observation with enough context that another person can understand what it proves. Separate observed facts, inferred intent and unresolved questions.
A screenshot without a viewport size and page path is difficult to reuse. A layout note without the page state may be wrong. Name the page, viewport, state and observed behavior. If a menu opens after a click, capture both closed and open states instead of describing one from memory.
Craft Anything stores project captures and investigation evidence in the project folder. That ledger gives the coding agent a stable reference and lets a human review why a design decision was made. It also exposes gaps: missing hover states, unvisited pages or unknown form validation should remain marked as unknowns.
Group evidence into templates, components and behaviors, then give the coding agent a scoped build order. Ask for reusable systems instead of page-by-page visual patches.
Start with the shared shell: header, navigation, footer, page container and responsive behavior. Then build the highest-value templates. Identify repeated cards, forms, buttons and content blocks that should become components. This reduces duplicated CSS and makes later refinement easier.
The brief should include the target stack, content rules, accessibility requirements and what may not be copied. For a migration, include known internal constraints from the owned source. For a clean-room study, state that the agent must work only from captured visible evidence.
The most common mistakes are capturing only desktop, ignoring interaction states, treating visual similarity as correctness and failing to document permissions.
A full-page screenshot can hide fixed headers, hover states, focus rings and mobile navigation. It also encourages the agent to infer spacing from a compressed image. Capture components in context and record viewport dimensions.
Authorization is another frequent gap. Teams may be allowed to inspect a public design but not to reproduce its photography, copy or logo. A responsible rebuild brief replaces protected assets and records the source of every asset that remains.
These are the practical questions people ask before choosing a workflow or starting a rebuild.
Publicly delivered browser code is visible, but permission and acceptable-use rules still matter. Clean room provides a safer default when your task is to learn from visible behavior.
Named page routes, viewport-specific captures, component behavior and explicit unknowns are more useful than a large unlabeled screenshot collection.
Yes. Project folders keep captures and investigation evidence so the build and its checks can be reviewed later.
Compare the plans, create your account and continue into the Craft Anything workspace. The desktop app remains available separately for local inspection and agent work.
Product and competitor claims were checked against first-party documentation on November 16, 2026. This article compares documented workflows; it does not claim independent benchmark results.
Corrections: hello@storyteller.ai