What this workspace does
Page-numbered decoded values from the local PDF.
File scanner · browser local
Scan QR codes inside a PDF without sending it away
Choose a PDF to render its pages locally at a practical scan size. Aftermath checks every page it can process and lists any codes it finds.
Use it accurately
Very large or damaged PDFs can exceed browser limits. Decoded URLs are displayed but never opened automatically.
Private browser processing
Selected files are processed in the current browser session. Aftermath has no account, cloud file storage, or server-side file-processing job.
What this tool checks
Scan supported PDF pages for QR codes locally when a document may contain one or more values to review. The browser renders bounded page previews, lists page-numbered decoded values, and never opens a decoded link automatically. Rendering limits, low-resolution codes, and unusual PDF content can prevent detection, so verify the document manually when it matters.
What to choose and what you get
What to choose
- one local PDF selected or dropped for page rendering
Result
- page-numbered decoded QR values displayed for review and copying
Supported use
- QR codes visible on locally rendered PDF pages
- Review of multiple page-numbered QR results from one document
Before you start
- The scanner does not modify the PDF or return a PDF download.
- Non-QR barcode formats and image-batch intent belong to dedicated sibling routes.
Supported formats
- Accepted formats: PDF.
- Output formats: on-page text.
Browser support and permissions
- Modern browser with JavaScript; flat PDF features, page limits, and available browser memory apply.
- No camera, microphone, or screen permission is needed.
Choose the right settings
- Use this route when the source is a PDF and page numbers matter in the result.
- Use /qr-code-scanner-from-image for one saved image or /scan-qr-code-from-screenshot for a screenshot.
- Use /barcode-scanner-from-image when the intended result may be a non-QR barcode format.
Worked example
A multi-page PDF may contain QR codes on several rendered pages and their page numbers need recording.
Starting facts
- The PDF is readable and can be rendered locally.
- Only visible rendered QR patterns can be detected.
Observed operation: Render pages under the route limits, scan each rasterized page and report decoded values with page numbers.
Review the result: Review every page-labelled value as untrusted text and inspect pages where expected codes were not detected.
Boundary: The scan cannot prove that all codes were found or that any decoded destination, document or instruction is safe.
What you can do
Find QR codes on rendered PDF pages
Choose another tool when
- This route does not create, edit, merge, split, or normalize a PDF.
- It is not the single-image, screenshot-first, batch-image, or general barcode reader.
If it does not work
- A damaged, protected, or unsupported PDF cannot be rendered in the browser.
- A QR code is too small, blurred, low-contrast, or incomplete at the bounded render size.
- A code appears beyond the PDF page limit enforced by the bundled scanner.
Things to know
- The bundled PDF scanner checks only its configured leading-page range and reports when that limit is reached.
- Rendering and detection are bounded by browser memory, canvas, and file limits.
- Decoded values are not proof of authenticity, and links are never opened automatically.
Privacy boundary
Selected PDF bytes stay in the current browser session and are not sent to an Aftermath processing service. How local processing is verified.
What this tool verifies
Checks the displayed limits and reports or creates page-numbered decoded QR values displayed for review and copying from one local PDF selected or dropped for page rendering.
Check before sharing
This route does not create, edit, merge, split, or normalize a PDF.