PNG Background Black Instead of Transparent

The most common cause is simple: the source image never had a transparent background to begin with, so converting it to PNG can't invent transparency that wasn't there. PNG is a format that supports transparency — it doesn't guarantee it. If you convert a JPG, a flattened screenshot, or a rasterized PDF/EPS to PNG, the converter can only copy the pixels it's given. If those pixels were rendered against a black canvas or a black matte, the resulting PNG faithfully shows black, because that's what was actually there. Other causes are less obvious: an export setting that quietly dropped the alpha channel, or a perfectly transparent PNG that simply displays as black in a viewer that doesn't render alpha correctly. The fix depends entirely on which of these you're actually dealing with, which is why the next step is always to check whether the file is transparent, not just to assume it should be.

If you started with a JPG, a flattened PSD, or a rasterized PDF/EPS export, your PNG was never going to be transparent — none of those formats can store an alpha channel, so whatever background color was baked into the pixels at export time is what you get. This trips people up because "PNG" is often used as shorthand for "transparent image," but PNG only supports transparency; it doesn't add it automatically. A JPG converted to PNG is still just the JPG's pixels, black background included, wrapped in a different file format. The only real fix here is to go back to a source that actually has (or can have) an alpha channel — for example, re-export from the original design file with a transparent background enabled, or recreate the cutout using a background-removal tool — and then convert that transparent source to PNG. Converting the already-flattened file again will never produce transparency, no matter how many times or which tool you use.

Sometimes the file is fine and the viewer is the problem. Some image viewers, older editors, and even some browsers render transparent pixels as solid black instead of the usual checkerboard pattern, because they don't support alpha compositing in their preview. This is an app limitation, not a defect in your PNG — the transparency data is still stored correctly in the file; it's just not being drawn correctly on screen. Windows Photo Viewer, some default OS thumbnail generators, and a handful of lightweight image tools are common offenders. Before you assume your file is broken, open it in a viewer known to handle alpha properly (Photoshop, GIMP, Preview on macOS, or a browser rendering it inside an HTML page) and see if it now shows a checkerboard where you expect transparency. If it does, your PNG was never the issue — only reopen or reconvert the file if a proper alpha-aware viewer also shows black.

Design tools can silently strip transparency during export if the output mode doesn't support an alpha channel. Exporting a PNG in Indexed Color mode, for instance, uses a limited color palette that may not include a transparency entry, so anything meant to be see-through gets filled with a solid color instead — often black or whatever the canvas background was set to. This happens in Photoshop, GIMP, and various online converters when "transparency" isn't explicitly selected in the export dialog, or when the image is flattened before export. The fix is to re-export using RGB/RGBA mode (not Indexed), explicitly enable "transparency" or "alpha channel" in the export settings, and confirm the canvas or artboard background is set to none/transparent rather than white or black before saving. If your tool defaults to a colored canvas with no way to disable it, that's a sign to switch to an export path that preserves alpha by default.

SVG-to-PNG and icon-to-PNG conversions add their own wrinkle: SVGs are code, not pixels, so a black background in the output usually means the SVG itself contains a black rect or background element behind the artwork, or the converter you used defaults to filling any non-opaque area with black instead of true alpha. Open the SVG in a text/code editor and check for a rect covering the full canvas with a black fill — removing it, or setting its fill to "none," fixes the root cause at the source. If the SVG itself is clean, the problem is the converter: some command-line and server-side SVG rasterizers fill unspecified background pixels with black rather than leaving them transparent. A canvas-based, browser-native converter renders exactly what the SVG specifies, including transparency, so switching converters solves this without touching the SVG at all.

Don't guess — verify. The fastest check is to open the PNG in an editor that renders alpha correctly (Photoshop, GIMP, Photopea, Preview) and look for the gray-and-white checkerboard pattern where you expect transparency; a solid black fill in one of these tools means the file genuinely has no alpha data there, not a display bug. You can also drag the PNG into a browser tab or an HTML page with a colored or patterned background behind it — a real transparent PNG will let that background show through. Alternatively, check the file's color type: PNG supports color type 6 (RGBA, true alpha) and color type 3 (indexed, which may or may not include a transparency chunk); a quick way to see this is opening the image's metadata/info panel in an editor, which usually reports "Alpha" or "No Alpha" directly. If every alpha-aware check still shows black, the transparency simply isn't in the file.

If your source genuinely has transparency — an SVG, a WebP with an alpha channel, or a PNG that's already correctly transparent — the goal when converting is simply not to lose it. Canvas-based, browser-side converters that render the image directly (rather than flattening it onto a fixed-color background) will carry the alpha channel through to the output PNG automatically. PixelTools' SVG to PNG, WebP to PNG, and general /convert tools work this way: because conversion happens via HTML canvas in your browser, any alpha data in the source is read and reproduced in the result rather than being composited onto black or white. This only works in one direction, though — it preserves transparency that already exists, it can't create transparency in a source format (JPG, flattened PDF) that never had any. If you're starting from a non-transparent format, transparency has to be added at the source (background removal, re-export with alpha) before any converter can carry it through. In PixelTools' own converter, the canvas is only pre-filled with a background color when the output format is JPEG (filled white, specifically, not black); PNG and WebP output skip that fill step entirely, so the alpha channel passes through untouched.