Convert PDF to JPG
Drop a PDF below and folio renders every page as a JPG image — entirely in your browser. Crank DPI up for crisp prints or down for tiny thumbnails.
Drop your PDF here
Each page becomes a JPG image
One PDF up to 100 MB. JPG pages bundled into a ZIP when there are more than one.
Every operation runs entirely in your browser. Your files never leave your device.
About PDF to JPG
When should I choose JPG?
JPG is smaller than PNG but uses lossy compression — perfect for photographic scans, screenshots and content where slight softness is acceptable. For sharp text or screenshots with hard edges, choose PDF→PNG instead.
What DPI should I use?
150 DPI is the sweet spot for screen viewing. Push to 200–300 if you'll print the result. 72 DPI is fine for thumbnails and saves bandwidth.
Multiple pages = a ZIP
If your PDF has more than one page, folio bundles all the JPGs into a single ZIP so you get one download. A one-page PDF returns a single JPG directly.
About this operation
PDF → JPG
What it does
folio uses pdf.js to render every page of your PDF onto a canvas and writes the result as a JPG. You control the DPI (50–200, default 150 for screen viewing) and JPEG quality (30–95). Multi-page PDFs come back as a single ZIP; one-page PDFs come back as a bare JPG. JPG is the right choice for photographic scans, complex screenshots and any content where small file size matters more than razor-sharp edges.
When to use it
- Email a single PDF page as an inline image
- Generate thumbnails of every page for a gallery
- Pull a chart or diagram out of a longer PDF
- Prep slides for embedding in chat or docs
Limitations — what it doesn't do
- Lossy compression — sharp text and line art may show JPG artefacts
- No way to pick specific pages — every page is rendered (use Split first)
- Cannot decode password-protected PDFs
- Multi-page output always comes back as a ZIP, not loose files
More PDF tools
Every tool runs entirely in your browser.
Frequently asked questions
Your PDFs never leave your device
folio is a static page. Every operation runs inside your browser via pdf-lib (edit) and pdfjs (render). There is no server-side processing, no upload, no temporary file, no cache. When you close this tab, every file is gone.
- No account required.
- No server processing. Your PDFs stay on your device.
- No caching, no Service Worker, no IndexedDB persistence.
- pdfjs-dist (lazy-loaded for rendering) is fetched from your own origin; nothing else is sent.