You can turn every page of a PDF into a JPG or PNG image without uploading anything: the file is opened in your browser, each page is rendered on a canvas at the resolution you choose, and you download the images. Nothing is sent to a server.
The converter supports three fixed resolutions (72, 150 and 300 DPI), JPG or PNG output, an optional JPG quality slider from 50 to 100, and a page range such as 1-3,5. Each page becomes a separate image file, so a ten page document gives you ten pictures. The one cost you must accept is that images have no text layer: after conversion the pages are no longer searchable or selectable, and that change cannot be undone. It is the right format for sharing a page, not for archiving a document you will need to quote from.
Most PDF to JPG services ask you to upload the document first, which is a poor fit for a signed contract, an ID scan or a medical record. This page explains what a browser-based converter actually does, how the three DPI settings trade size against detail, and where the approach stops being the right tool.
PDF to JPG
Render each PDF page to JPG or PNG at 72, 150 or 300 DPI, with a page range and a JPG quality slider. The file never leaves your device.
What converting a PDF to JPG actually does
A PDF page is not a picture. It is a set of instructions: text runs with fonts, vector shapes, and embedded images placed at coordinates. To produce a JPG or PNG, the converter has to rasterise the page, which means drawing all of those objects onto a pixel grid at a chosen scale, and then encoding that grid as an image file. This tool does the drawing with PDF.js, a rendering engine that runs inside the browser, and it processes one page at a time.
Two consequences follow. The first is that the output is a flat image: whatever was text, a link or a vector shape becomes coloured pixels, so the page looks the same but carries no structure. The second is that the resolution you pick decides how fine the pixel grid is, and therefore how sharp the result looks and how large the file becomes.
How to convert a PDF to images without uploading it
- Add your PDF. Drop the file into the tool or click to browse. It is read locally into the page and opened there, so no network request carries the document.
- Choose the output format. JPG is selected by default and gives smaller files; PNG is lossless and keeps text and thin lines crisp. The JPG quality slider appears only for JPG, with a range from 50 to 100 and a default of 92.
- Pick a resolution. Choose 72 DPI for a screen-sized preview, 150 DPI for a readable document, or 300 DPI for printing. Higher settings draw more pixels per page and take longer.
- Set a page range if you need one. Leave the box empty to convert every page, or type something like 1-3,5. Entries that are out of range or badly formatted are reported before anything is rendered.
- Convert and download. Watch the per page progress, then save images one at a time or use Download all, which saves the whole set in sequence.
Before you download, the result panel reports the format, the resolution, how many pages were converted out of the total, and the combined size of the images. Changing any setting clears the previous results, so what you see on screen always matches the settings shown.
72, 150 or 300 DPI: what to pick
DPI describes how many pixels are drawn per inch of the page. The tool offers three fixed steps because most work falls into one of three buckets, and a free slider would mostly invite guesses.
| Setting | Render scale | Best for | What it costs |
|---|---|---|---|
| 72 DPI (screen) | 1x the page size | Quick previews, thumbnails, sharing a page in chat | Lowest detail; small text looks soft when zoomed in |
| 150 DPI (good) | About 2.1x | Reading a document on screen, sending a clear copy | Larger files and slower rendering than 72 DPI |
| 300 DPI (print) | About 4.2x | Printing, archiving, records and legal copies | Largest files; many pages means many big images |
The jump is bigger than it looks, because pixel count grows with the square of the scale. Moving from 72 to 300 DPI multiplies the width and the height by about 4.2 each, so a page carries roughly seventeen times more pixels. That is why a whole scanned report at 300 DPI produces a large set of large files, and why rendering takes noticeably longer.
JPG or PNG: which output format
Both formats are flat images with no text layer, so the choice is about compression rather than capability.
| Format | How it compresses | Good for | Watch out for |
|---|---|---|---|
| JPG | Lossy, small files | Photos, scanned pages, quick sharing | Fine text and sharp edges pick up artefacts at low quality |
| PNG | Lossless, larger files | Screenshots, line art, pages where text must stay crisp | Much bigger downloads on photographic pages |
JPG is the default because most PDF pages end up being shared, and the quality slider lets you trade file size against artefacts. Setting it near 100 keeps text clean at the cost of size, while dropping it toward 50 shrinks the images but makes small text and thin rules visibly rough. PNG has no quality setting at all, because it stores every pixel exactly, and it is the better pick when a page contains charts, tables or fine typography that has to stay sharp.
You lose the text layer, and that is irreversible
Rasterising a page removes its text layer. In the converted image, words are shapes made of pixels rather than characters, so the file cannot be searched, text cannot be selected or copied, and a screen reader finds nothing to read. For a chat attachment or a preview image this is fine, because nobody searches a picture. For a contract, a manual or anything you may need to quote later, it is a real loss, and it cannot be undone from the image.
Two honest points follow. First, higher DPI does not put the text back: a 300 DPI image of a page is still an image, only a sharper one. Second, this tool is not optical character recognition, so it never reads the words and cannot rebuild them. If you need searchable text, keep the original PDF, or use the PDF to Text tool to extract the text layer into a file you can edit. If the PDF is a scan with no text layer, neither approach recovers it and you need a genuine OCR step.
PDF to Text
Need the words rather than a picture? Pull the text layer out as editable, searchable plain text, still entirely in the browser.
What this converter cannot do
Worth reading before you start, because these are the cases where a different tool is the honest answer.
- It cannot make text searchable. Rasterising destroys the text layer, and the tool does not perform OCR, so a converted page is never searchable or selectable.
- It cannot add detail that is not in the file. A low resolution scan exported at 300 DPI is rendered larger, not sharper; DPI changes the pixel count, not the information.
- It cannot combine pages. Every page becomes its own image file, with no single long image and no multi page output.
- It cannot accept anything but a PDF. The input is PDF only, so an image, a Word file or a web page has to be turned into a PDF first.
- It cannot open password protected files. An encrypted PDF fails to load, so unlock it first and convert the unlocked copy.
- It cannot exceed 40 megapixels per page. If a page would be larger than that at the chosen DPI, the tool reports it instead of rendering and asks you to pick a lower resolution.
- It cannot change page content. Cropping, rotating or deleting pages happens in the PDF itself, not here.
Why convert in the browser instead of uploading
An upload-based converter is convenient, and for a file you do not mind handing over it works well enough. The documents people actually convert to images tend to be the opposite: signed contracts, ID scans, bank statements, medical letters and internal reports. For those, the property that matters is that the file never leaves your own machine.
| Aihangsoft | Upload-based converter | |
|---|---|---|
| Where the file goes | Stays in the browser tab | Sent to their servers |
| Account and limits | None | Often a sign-up, daily caps or watermarks |
| Works offline | Yes, after the first load | No |
| Output control | Format, DPI, JPG quality, page range | Usually one fixed preset |
The trade is that the work happens on your own hardware, so a long, image heavy document renders more slowly than it would on a server, and everything is bounded by your browser memory. For the handful of pages most people convert, that is a good trade. The engine is a self hosted copy of PDF.js, a little over a megabyte, and it downloads on first use and is cached afterwards.