CaptureGuide
5 min read
Why Chrome says "Page Scanner started debugging this browser"
The bar is Chrome's own notice that an extension is using its debugger. Page Scanner attaches it for the length of one scan, to lay the page out once and take the PDF from that layout, and the capture never leaves your machine.
The bar at the top of the window is Chrome's, not Page Scanner's. Chrome shows it whenever an extension attaches its debugger to a tab, and Page Scanner attaches it for one reason: the debugger is the only way an extension can reach Chrome's own print-to-PDF pipeline, which is what makes the PDF's text real text rather than a picture of text. The bar appears when a scan starts and goes away about five seconds after the scan finishes, which is Chrome's own delay; the editor says so while it is still up. Nothing is inspected, and the capture never leaves the machine.
What the bar says
Chrome puts one line under the address bar, in a bar of its own, with a Cancel button at the right:
"Page Scanner" started debugging this browserIt is Chrome's wording, and Chrome shows the same line for any extension that uses the debugger, with that extension's name in the quotes. Pressing Cancel detaches the debugger, which ends the scan; scan again when you want the capture.
What the debugger is used for
One attachment, one layout, two outputs. While the debugger is attached, Page Scanner lays the page out once at its full height, then takes two things from that single layout: a screenshot, which is the preview you crop in the editor, and Chrome's print-to-PDF output, which is the file. Because both come from the same layout, the crop you draw on the preview lands exactly on the PDF.
Without the debugger, an extension can only scroll the page a screen at a time and stitch the screenshots together. That gives a picture of the text, not the text. Page Scanner does exactly that as a fallback when the debugger cannot attach, most often because DevTools is already open on the tab, and the editor's Output Format panel says that such a capture's text cannot be selected. Close DevTools and scan again to get a vector capture.
Why it cannot be hidden
The bar is drawn by Chrome for any extension that uses the debugger API, and no extension can
suppress it. Page Scanner does not try to, and no setting hides it: the settings'
Explain Chrome's debugging bar switch only turns off the editor's card about it. The one
thing that turns it off is a command-line switch on Chrome itself, --silent-debugger-extension-api,
which exists for automated test setups; Page Scanner does not ask you to use it.
What it does not mean
Chrome's wording says "debugging this browser", and what is happening is narrower than that: the debugger is attached to the one tab you scanned, for the length of that scan, and detached the moment it is done. Page Scanner never watches pages you have not scanned, and it asks for no host permissions, so it has no standing access to any site. Until you connect local agents, it does not run in the background and has no access to any other tab.
Connecting local agents, with Connect in the settings' Local Agents section, changes two of those. Page Scanner's helper on your computer then keeps the extension running in the background for as long as the browser is open, and a program on your machine that holds the pairing, such as the command line or an AI agent through the MCP server, can list your open tabs, capture one, or give an address that Page Scanner opens in a background tab, in a green Page Scanner tab group, and closes after the scan. The debugger is still attached only for each scan, and the connection stays on your computer. Disconnect ends it.
There is no account, and the capture is never uploaded. It is written to the extension's own storage in your browser so the editor tab can open it, and anything older than 12 hours is deleted the next time the extension starts. Of the network requests the extension makes, which the privacy policy lists, two matter here. One is anonymous usage statistics sent to Google Analytics: that a scan ran and how it ended, which export options were chosen, never the address, title or content of a page. They are on by default, and switching off Report usage statistics in the settings stops them. The other is an optional bridge for a program on your own machine, which stays on that machine and is off until you connect it.
These are the permissions the extension asks for, as the privacy policy lists them:
| Permission | Why it is needed |
|---|---|
activeTab | Grants access to the one tab you scan, at the moment you click the icon, and to nothing else. |
debugger | Lays the tab out at its full content size and takes the full-page screenshot and the vector PDF from that one layout. This is the capture, and it is the only Chrome API that can produce a real vector PDF of a whole page. |
scripting | Measures the page's full height, and drives the scroll-and-stitch fallback used when the debugger cannot attach (for example when DevTools is open). |
storage | Remembers your light/dark theme, your capture and editor settings, the bridge pairing, and the usage statistics' random id and on/off choice, on this device. |
favicon | Shows the scanned site's icon in the editor, read from Chrome's local favicon cache. No request leaves the browser. |
nativeMessaging (optional) | Lets the extension talk to Page Scanner's helper on your own computer, for the local agent bridge. Asked for only when you press Connect in the settings. |
tabGroups (optional) | Names and colors the green Page Scanner tab group a tab opened for a local agent goes into. Asked for with Connect in the settings. |
What the mechanism costs
The limits that come with capturing this way, as the extension's own feature record states them:
- Chrome shows its own "started debugging this browser" bar for the length of a scan, and it cannot be suppressed.
- With DevTools open on the tab the capture falls back to stitching screenshots, and the Output Format panel says the PDF's text cannot be selected.
- Only one debugger can attach to a tab at a time.
chrome://pages, the Chrome Web Store and other extensions' pages cannot be scanned.