Convert PDF to PNG online — with transparent background support

When to convert a PDF to PNG (instead of JPG)

PNG and JPG are both raster image formats, but they were designed for different jobs. The PNG specification (W3C Recommendation, ISO 15948) defines a lossless image format with an explicit alpha channel¹. JPG (ISO/IEC 10918-1) is lossy, opaque, and tuned for continuous-tone photographs². That difference points each format at very different PDF use cases:

• Pick PNG when the page contains a transparent background you want to keep (logos, slide overlays, sticker artwork, design comps), when the page is mostly flat colour or vector linework where JPG's blocking artefacts would be visible, or when the PNG will be re-edited later and you want to avoid generation loss.
• Pick JPG via PDF to JPG when the page is mostly a photograph, when file size matters more than perfect fidelity, or when the destination platform (some email clients, some legacy CMSes) refuses PNG.
• Pick a separate workflow via Extract Images when you want the original embedded photographs back as their own files — image extraction is a different operation from page-rasterisation, and conflating them is the single biggest source of "the output isn't what I wanted" support tickets.

Step-by-step: convert a PDF to transparent PNGs

The ScoutMyTool PDF-to-PNG tool lives at scoutmytool.com/pdf/pdf-to-png. It runs client-side via pdf.js — no upload, no signup, no quota. The full workflow takes under a minute for a typical document.

1. Open the tool and drop your PDF. One file at a time. The file is loaded into a sandboxed memory buffer using pdf.js; nothing is uploaded. If the source is sensitive (an unreleased design comp, a private brand asset, a draft slide deck) open the browser network tab first and confirm there is no outbound request when you run the conversion.
2. Pick the resolution. Three explicit options instead of a vague "auto":
   • 1× (~72 dpi) — smallest files. Use for thumbnails or contact sheets.
   • 2× (~144 dpi) — recommended default. Sharp on Retina displays, manageable size. Right for almost all on-screen use.
   • 3× (~216 dpi) — print quality. Use when the PNG will be placed in a print-bound layout at near-original size, or zoomed heavily.
   Because PNG is lossless, file size scales roughly with pixel count: a 2× export is ~4× larger than a 1× export, and a 3× export is ~9× larger.
3. Confirm the transparency option. A toggle labelled "Preserve transparency" is on by default. Leaving it on means the canvas is rendered without a pre-fill, so any region the PDF did not paint stays fully transparent in the PNG. Toggle it off only if you specifically want a white background — for example, if the downstream platform mishandles alpha PNGs and you would otherwise have to flatten them anyway.
4. Click Convert. The tool walks every page of the PDF, renders it to an off-screen canvas at the chosen scale, and encodes the canvas to PNG via the browser's native PNG encoder. Pages are processed one at a time so per-page memory usage stays bounded; a 50-page PDF does not need 50× a single page's memory budget. Progress is shown live so you can tell whether a slow page is making real progress or has stalled.
5. Download the zip. All page-PNGs are bundled into one zip named <your-pdf-name>.zip with each page named page-1.png, page-2.png, etc. The download starts automatically. Typical time: 1–3 seconds per page at 2× on a modern laptop, longer at 3×.
6. Verify transparency. Open one of the output PNGs in any image viewer that shows the transparency checkerboard (Preview on macOS, GIMP, Photoshop, or even a browser tab). If the corners show the checkerboard pattern instead of solid white, transparency made it through end-to-end. If they show solid white, the source PDF had a painted white background — the converter cannot recover transparency that was never in the input.
7. If you only want some pages. Pre-filter via Extract Pages using a range syntax like 2, 5-7, then run the smaller PDF through PDF-to-PNG. Two passes, both client-side.
8. If the source PDF is password-protected. Unlock first via Unlock PDF; the PDF-to-PNG tool deliberately refuses to silently strip encryption.

How ScoutMyTool compares to Smallpdf, iLovePDF and PDF2Go

All four offer some flavour of PDF-to-PNG conversion. The meaningful differences are around transparency handling, explicit resolution control, and whether the source file leaves your device. The row that matters most for the transparent-background use case is the third one: most competitors pre-fill the canvas white before rendering, so the PNG that comes out is alpha-channel-flat regardless of the input PDF.

Third-party gating, free-tier caps, and feature availability taken from each vendor's public pricing pages as of May 2026 and may change. Transparency-handling rows determined empirically by converting the same alpha-channel test PDF through each tool and opening the outputs in GIMP with the alpha layer visible.

Why most PDF-to-PNG converters destroy transparency

PDF's imaging model has supported transparency since PDF 1.4 in 2001 — every modern PDF can carry an alpha channel via the ExtGState transparency group mechanism. PNG has supported alpha since the original PNG 1.0 specification in 1996. So a conversion from one to the other has no format-level reason to drop alpha. The reason it usually happens anyway is a one-line decision in the converter's rendering pipeline:

• The converter creates an off-screen canvas (in JS, in ImageMagick, in Ghostscript — same idea everywhere).
• Before passing the canvas to the PDF renderer, the converter fills it with opaque white. This is the line that destroys transparency. It is almost always there because earlier in the tool's life it was a PDF-to-JPG tool (which has to fill white because JPG cannot store alpha), and when PNG output was added the pre-fill was never removed.
• The PDF renderer then paints page content on top of the now-opaque white background. Wherever the PDF had transparency, the rendered canvas now shows opaque white.
• The canvas is encoded as PNG — technically a 32-bit alpha-aware PNG — but every alpha value in the file is 255 (fully opaque) because nothing transparent remains.

ScoutMyTool's PDF-to-PNG explicitly omits the pre-fill step when the "Preserve transparency" toggle is on, so alpha makes it all the way through.

Managing PNG file size without sacrificing transparency

PNG is lossless, which means it cannot compress the way JPG does for photographic content — a page of dense photos exports to a PNG roughly 5–10× larger than the equivalent JPG at quality 90. That can be a problem when you need to email the result, embed it in a web page, or upload it to a platform with a per-file cap. The good news is that PNG file size is dominated by three factors, and all of them are within your control:

• Pixel count. File size scales roughly with (width × height). Dropping from 3× to 2× cuts pixel count by about 56% and file size by a similar fraction. For most screen use, 2× is the right choice — the bytes you save by going lower are immediately worth it for any non-print deliverable.
• Colour complexity. A page of flat colours, line art, and text compresses dramatically better than a page of photographs. If your PDF's pages are mostly text on a transparent background — for example, a brand-asset PDF containing only a logo — the resulting PNG will be small (often well under 100 KB at 2×) even at high resolution. A photo-heavy page will not, regardless of resolution.
• Post-process compression. The browser's native PNG encoder is fast but not the most aggressive compressor. If the result is right but too large, run the individual PNGs through a lossless re-compressor such as pngcrush, OptiPNG, or zopflipng — they typically shave a further 10–25% from PNG file size with zero quality change. Those are command-line tools, but plenty of free GUI wrappers exist if you prefer a drag-and-drop interface.

The one thing not to do: re-save the PNG as JPG to make it smaller. That destroys the transparency you went to PNG to preserve in the first place, plus it introduces JPG compression artefacts around the sharp edges that are PNG's strength. If the deliverable does not need transparency and file size is paramount, do the original conversion straight to JPG via PDF to JPG instead — the output is built for that use case from the start.

Related PDF tools on ScoutMyTool

• PDF to PNG — the tool this guide is about: page-to-PNG with alpha preserved.
• PDF to JPG — same workflow, JPG output, smaller files, no transparency.
• Extract Images — pull each embedded image out as its own file (different operation from page-rasterisation).
• Extract Pages — pre-filter to specific pages before conversion.
• Compress PDF — if you want the PDF smaller while keeping it a PDF.
• Unlock PDF — required first if your source is password-protected.
• Best free PDF tools (2026) — broader landscape comparison.

Frequently asked questions

Why use PNG instead of JPG when converting a PDF?

PNG keeps transparency (an alpha channel) and uses lossless compression — what goes in is what comes out, pixel-for-pixel, no JPG-style compression artefacts around sharp edges, logos, or text. JPG cannot store transparency and re-encodes the image with lossy DCT compression, which is great for photographs but visible on flat colour fills, line art, and screenshots of text. Convert to PNG when the result will sit on a non-white background (a slide, a designed web layout, a coloured social card), when crispness matters more than file size, or when you may re-edit the image and want to avoid generation loss.

How do you actually preserve PDF transparency in the output PNG?

ScoutMyTool renders each PDF page to an off-screen HTML canvas without pre-filling a background colour. pdf.js draws every page element (text, vectors, images) onto the alpha-aware canvas as-is, and the canvas is encoded with HTMLCanvasElement.toBlob(..., "image/png") which writes a PNG-32 file with an 8-bit alpha channel. Regions of the PDF that have no painted content remain fully transparent (alpha 0) in the PNG. Other PDF-to-PNG tools commonly pre-fill white before rendering, which destroys the alpha — open one of their outputs and check the corners with the eyedropper, you will see RGB(255,255,255) instead of transparent.

My PDF looks white in a viewer — does it actually have transparency?

Maybe not. Most PDFs you receive (scans, reports, exported invoices, downloaded forms) have an explicit white page background painted by the producer application, so even though the file format supports transparency, that specific page has none. The fastest way to check: open the PDF in a viewer that can show transparency (Adobe Acrobat with View → Show Transparency Grid, or any PDF tool that visualises the alpha layer). If the page is still solid white with the grid on, the white is "paint", not transparency, and a PNG export will keep it white. If you want a transparent background under existing white paint, you first need to remove the background fill — typically in the source application (Illustrator, Figma, InDesign) rather than after-the-fact.

What resolution should I pick for transparent PNGs?

2× (~144 dpi) is the recommended default for screen use and matches what looks crisp on a Retina display. Use 1× (~72 dpi) for thumbnails or when file size dominates. Use 3× (~216 dpi) when the PNG will be placed into a print-bound deliverable at near-original size, or where the recipient may zoom in heavily. Because PNG is lossless, every doubling of scale quadruples both pixel count and file size — a 2× page typically lands at 200–600 KB; the same page at 3× often exceeds 1.5 MB. Going beyond 3× hits the browser canvas memory cap (~96 MB per page) and the tool will refuse with a clear error rather than silently crashing.

Is my PDF uploaded to your servers?

No. The conversion runs entirely in your browser using pdf.js for rendering and the browser-native canvas PNG encoder. Your PDF is loaded into a sandboxed memory buffer, each page is rasterised to an off-screen canvas, the canvas is encoded as PNG, and the page-PNGs are bundled into a zip with JSZip — all in-browser. The "download" you receive is that zip file; nothing was uploaded. You can confirm in the browser network tab (open DevTools → Network, filter to XHR/Fetch, run a conversion — there should be zero outbound requests to scoutmytool.com beyond the page itself).

How big can the input PDF be?

No hard file-size cap — the conversion is client-side. The practical limit is per-page canvas memory: at 3× scale a Letter-size page needs roughly 32 MB of pixel buffer; at 2× scale, about 14 MB. The tool pre-checks each page and refuses with a clear error if the chosen scale would need more than ~96 MB per page (mobile Safari caps around 128 MB and the tool deliberately stays below that). If you hit the cap, drop the resolution to 2× or 1× — the visual difference is minimal for screen viewing. There is no cap on number of pages; a 500-page PDF will simply take 500× single-page time.

Can I convert only specific pages instead of all of them?

Not in the PDF-to-PNG tool directly — it converts every page in the input PDF. To convert a subset, first run the PDF through Extract Pages with a range like "5, 8-10" to produce a smaller PDF containing only the pages you want, then run that smaller PDF through PDF to PNG. Two-pass workflow, both passes client-side, no upload at either step.