Help center

Support

Answers for common packaging and retrieval issues.

Start here

Quick checks

No PDFs were detected

Confirm that the webpage contains direct HTTP or HTTPS links ending in .pdf or embedded PDF resources. Links that open a custom viewer instead of a direct file may not be detected.

Chrome asks for site access

This is expected. Access is requested only for the domains hosting the PDFs you selected. Job-acquired access is removed after completion, cancellation, workspace close, or the next browser startup.

The ZIP did not download

Check Chrome’s Downloads page for a blocked or interrupted download. Then retry with fewer or smaller files and keep the packaging workspace open until the job finishes.

Manifest results

Understanding retrieval errors

Result What it means

Not a PDF The server returned a login page, error page, or other non-PDF content.

HTTP error The host rejected or could not complete the request.

Timed out The file did not finish responding within 60 seconds.

Duplicate The bytes matched a file already stored in the package; the duplicate remains documented in the manifest.

The extension does not send cookies, use login credentials, bypass paywalls, or defeat access controls. Some hosts intentionally block extension requests.

Version 0.1

Free beta limits

25PDFs per job
100 MBMaximum per PDF
300 MBStored PDF bytes per ZIP
60 secRetrieval timeout per file

A SHA-256 checksum shows whether file bytes match. It does not prove authorship, legality, or authenticity.

Still need help?

Report a problem

Use the support contact shown on the PDF Evidence Packager Chrome Web Store listing. Include:

Your Chrome version
The public source-page URL, only if it is safe to share
The exact error shown in the packaging workspace

Never send private PDFs, signed URLs, access tokens, or passwords.