NSC Labs

Chrome Extension • Local-first

See what the active page rendered.

WebLens Page Lens creates a bounded, copyable evidence packet from the active browser tab. It shows rendered page facts, browser messages collected after Page Lens starts, and suggested review boundaries without claiming a verdict.

How Page Lens works Read the privacy policy

What it shows

A small browser evidence packet, not a scanner.

WebLens is designed for developers, site owners, support teams, and AI-assisted debugging workflows that need a clean account of the active page.

Rendered page evidence

URL, title, viewport, document size, links, images, broken rendered images, canonical URL, meta description, and other bounded page facts.

Console evidence

A bounded set of console errors and warnings from the active tab, collected only after Page Lens collection starts.

WordPress / browser hints

Browser-visible references such as plugin paths, theme paths, wp-json, WooCommerce, Elementor, cart, checkout, nonce, REST, CORS, and explicit HTTP status references.

Discrepancy hints

Suggested review boundaries based on combinations of rendered and console evidence. These are not findings, causes, or verdicts.

AI-ready copy

Copy one clean evidence packet into an issue, support request, or AI assistant without pasting a full browser console or source tree.

Manual by design

WebLens does not crawl the site, click controls, submit forms, or run in the background. The user chooses when Page Lens runs.

How it works

Run it only when you need evidence.

  1. Open the page you want to inspect. WebLens works on published and locally hosted pages.
  2. Open WebLens and press Run page evidence. This collects rendered facts and starts bounded console collection.
  3. Interact with the page if needed. Use the page normally to reproduce the browser behavior you want to review.
  4. Reopen WebLens and run Page Lens again. Messages collected after the first run can now appear in the packet.
  5. Copy the evidence packet. Use it in an issue, support request, or AI-assisted debugging session.

Optional developer mode

Add local source context only when it exists.

WebLens works on published pages without any additional software. Developers working with local source files may optionally run the local WebLens helper. The helper serves one selected directory and can add bounded local source context from the same device.

The Chrome extension does not contact the helper when the popup opens. Local source context is checked only after the user opens the optional section and explicitly requests it. 

Published page
→ Chrome Page Lens
→ Browser evidence packet

Local project available
→ Optional localhost helper
→ Local source context

No account
No cloud service
No automatic upload

Privacy policy

Evidence stays on the user’s device.

WebLens Page Lens processes browser evidence locally and does not send it to NSC Labs, analytics providers, advertisers, AI services, or other third parties.

Information WebLens may process

WebLens reads limited information from the active browser tab only after the user invokes the extension. This may include:

  • the active page URL and title;
  • rendered page metadata and bounded visible text;
  • bounded resource and form references;
  • bounded console errors and warnings collected after Page Lens starts.

How the information is used

The information is used only to create the evidence packet displayed in the extension popup and copied by the user.

What WebLens does not do

  • WebLens does not upload page evidence to NSC Labs.
  • WebLens does not sell user data.
  • WebLens does not use analytics or advertising trackers.
  • WebLens does not create user accounts.
  • WebLens does not track or retain browsing history remotely.
  • WebLens does not send page evidence to AI services.
  • WebLens does not crawl websites or automate browser actions.

Optional localhost helper

The optional local WebLens helper communicates only with localhost addresses on the user’s own device. The extension checks the helper only after the user explicitly requests local source context. Source context is not transmitted to NSC Labs.

Retention and sharing

WebLens does not retain evidence on a remote server and does not share evidence with third parties. The user may choose to copy and share an evidence packet outside the extension.

Policy updates

Material changes to this policy will be published on this page with an updated date.

Last updated: July 10, 2026.

Support

Questions or Chrome Web Store support

For product questions, bug reports, or privacy requests, contact NSC Labs through newssourcecrawler.com.