--- title: Browser extension description: Comment on the current web page, then publish it as an HTML artifact. slug: /docs/browser-extension group: publishing updatedAt: 2026-08-15 --- Use the Display.dev Chrome extension to review the page open in your browser and publish its current rendered state. ## Install and sign in Install **Display.dev browser extension** from the Chrome Web Store. Select its toolbar icon on a normal `http://` or `https://` page, then choose **Sign in to display.dev**. Complete the sign-in screen for the organization that should own the artifact. Chrome does not let extensions run on browser settings, the Chrome Web Store, or other protected pages. Open an ordinary web page before starting a review. ## Add comments Select at least three characters of visible text. When the extension says the selection is ready, choose **Add comment**. Add the direction you want to keep with that passage. A review can contain up to 50 draft comments. Comments can target text in the main page and text slotted into a component. Text inside a component's shadow root cannot be targeted in this version. Select nearby page text instead, or publish without that comment. Draft comments stay in the current tab until publishing starts. Reloading, navigating, closing the tab, or closing the browser before then can lose them. ## Preview and publish Choose **Publish page** to set the artifact name and audience. Company is the default. Private is available when your plan permits it, and Public must be selected explicitly. You can publish with no comments. **Preview capture** shows the inert result before it is sent to Display.dev. The published artifact does not run the source site's JavaScript. Safe CSS motion and browser-native links, same-page anchors, details, scrolling, hover, focus, and narrowly scoped CSS toggles can remain. When motion is preserved, viewers can pause or resume it from the artifact. Forms, downloads, popups, and scripted behavior stay blocked. Replacing its complete source later follows the ordinary HTML artifact behavior. The extension captures only content already loaded in the current page. It does not scroll, open menus, or trigger lazy loading. It removes form values, scripts, frames, unsafe URLs, URL query strings, and HTTP subresources. To keep the result visually closer to the page, Preview and Publish can embed a bounded copy of an eligible loaded public WOFF2 font. That request omits page credentials and the referrer and does not follow redirects. The font host can still see your IP address and request time. A font that cannot be embedded remains a public HTTPS fallback only when its accessible stylesheet can be safely copied; otherwise it can look different or be missing. Already-loaded images whose effective URL contains a query, fragment, or `blob:` URL, and eligible current video frames, are copied from their visible pixels without another asset request. Query-dependent CSS backgrounds use a readable fallback. Closed custom elements, partially visible or below-fold elements, cross-origin frames, and unreadable pixels are not rasterized. The capture uses a measured placeholder and warning when an eligible visual cannot be preserved. Accessible linked stylesheets are copied through the sanitizer; unreadable linked stylesheets are omitted. Remaining query-free public HTTPS images, fonts, and assets referenced by copied CSS load from their original hosts when someone views the artifact. Open shadow roots are captured when the browser exposes them. Constructed stylesheets or manual slot assignment can produce warnings and a less accurate result. Closed shadow roots are not accessible and their missing content cannot always be detected. An HTTP page shows a warning because its styles, images, and fonts may be removed. Imported styles and assets that depend on a URL query may also be missing. Canvas content is always replaced by a measured placeholder. The extension does not inspect the source canvas context or take a screenshot of the page. The extension limit is 8 MiB. If embedded fonts or image/video snapshots make the page too large, the drawer offers **Capture with placeholders**. Select it and capture again to omit font copies and replace those pixels with measured placeholders. Use [Web upload](/docs/web-upload) for a larger exported HTML file. ## Recover an interrupted publish Once the artifact publish starts, an extension-owned recovery tab protects an unknown publish result or comments that remain unattached. It blocks another publish until you finish or clear it. - For an unknown artifact result, open display.dev and check before using **I checked display.dev – clear this**. Clearing discards the retained drafts. - For an interrupted comment run, open the artifact and choose **Resume comments**. Successfully attached comments are not repeated. - For an unknown comment result, check the artifact before clearing that one draft. - After a rate limit, resume after the time shown. - **Discard remaining drafts** removes comments that have not been attached. Recovery lasts for the current browser session. Closing Chrome clears it. If a definite publish failure occurs after the source tab is gone, the newest comment text may be offered when you reopen the page. Select replacement text for every recovered comment before publishing; old targets are never restored automatically. ## Continue with an agent Open the published artifact and use its existing edit handoff to pass the URL, source, and attached comments to an agent. The capture is rendered evidence, not the website repository source. The agent should inspect the repository before applying an approved change to the website code.