PDF to Transparent PNG — Remove White Background Free
Convert PDF pages to transparent PNG images. White background removed automatically with adjustable threshold — perfect for logos, signatures, and overlays.
Turn a PDF page into a transparent PNG
This is a PDF to transparent PNG converter: it renders the pages you pick, removes the white background, and hands back a PNG with a real alpha channel — the format you want for a logo, a signature, a stamp, a watermark, or any PDF graphic you need to overlay on a coloured or photographic background without a white box around it. Toggle Remove white background off and it becomes a plain page-to-PNG export instead.
It runs entirely in your browser tab — pages are rasterized with a local copy of PDF.js and the pixels are edited on a <canvas>, so your file never leaves your device, there is no upload, no signup, and it is free. If you actually want an opaque page image, our PDF to image converter keeps the white; if you want to stamp text over a page, Watermark PDF does that instead.
How the tool decides which pixels vanish
There is no AI and no edge detection here — it is a deliberately simple pixel scan, which is exactly why the threshold slider behaves so predictably. After a page is drawn to the canvas, the tool walks every pixel and looks at its red, green, and blue channels. If all three are at or above the threshold you set, that pixel is made fully transparent; otherwise it is left exactly as it was:
for (let i = 0; i < data.length; i += 4) {
if (data[i] >= threshold && // red
data[i + 1] >= threshold && // green
data[i + 2] >= threshold) { // blue
data[i + 3] = 0; // alpha -> fully transparent
}
}Three consequences fall straight out of that rule, and they explain almost every result you will ever get:
It only clears near-neutral pixels. Because red, green, and blue must all be high, a background has to be white or a light gray to qualify. A blue, cream, or kraft-coloured page keeps at least one low channel, so it is never touched — this removes white, not colour.
The cut is binary — there is no feathering. A pixel is either wiped to alpha 0 or left fully opaque; nothing is made half-transparent. Anti-aliased edges (the soft gray ring the renderer paints around letters and curves) are a smooth gradient from ink to white, so a hard cut through them can leave a faint light halo or, if you push the threshold too low, bite into the edge and make it look ragged.
The threshold is global, not regional. The same number is applied to the whole page — you cannot protect one area and clear another. The default is 250 and the slider runs from 200 (more aggressive) to 255 (pure white only). The checkerboard behind each preview is just how transparency is drawn on screen; it is not baked into the PNG you download.
A worked example: 250 vs 235 on a light-gray letterhead
Imagine a scanned letterhead with four kinds of pixel in it: the bright page, a slightly cream margin, a hairline rule under the header, and the soft gray edge of the body text. Here is what each threshold does to them — the same four pixels, three different slider positions:
| Pixel | RGB (approx.) | Threshold 250 | Threshold 235 | Threshold 220 |
|---|---|---|---|---|
| Bright page background | (252, 251, 250) | Removed | Removed | Removed |
| Cream / off-white margin | (243, 240, 238) | Kept | Removed | Removed |
| Light-gray hairline rule | (225, 225, 225) | Kept | Kept | Removed |
| Anti-aliased text edge | (205, 205, 205) | Kept | Kept | Kept |
At 250 only the brightest pixels clear, so a cream scan still shows a pale film. Drop to 235 and the cream goes too — that is usually the sweet spot for off-white letterhead — while the rule and the text edge survive. Go to 220 and you also erase the hairline rule; that soft text edge only starts disappearing as you approach the slider’s 200 floor, and once it does the type looks thin and chewed. The honest takeaway: lowering the threshold to catch a dingy background will, sooner or later, start eating light content, because the cut is binary and cannot tell a faint background apart from a faint line.
Troubleshooting: which threshold to reach for
Most transparency problems are a mismatch between the slider and the actual shade of your background. Match the symptom, then nudge the threshold a few points at a time and re-convert:
| Symptom | Why it happens | What to try |
|---|---|---|
| A pale halo rings the extracted logo or signature | Anti-aliased edge pixels sit just below the threshold, so they stay opaque | Lower the threshold gradually (250 to 240 to 230); a last faint fringe is the binary cut, which only a manual edit in an image editor fully removes |
| An off-white or scanned background survives at 250 | The paper is not pure white, so at least one channel is under 250 | Try 235 to 240, then check that light rules and watermarks did not vanish with it |
| Hairlines, table rules, or a faint watermark disappeared | They are neutral gray above your threshold, so the rule counts them as white | Raise the threshold back toward 248 to 252 to protect them, accepting a little background residue |
| Coloured paper (blue, kraft, pastel) will not go transparent | The rule only clears pixels where red, green, and blue are all high; a colour keeps one channel low | No threshold fixes this — the tool removes white and gray, not colour; use a background remover built for chroma |
| Light areas of a photo (sky, highlights) get punched out | Those highlights are near-white too, and the threshold is applied to the whole page | Raise the threshold, or crop to just the logo or signature before converting so the photo is out of frame |
| Text or a thin logo looks ragged and bitten-into | The threshold is low enough to erase the anti-aliased edge itself | Raise it until the edges fill back in; 250 is the safe default for crisp type |
You are extracting a raster PNG — sometimes you want the vector
A logo sitting on a PDF letterhead is very often stored as vector art — crisp maths that stays sharp at any size. The moment you convert it here it becomes a raster PNG: a fixed grid of pixels baked at the tool’s render resolution. That is perfect for a web overlay, a presentation graphic in a slide deck, a product image or spec diagram for an e-commerce listing, an app UI asset like an icon or badge, or a transparent stamp — anywhere the size is known and modest. But blow that PNG up past its native size and it will soften and pixelate, because there is no vector left to redraw from.
So the honest rule of thumb: if you own the brand asset and expect to scale it big — a billboard, a large print, a favicon-to-hero range of sizes — track down the original vector (an .svg, .ai, .eps, or .pdf with the live artwork) instead of ripping a raster copy out of a document. When a fixed-size transparent PNG is genuinely what you need, this tool is the fast path, and you can crop it tight or compress it afterwards.
Resolution: web, print, and signatures
The tool rasterizes every page at a fixed 2× scale. For a page measured in standard PDF points that works out to roughly 144 pixels per inch at full-page size — so a US-Letter page (612 × 792 points) exports at about 1224 × 1584 pixels. Whether that is enough depends entirely on where the PNG is going:
- Web and screen overlays
- The fixed 2× render is plenty for a logo, diagram, or graphic shown on a website, a slide, or a social card. Screens are the tool’s home turf, and transparency drops the content straight onto any background.
- About 144 ppi at full-page size is below the ~300 DPI convention print shops expect, so a whole page enlarged for print can look soft. For print, source a higher-resolution original (or the vector) rather than upscaling this PNG — enlarging a raster does not add real detail.
- Signatures and stamps
- Crop tightly to the mark; a signature only needs to be a few hundred pixels wide to overlay cleanly, and a transparent PNG sits over existing text without a white block. One caveat that is not legal advice: a pasted image of a signature is not always the legally binding equivalent of a proper e-signature — check what your document or jurisdiction requires, and if you need a genuine signing flow use eSign PDF instead.
Frequently asked questions
Only near-neutral white and light gray. A pixel becomes transparent only when its red, green, and blue channels are all at or above your threshold, so a coloured background (blue, cream, kraft, pastel) always keeps one channel low and is left untouched. This tool removes white backgrounds, not coloured ones.
Start at the default 250, then drop toward 235-240 if a pale film remains. Watch that light-gray rules, hairlines, or a faint watermark do not vanish at the same time; if they do, raise the threshold back toward 248-252 and accept a little residue.
Because the transparency cut is binary with no feathering, the anti-aliased pixels that ring the artwork are either kept or wiped whole. A light halo means those edge pixels sit just below the threshold. Lowering it a few points helps; a last faint fringe usually needs a quick manual cleanup in an image editor.
No. JPEG has no alpha channel, so re-saving as JPG flattens the transparent areas onto a solid colour (usually white). Keep the file as the PNG this tool produces wherever you need the see-through background.
Pages are rendered at a fixed 2x scale, roughly 144 pixels per inch at full-page size, which is great for web, slides, and overlays but below the ~300 DPI print standard. For print, use a higher-resolution original or the source vector rather than upscaling the PNG.
Yes to both. It is free with no signup, and every step runs locally in your browser using PDF.js and the Canvas API. Your file is never uploaded, so nothing leaves your device.