About Scan to PDF
Scan to PDF captures still frames from a device camera, detects a likely document quadrilateral after capture, lets you adjust its four corners, applies perspective correction and an optional enhancement, then assembles the accepted captures as PDF pages. Choose A4, Letter or Match capture and Auto, Color, Grayscale or Black & white enhancement. The output is image-only until OCR is run separately.
Scan to PDF specs
| Price | Free ($0) — no paid tier |
|---|---|
| Account | Not required |
| Watermark | None |
| Where it runs | In your browser, on your device |
| File upload | No file is uploaded |
| Input | Photos captured with your device camera |
| Output | |
| File size limit | Limited only by your device's memory |
| Offline use | May work after all required code and assets have loaded; browser caching is not guaranteed |
How to use Scan to PDF
Start the camera
Press Start camera and grant browser permission. Capture requests the rear-facing camera when available.
Capture and adjust
Press Capture, inspect the detected outline and drag any corner that is wrong.
Add or discard
Add page commits the corrected capture; Discard returns to the camera. Repeat for more pages.
Download PDF
Review the captured-page thumbnails, remove mistakes, and press Download PDF.
Frequently asked questions about Scan to PDF
Does edge detection run continuously?
No. The live camera helps framing, but quadrilateral detection runs on the captured still. You confirm or correct the corners before adding that page.
Does Scan to PDF recognise text?
No. It creates image pages. Run OCR PDF afterwards for a searchable layer, and proofread the recognised result.
What leaves the device?
The component reads camera frames and processes captures in browser memory; it has no file-upload step for them. Camera permission remains governed by the browser and can be revoked in site settings.
Why in-browser processing matters
Every PDFChamp tool runs inside this page: the file you choose is read by JavaScript in your own browser and is never sent to a server, so nothing is uploaded, queued, or stored anywhere. That removes the upload wait, the processing queue, and the question of what happens to your file afterwards — the PDFChamp overview compares this architecture with server-side PDF tools.
Last updated