Screenshots, exported diagrams, charts pulled out of a report, UI mockups — the images that document work on a screen arrive as PNGs far more often than as JPGs. Turning them into a PDF makes them filable, printable, and sendable as one ordered document, and the same browser-based tool that handles JPGs handles PNGs too: JPG to PDF accepts both formats, despite its name.
This guide is deliberately PNG-specific: when PNG is the right source format, how its lossless nature carries through the conversion, and where the JPG-vs-PNG decision actually matters. For the general images-to-PDF workflow — page sizing in depth, page numbering, ordering — the full walkthrough lives in How to Convert JPG to PDF, and everything there applies to PNGs unchanged.
When the source is PNG — and why it matters
PNG and JPG images end up in the same kinds of documents, but they're built for opposite jobs, and choosing the right one upstream decides what your PDF looks like downstream:
- Screenshots — crisp UI text, straight 1-pixel edges, flat backgrounds. JPG compression turns each of these into a soft smear of artifacts; PNG was designed for exactly this content.
- Diagrams and flowcharts — lines, arrows, and labels that must stay razor-sharp at any zoom. Lossy compression breaks first precisely where diagrams can't afford it: thin lines and small text.
- Line art and charts — solid colors and sharp transitions. JPG renders flat color as blotchy bands; PNG keeps it flat.
- Anything with repeated saving — JPG is lossy, so every re-save degrades it a little more. PNG is lossless: the fifth copy is identical to the first.
The rule of thumb: photographs of the real world belong in JPG; images of a screen or drawn on a computer belong in PNG. When the image contains text — which is most images that end up in a document — that rule stops being a nicety, because text is where compression artifacts are most visible and least forgivable.
The same tool, stated plainly
Because the question deserves a direct answer rather than a shrug: yes, the JPG to PDF tool converts PNG files. JPG/JPEG and PNG are both supported, and you can mix both in the same PDF — the name describes the most common use, not the limit of the input.
That mixing matters more than it sounds. A single document often legitimately contains both formats: screenshots of an app plus photographs of the whiteboard it was designed on, or diagrams plus a headshot for the title page. There's no need to convert everything to one format first — feed the document what it's made of.
How to convert PNG to PDF
- Open JPG to PDF and drop in your PNGs — up to 100 MB per image, processed in your browser.
- Reorder them into the page order you want.
- Choose a page size: by default each page matches its image; A4 or US Letter pages center the image with its aspect ratio kept.
- Convert and download the PDF.
As many images as you need — a handful or dozens. Nothing is uploaded, so the practical limit is your device's memory, not a server's queue or a plan's quota.
One PNG-specific note on that page-size step: screenshots and diagrams rarely have paper-shaped proportions, so the default — each page matching its image's own dimensions — is usually the right call for them. Nothing is scaled and nothing is letterboxed; the page simply is the image, which is exactly what a screen-capture appendix wants. Reach for A4 or US Letter when the PDF will be printed or filed beside text documents; the image is centered with its aspect ratio kept, so a wide screenshot sits comfortably rather than being squeezed to fit.
Lossless in, lossless out
Here is the property that makes PNG-to-PDF conversion pleasantly boring: each image is embedded into the PDF as-is — no recompression, no resizing. The PDF is just as sharp as your originals. A screenshot's text stays pixel-perfect; a diagram's lines stay crisp. Nothing in the pipeline decides your images are "good enough" and quietly degrades them.
The honest corollary is about size. Lossless images carry all their data, every time — a dense full-screen screenshot can weigh several megabytes, and a PDF containing twenty of them will weigh roughly what those twenty files weigh together. The format doesn't shrink them, and this converter chooses not to silently degrade them either. If the finished PDF needs to fit an attachment limit, the honest order of operations is to reduce or compress — before or after converting — rather than hoping the conversion slimmed things down. It didn't; that's by design.
A note on transparency
PNG supports transparent regions; JPG does not — it's one of the format's genuine advantages, and the reason logos and overlay graphics ship as PNGs. What the tool's documentation doesn't spell out is exactly how transparent areas render once a PNG is placed on a PDF page, so if your image depends on transparency — a logo meant to sit on a colored background, an element with soft cut-out edges — convert one test image and look at the result before you batch-convert the set. Ten seconds of checking beats discovering it after the fifty-page build.
Why PDF, anyway?
A folder of PNGs and a PDF of the same PNGs differ in the ways documents differ from files. The PDF arrives as one attachment instead of a burst of images; its page order is fixed rather than whatever the mail client decides; it opens the same on every device; and it prints as one job with one predictable result. For anything someone will read, file, or reference — a bug report's screenshots, an assembly guide's diagrams, a portfolio of interface work — the PDF is the container and the images are the contents.
And when the need runs the other direction — pages out of a PDF as image files — PDF to JPG and PDF to PNG handle the reverse trip with the same no-upload guarantee.