Turn PNG files into PDF in your own browser

PNG stores an image losslessly: it keeps every pixel and full transparency, and the W3C specification of 24 June 2025 allows 8 or 16 bits per colour channel[1]. A PNG file opens in every browser, and in Windows with no add-ons[2][3].

PDF is a document format Adobe released in 1993, and an ISO 32000 standard since 2008[4]. A file holds pages of a fixed size, so an image in it has its place on the sheet and comes out of a printer the way you see it on screen.

Turning PNG into PDF helps when an image has to become a document: an email attachment, a file to sign, or a printout. The converter puts every image on its own A4 page, centred and with a margin, and with the Combine all images into one PDF document option checked it builds one document out of several images.

1. Drag your files onto the Add files area, or click it to pick them from your disk. Any number of PNG files is fine.
2. Change the page order with Move up and Move down, and the Combine all images into one PDF document option turns them into a single file.
3. Click Convert. Every finished file gets the Done status.
4. Save it with Download PDF when combining is checked, or Download all when each image gets its own file.

The queue shows every file with its Before and After weight, the difference in percent, and the batch totals.

The quality slider shows up for lossy sources such as JPG or HEIC. For PNG files it is absent, because the image enters the document with no further lossy compression.

Remove takes one file out of the queue, Clear all empties it.

Everything happens in your own browser: the PNG file is read by an image element, and the jsPDF library assembles the document in that same browser.

No. A PNG image enters the document as PNG, so no pixel is coded lossily and text on a screenshot stays sharp. That is why this page has no quality slider: it appears for the other sources, JPG and HEIC among them, which are stored lossily anyway.

The file weight does move in both directions, because the document packs the pixels with its own algorithm rather than the one from your file. In the measurement the landscape photo comes out 2 percent larger, the product photo on a light background actually comes out 7 percent smaller, and the screenshot with text comes out 31 percent larger. The icon with transparency grew the hardest: it comes out 59 percent larger. That is a difference in how the same pixels are packed, not in how many there are.

The image is never enlarged: one smaller than the page area keeps its own size, and a larger one comes down to the size of the sheet with its margin. The page is A4, the international ISO 216 size that North America does not use[5], so a document printed on US Letter will have slightly different margins. If you would rather set the dimensions yourself first, change them in the Helios editor, and an image out of a finished document comes from the PDF to JPG converter.

The image lands on a white sheet, so a transparent background comes out white in the document and semi-transparent pixels are blended with white. In print it looks the same as on screen, because the sheet is white anyway.

EXIF data does not reach the document, and the orientation stored in that data is applied. The colour comes out on 8 bits per channel, because that is what the browser canvas we read the pixels from hands over[2].

The document is assembled here by the jsPDF library running in the browser, so the image never leaves your device. If the file is meant to stay an image rather than become a document, pick the PNG to JPG converter or the PNG to WebP converter, and for a print shop that asks for an uncompressed file the PNG to TIFF converter.