Render each page to a PNG or JPG at the resolution set. The pages are drawn on this device, one image per page, with nothing uploaded.
Document format work by OnlinePCApps since 2013
Each of these needs a picture of the page, not the PDF. An image drops in where a document will not.
An upload field, a chat window or a content system often accepts a PNG or a JPG but rejects a PDF. Turning the page into an image lets it go where the document could not.
A chart or a diagram inside a report is needed in a slide deck, a web page or a social post. A picture of that page places it exactly as it looks, with no reformatting.
A legal filing or an archive expects each page as its own numbered artifact, cited and marked up on its own. A continuous PDF makes that awkward where a set of images does not.
A file is dropped onto the panel above or chosen from the device. It opens locally and each page is queued for rendering, with no copy sent out.
Choose PNG for crisp text and transparency or JPG for a smaller file. A higher resolution gives a sharper image at a larger size.
Each page saves as a numbered image, taken one by one or all at once in a zip. The source PDF is left untouched.
Converting a page to an image redraws it as pixels. The value is in the control over format and resolution that decides how it looks.
Text, vector art and images on a page are painted together into one flat picture, so the image looks exactly like the page it came from.
A resolution in dots per inch fixes the pixel size of each image. Seventy-two suits a screen, one hundred fifty reads cleanly and three hundred prints sharp.
PNG is lossless and keeps a transparent background, which suits text and line art. JPG is smaller and better for photo-heavy pages that carry no fine edges.
Every page becomes its own numbered image, or a range is picked so only the wanted pages are rendered and the rest are left alone.
Rendering a page to an image is different from pulling the photos out of a PDF. This tool paints the whole page as it looks, useful for a preview or a page thumbnail, while an image extractor returns the original embedded pictures on their own.
Both turn a PDF into page images. The split is over where the document goes and how high the resolution can climb.
| Point of comparison | This tool Rendered in the browser Drawn on the device | Hosted converters Uploaded and rendered on a server |
|---|---|---|
| Where the file goes | Never leaves the device | Goes up to a server |
| Format and resolution | PNG or JPG, DPI set | Usually the same |
| Sign-up or watermark | Neither | Common above a free tier |
| Very high resolution runs | Limited by the browser memory | Rendered in parallel on servers |
| Convert then edit again | A separate step | Often chained in one flow |
The bottom two rows go to the hosted services, and they are the honest reason to upload. A long document rendered at a high DPI can outrun the memory of a browser tab, and a hosted suite can render then compress together. On every other row the browser holds up, because the file stays put.
A browser already draws PDF pages on screen to show them. Saving that drawing as an image is the same work taken one step further, so it happens on the device with no server in the loop.
Since the document is never received, there is nothing on a server to keep and no deletion promise to rely on. A contract or a filing rendered to images stays as private as it was on the disk.
Rendering flattens a page into pixels. Some things carry over, and some are features of a PDF that an image cannot hold.
| Part of the page | Result | What happens and why |
|---|---|---|
| Text | painted, not selectable | Letters are drawn as pixels, so the image looks right but the text can no longer be selected or searched. An OCR pass is needed to read it back. |
| Vector art | rasterized | Lines and shapes are redrawn at the chosen resolution and stop scaling, so a higher DPI keeps them sharp at a larger pixel size. |
| Embedded images | re-rendered in place | Photos already on the page are painted into the flat image at the render resolution, not pulled out at their native size. |
| Links and forms | dropped | Hyperlinks, form fields and comments are PDF features with no place in a picture, so they do not survive the conversion. |
| Transparency | PNG keeps, JPG fills | A PNG holds a transparent background, while a JPG has none and flattens clear areas onto a solid color, white by default. |
| Resolution | 72 to 300 DPI | Dots per inch set the pixel size. An A4 page at 300 DPI is about 2480 by 3508 pixels, sharp enough to print. |
| PNG | lossless | Every pixel is kept exactly with lossless compression, which holds the crisp edges of text and line art. |
| JPG | smaller, lossy | A smaller file that suits photo-heavy pages, set by a quality value from 0 to 100, at the cost of soft halos around sharp text when pushed hard. |
| Scanned pages | capped by the scan | A page that is already an image cannot gain detail. Rendering a 150 DPI scan at 600 DPI only enlarges it, it does not sharpen it. |
The Standards This Follows
Rendering reads the PDF specification and writes standard image formats, which is why the output opens anywhere. The documents below define both sides.
Each of these renders a page. They differ in the control they give and whether they run on the device.
Each of these keeps the file on the computer it opened on, apart from hosted converters that require an upload. The tool above does the same.
A page image is only as good as the choices behind it. These three decide how it comes out.
Seventy-two dots per inch is fine on a screen, one hundred fifty keeps text legible and three hundred prints sharp. Text at seventy-two can look soft, so raise the DPI when it matters.
PNG keeps text and line art crisp and holds transparency. JPG is smaller for a photo-heavy page but softens sharp edges, so the choice follows what the page mostly holds.
An image of a page cannot be searched or edited. When the words still need to be selectable, either keep the PDF or run the image through OCR to recover the text later.
The browser tool renders one document at a time, held in memory. A folder of reports, or a batch that runs at high resolution, is work for the desktop edition, which reads from disk and writes every page image without a tab open.
Point it at a directory and every PDF inside is rendered to page images at the resolution set.
Print-grade DPI runs from disk without straining a browser tab, so large documents render cleanly.
A saved job renders a folder on a schedule, which suits a library that keeps growing.
Free, no sign-up and no upload. The pages are rendered on the device as one image each, and the source PDF is left untouched.