When this tool is useful
Email previews, thumbnails, slides, and systems that accept images but not PDF documents.
How local processing works
PDF.js renders each selected page to a browser canvas; the canvas is encoded as JPEG at the chosen resolution and quality.
How to use it
- Choose the source files.
- Review the available settings and page order.
- Process locally, inspect the result, and download it.
Important limitations
Text becomes pixels and is no longer selectable. Password-protected, damaged, or extremely large PDFs may not open.
Verify the downloaded result
Reopen the downloaded file in its destination application, check dimensions or page count and visible content, and keep the source until the result has been accepted.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
Does this tool upload my files?
No. Processing happens in your browser; closing the page clears the working session.
Will the output always match the source exactly?
Text becomes pixels and is no longer selectable. Password-protected, damaged, or extremely large PDFs may not open.
What should I check before using the result?
Reopen the downloaded file in its destination application, check dimensions or page count and visible content, and keep the source until the result has been accepted.
Which browsers and devices are supported?
Use a current browser with JavaScript, workers, canvas, WebAssembly where the format requires it, Blob downloads, and enough memory. Reopen important downloads in the destination application.
Concrete input and output example
Input pages 2–4 of a 12-page report and render at 2× scale. The output is three JPG files (or a ZIP); text, links, vectors, and annotations on those pages become pixels.
Browser compatibility notes
Reviewed against the implementation and required web APIs on 2026-08-12. Use a current browser where these APIs are available and verify important output on your device.
- Chrome / Edge (current desktop)
- Requires local PDF parsing, worker/canvas APIs where applicable, document creation, and Blob download.
- Firefox (current desktop)
- Uses the local PDF workflow; always verify the generated download in its destination viewer.
- Safari (current desktop)
- Uses the same local workflow; large page sets can have a lower practical memory ceiling.
A tool-specific question
Can I select text in the JPG output?
No. Rendering deliberately turns each page into a pixel image; use split or organize to keep PDF page objects.