Frequently asked questions
Why did a long capture produce multiple PNG files?
Browsers limit the dimensions and memory of a single image. PageCapture
uses numbered PNG segments when one safe image cannot contain the whole
result. PDF output continues the same captured content across pages.
Why did capture stop before an infinite page ended?
Loaded content only intentionally stops at the page length measured when
capture starts. Keep loading follows newly appended content, but a truly
infinite page still stops at frame, time, image-size, or memory safety limits
and returns a marked partial result when it is usable.
Why is Copy to Clipboard unavailable?
Clipboard copy needs a browser-supported single-image result and your click
in the Result View. Split results should be saved as PNG or PDF. The Result
View shows the specific reason when the browser blocks Clipboard access.
Why can’t I capture Chrome pages or the Web Store?
Chrome protects internal pages, the Chrome Web Store, some PDF viewer
surfaces, and inaccessible cross-origin frames. The extension does not
bypass those security boundaries. Chrome’s built-in PDF viewer supports
Visible Area Screenshot only.
Where is the screenshot processed?
Capture data is processed locally in your browser. Long jobs may use
extension-private temporary IndexedDB storage, which is cleaned after
completion, cancellation, failure, Result View close, or session expiry.
The extension does not upload captures to a publisher server.
Contact
Feature requests and improvement ideas are welcome. We review them and apply
feasible improvements as quickly as possible. For a bug, include the extension
version, Chrome version, operating-system type, capture mode, visible error
code, and steps to reproduce.
Email: abcdejoji@gmail.com
Do not send passwords, authentication tokens, private email, confidential AI
conversations, or unredacted work screenshots. A capture file is never required
to ask for help, and the extension never attaches one automatically.