PDF to JPG

UtilTools ships its own PDF renderer: paths, fills, strokes, clipping, images and text with embedded fonts are drawn to canvas. It handles the great majority of real documents, but it is not a full print-quality engine — exotic shading patterns and some Type 3 fonts are approximated. Always eyeball the preview.

Scanned documents are usually one big JPEG per page. Extraction pulls that JPEG out at its original resolution with zero re-encoding, which is both faster and sharper than re-rendering the page.

150 DPI matches typical screen reading. 300 DPI is the standard for printing or OCR. 72 DPI gives you the page at its nominal PDF size in pixels. Higher settings multiply memory use by the square, so very large pages at 600 DPI can exhaust a phone.

JPG for photographic scans — much smaller files. PNG for pages that are mostly text, line art or screenshots, where JPEG artefacts show up around sharp edges.

Yes. Select the single thumbnail, or type 1 in the page selection. Only the pages you choose are rendered, so pulling one page out of a 300-page report takes about as long as a one-page document.

Usually the DPI setting — raise it to 300 for print or OCR, which quadruples the pixel count. If the page is a scan, the source resolution is the hard ceiling: rendering a 150 DPI scan at 600 DPI only enlarges the same pixels and makes a much heavier file, so match the scan rather than going past it.

Yes. There is no account, no daily cap, no file-size tier and no watermark, because there is no server cost to recover. The site is funded by clearly disclosed partner recommendations on the Partners page, never by metering the tools.

No. Everything is processed by JavaScript running in your browser, on your device. You can verify it: open your browser's developer tools, switch to the Network tab, and use the tool. You will see no request carrying your data — because there is nowhere for it to go.