PDF to JPG

A PDF page is not a picture — it is a set of instructions describing text runs, embedded fonts, vector shapes and any embedded images, all positioned with mathematical precision. Turning that into a JPG or PNG means interpreting those instructions and painting the result onto an actual pixel grid at a chosen resolution, the same fundamental process a PDF viewer performs every time it displays a page, except the output here is captured as an image file rather than shown on screen. This is why increasing the DPI produces a genuinely sharper image rather than just a scaled-up blurry one: the page is being redrawn from its underlying vector instructions at the higher resolution, not stretched after the fact.

DPI (dots per inch) describes how many pixels get painted per inch of the original page, so the right number depends entirely on how the resulting image will be viewed rather than on the document itself. 150 DPI matches typical screen viewing and web use comfortably, since displays cannot resolve much beyond that at normal viewing distance regardless of how many pixels the file contains. 300 DPI is the long-standing standard for print reproduction, where physical paper and closer viewing distance genuinely reveal more detail. Going meaningfully higher than 300 rarely adds visible quality for either use case and mainly produces a larger file — there is a real ceiling past which more pixels stop mattering.

A rendered page that is dominated by a photograph or a scanned image compresses well as JPG with no visible cost, for the same reason photographs generally do. A rendered page dominated by text, line art or sharp diagram edges is the case JPEG handles worst — its compression is tuned to discard exactly the kind of high-frequency detail that sharp text edges are made of, producing a visible soft halo around lettering that gets more obvious the more the image is zoomed. PNG has no such penalty because it is lossless, at the cost of a meaningfully larger file for the same page. The distinguishing question is the same one that applies everywhere: is this page's content mostly continuous tone, or mostly hard edges and text.

Form fields, hyperlinks and any other interactive layer a PDF might carry exist as a separate structure layered on top of the visible page, invisible to the rendering process that paints pixels — converting to an image captures exactly what a page looks like, not the interactive elements sitting behind that appearance. A form rendered this way looks identical to the original but the fields are no longer fillable, and any links become plain unclickable text. That is inherent to the conversion, not a bug: an image has no concept of interactivity to preserve.