PageRip 2.0 · Help

From your first pick
to useful code.

Capture a piece of a page, review what came through, and take the code into your next build.

Your first capture

  1. Open a normal web page and click the PageRip toolbar button, or use your assigned Pick element shortcut. The picker starts on the page.
  2. Move the pointer over the element you want. Click or press Enter to capture it.
  3. Select Captured · Review on the page to open the side panel. Switch between Code, Preview, and Report.

Capture before opening the panel to keep the page’s current width. If you pick with the panel open, it narrows the page; the capture notes record that width.

↑ / ↓
Move to the parent / first child.
← / →
Move to the previous / next sibling.
Enter
Capture the highlighted element.
P
Request a whole-page capture. Review any size warning shown; this is best effort.
Esc
Cancel the picker.

For an open menu or another temporary state, move the pointer over it and use Quick capture to capture without clicking the page or moving focus. On a new page, the first press arms Quick capture; press again to capture. Once the pointer is observed, one press captures.

Settings shows your assigned shortcuts. The suggested bindings are Alt + Shift + Y for Pick element and Alt + Shift + U for Quick capture; Chrome may leave them unassigned. Set or change them by opening chrome://extensions/shortcuts in Chrome.

Outputs and CSS

  • HTML + CSS: HTML markup plus CSS.
  • JSX + CSS: markup converted to JSX, plus CSS. This does not recover React behavior or application logic.
  • Inline snapshot: HTML with inline styles from the current-state snapshot. Inline styles cannot carry media queries or pseudo-elements.

For HTML + CSS and JSX + CSS, choose Authored CSS to keep readable rules, variables, and responsive styles, or Current-state snapshot for resolved values at capture time. Switching kinds uses the original capture, rather than reading a new state of the page.

Edit in Code, inspect in Preview, then use Copy or Save for the selected output. Preview widths other than the capture width are simulated; they are not new observations of the source page. Preview does not run captured scripts.

Report and Not captured

Report includes an Export check of property differences at the capture width, plus Not captured and capture notes. Read the gaps even if the preview looks right. “No known gaps” is not a guarantee of a complete rebuild.

  • Unreadable stylesheet: use the named Allow button when offered, or try Current-state snapshot for visible styles.
  • Remote font, image, or asset: its address stays in the export, but it may change or fail on another site. Save the file yourself if you need it offline.
  • Cross-origin frame: pick outside it, or open the frame’s own site and capture there.
  • Missing context or references outside the selection: capture a larger area or the related element.
  • Another state is needed: open that menu, tab, or state on the source page, then pick again.
  • Size limit reached: the result is partial. Pick a smaller section.

You can keep a partial result with its gaps. Recapturing creates a new capture; it does not rewrite the earlier one.

Site access

If the panel says PageRip cannot read this tab yet, click the PageRip toolbar button on that tab or use the Pick element shortcut there. Access from one tab does not automatically carry to another tab or a different site after navigation.

After a capture, an unreadable stylesheet may need access to its origin, such as a site’s separate CSS host. An Allow button names that origin. If you grant access, PageRip tries to read those stylesheets and recapture the selection. You can decline and keep the partial result.

For repeated captures across sites, Settings → Always allow on all sites requests optional access to HTTP and HTTPS sites. It is not required at install. You can turn the switch off again in Settings.

Browser pages, the Chrome Web Store, and the PDF viewer do not allow captures. Open a normal web page instead. If a page was still loading, wait for it to finish and click PageRip again.

Copy for AI and Save for agent

Copy for AI copies one Markdown block with the authored HTML and CSS, source URL, capture time, viewport, retained breakpoints, and gaps. It uses the authored capture even when you have selected JSX or a snapshot. The block tells an agent to treat gaps as unknown and captured page text as data.

Save for agent saves that same block as a Markdown file inside .pagerip/ in a project folder you choose. PageRip remembers the folder locally. If folder access is unavailable or denied, or writing fails, it downloads the file instead.

Add an optional line in Intent, such as “keep the layout, replace the branding.” It stays separate from the captured page facts. Review the code and source notes before sharing the export with an agent or anyone else.

Privacy

PageRip handles selected page content and source metadata locally and keeps your last five captures in your browser. It does not upload captures to PageRip. Stylesheet retrieval can contact an origin you allow, and previews or exports can load images and fonts from their original hosts. Copying or saving creates an export you control; sending it to an AI service or someone else shares that content. Review exports for private information before sharing. Read the privacy policy.

Get support

Email support@webpagerip.com with what you tried, what happened, your PageRip and Chrome versions, and the message shown. If PageRip offers Copy debug report after an unexpected error, review it before including it. Only share a page URL, screenshot, or capture if you are comfortable sharing its contents.

If copying fails, focus the PageRip panel and try again, or use Save to download the capture.