About PDF to JPG
PDF to JPG rasterises every page of a PDF into a standalone JPEG image, so a document becomes a set of pictures you can drop into a slide deck, a CMS or a chat window. Rendering happens on your own machine: pdf.js draws each page onto an HTML canvas at the DPI you pick — 72, 150 or 300 — and the browser encodes that canvas as JPEG at your chosen quality. People reach for this when a printer asks for flat images instead of a live PDF, when a web form only accepts .jpg uploads, when they need a thumbnail of a report cover, or when they want to paste a page into an email without an attachment.
PDF to JPG 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 | PDF (1 file) |
| Output | JPG (one image per page) |
| 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 PDF to JPG
Drop the PDF in
Drag a single PDF onto the panel that reads "Drop your PDF here or click to browse", or click it to open the file picker. A thumbnail strip of every page appears as soon as the file parses.
Pick a DPI
Under the DPI label choose the 72, 150 or 300 chip. 150 is preselected; the number is a scale factor against the PDF's 72-point page grid, so 300 quadruples the pixel area of every exported image.
Set the quality slider
The Quality slider runs from 50 to 100 % and starts at 90. The percentage printed next to the label goes straight to the browser's JPEG encoder, so lower values shrink the file and soften edges around text.
Check the sample page
The "Pages to export" panel shows the page strip plus a larger sample of the selected page, with the page count, DPI and quality summarised above it.
Convert & download
Press Convert & download. The status line counts "Rendering page 3 of 12…" as it works, and each page saves as name-page-01.jpg — a one-page PDF simply saves as name.jpg.
Frequently asked questions about PDF to JPG
Which DPI should I pick when converting a PDF to JPG?
150 DPI is the right default for a PDF-to-JPG export, and it is what the tool preselects. The chip you pick becomes a scale factor against the PDF's native 72-point grid, so 72 reproduces the page at roughly its on-screen size, 150 doubles each dimension and 300 quadruples the pixel area — an A4 page goes from about 595×842 pixels to about 2480×3508. Choose 72 for a quick preview or a chat attachment, 150 for slides and web pages, and 300 when the JPG will be printed or cropped into. Higher DPI costs memory as well as disk space: each page is rendered into a full-size canvas before it is encoded, so a 300 DPI run on a long document is where an older phone is most likely to run out of room.
What happens to transparent areas when I choose JPG?
JPEG has no alpha channel, so transparency cannot survive. PDF to JPG explicitly paints the canvas white before pdf.js renders the page and before JPEG encoding, which makes unpainted regions predictably white. Use PDF to PNG when retaining unpainted transparency matters.
Does a 12-page PDF give me 12 separate JPG files?
Yes — PDF to JPG saves one JPEG per page and there is no option to bundle them into a zip. Files are named after your PDF with a zero-padded page suffix, so report.pdf becomes report-page-01.jpg through report-page-12.jpg, while a single-page document is saved as report.jpg with no suffix at all. The downloads fire one after another with a short pause between them, because browsers throttle rapid sequential saves. Chrome and Edge usually show an "Allow multiple downloads" prompt on the first multi-page run — accept it, or only the first image lands. If your browser silently blocked the rest, allow multiple downloads for the site in its permission settings, press Reset, and convert the document again.
What does the quality slider actually change?
The Quality slider sets the JPEG compression level the browser applies when it encodes each rendered page, from 50 % up to 100 %, starting at 90 %. It has no effect on resolution — that is what the DPI chips control — only on how aggressively the encoder discards detail. At 90 % text stays crisp and the files are a fraction of a lossless export. Below roughly 70 % you start seeing ringing around sharp black type and blocking in flat colour fills, which is exactly the content most PDF pages are made of; photographs tolerate low settings far better than text does. If you want no loss at all, no slider position gets you there — JPEG is lossy by design, so switch to PDF to PNG.
Is PDF to JPG free, and does my file get uploaded to convert it?
PDF to JPG is available without an account and does not burn a PDFChamp watermark into the images. The component gives the selected File bytes to pdf.js, renders each page to a canvas and asks the browser for JPEG bytes; it does not post the PDF to a conversion endpoint. The pdf.js code and worker can still be fetched as application resources.
The tool says it could not convert my PDF — what went wrong?
"Could not convert — make sure the PDF is not encrypted" means pdf.js refused to open the document, and a password is the usual reason. A PDF with a user password cannot be rendered until it is decrypted, so run it through Remove PDF password first and convert the unlocked copy. The other common cause is a file that is not really a PDF: some scanners and phone apps save a JPEG or TIFF with a .pdf extension, and those fail the moment the header is read. A truncated download produces the same message. If the page strip loaded thumbnails but conversion still fails, the document is probably damaged part-way through — re-export it from the source application.
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