Check the final PNG in your browser
- Download or export the image you intend to use. Choose the original file, rather than taking a screenshot of its preview.
- Open the PNG Transparency Checker and drop in that file, or choose it from your device.
- Read the verdict and the fully transparent, partially transparent, and fully opaque pixel counts. Use the table below to interpret the result.
- Compare the white, black, and saturated-color previews. The background should show through the areas you wanted to remove. Check that the subject, its holes, and any intended shadow still look right.
The checker reads the selected image in your browser; it does not upload the image. It accepts files up to 25 MiB (26,214,400 bytes) and 16,000,000 pixels. A small compressed file can still exceed the pixel limit: multiply its width by its height. For larger images, use the Python inspector below on the original file.
The previews fit the image into a smaller canvas. Use them to spot a white rectangle, painted grid, or obvious fringe. For fine hair, tiny text, or a large product photo, reopen the PNG in an editor and inspect the edge at full resolution. Downloading a JSON report is optional; it is useful when checking a batch or handing a file to someone else.
| Result | What it establishes | What to do |
|---|---|---|
Transparency foundPASS_ALPHA_IN_USE | At least one pixel in the decoded image has alpha below 255. | Check where transparency occurs. A tiny transparent corner can pass while the unwanted background remains. |
Alpha is present but unusedHOLD_ALPHA_UNUSED | The file declares alpha or tRNS, but the decoded image is fully opaque. | If you need a cutout, inspect the background layer, mask, and export settings. |
No transparency foundFAIL_OPAQUE | No transparency storage was found, and the decoded image is opaque. | Remove the background in the source and export again. Changing the extension cannot add transparency. |
File checksum problemHOLD_CRC_ERROR | A parsed PNG chunk has a checksum mismatch. | Retrieve the original download or re-export from the source before relying on this copy. |
File could not be readERROR_UNREADABLE | The checker could not read the signature, structure, or image data. | Check that you downloaded an image file, then recover or re-export it. |
These are results for the decoded image, not a guarantee that the background was removed correctly. The precision and animation limits are explained near the end of this guide.
Check transparency in an image editor
A contrasting layer underneath the PNG provides a useful visual check. Open the exported PNG as a new document first. Testing an unsaved layered project can miss a background that was introduced during export.
In Photoshop
- Open the PNG and keep its image layer visible.
- Create a layer below it and fill that lower layer with a strong color, such as magenta. Keep the image layer at full opacity with normal blending.
- Look around and through the subject. The lower color should appear in the removed background and any intended openings, such as a handle or the center of a letter.
- Change the lower layer to black, then white, and inspect the edge. An opaque painted checkerboard stays visible when the lower color changes.
Before exporting the repaired image, hide the temporary color layer and any unwanted background layers. In File > Export > Export As, select PNG and enable Transparency. Adobe documents this setting in its Export As options. Open the new export and repeat the check.
In GIMP
Open the PNG, then place a solid-color layer underneath the image layer and change that lower layer between contrasting colors. The GIMP transparency guide also explains how to inspect the Alpha entry in the Channels dialog.
If the layer lacks alpha, use Layer > Transparency > Add Alpha Channel. Adding the channel only makes transparency possible; it does not remove an existing white background. Remove or mask the unwanted area, hide the temporary test layer, and export as PNG. Reopen that exported file to check it.
Reducing the whole image layer's opacity makes the subject fade as well. For an opaque logo with a transparent surrounding area, leave the logo at full opacity and change the background area through a mask or pixel transparency.
Why a white background or checkerboard can mislead you
An image viewer has to put something behind transparent pixels. A white viewing surface can make a valid cutout look as though it has a white rectangle. A black viewing surface can create the same confusion with a black rectangle. Change the surface color or place the file over a colored layer before editing the image.
A checkerboard has two possible origins. The editor may draw it behind transparent pixels, or the file may contain ordinary gray and white squares. In the second case, the squares remain when you place the image on a different background. An AI-generated image or a screenshot can contain that painted pattern.
The extension is another weak clue. Renaming logo.jpg to logo.png leaves the file's encoding unchanged. Converting a JPEG into a real PNG also preserves its rectangular background unless you remove that background. A valid PNG can be completely opaque.
Read the alpha counts
Alpha describes opacity. In the checker's 8-bit decoded view, 0 means fully transparent, 255 means fully opaque, and values from 1 to 254 mean partially transparent. Read the three counts together; the minimum alpha value alone cannot tell you whether a cutout is useful.
| What the report shows | What it means for your image |
|---|---|
| Every pixel is fully opaque | The decoded image has no transparent area, even if it has an alpha channel. |
| Transparent surroundings, opaque subject, some partial pixels at the edge | This can be a normal cutout with a smooth boundary. Confirm the shape visually. |
| Only a few non-opaque pixels | Transparency exists, but it may be an accidental corner or a tiny hole. Look for the background you actually wanted removed. |
| Many partial pixels, with no fully transparent pixels | The image is translucent in places, but it has no completely clear area. This can suit glass or a fade; it may fail a clean-background requirement. |
| Every pixel is fully transparent | The image is invisible. If you expected a visible subject, inspect the mask or export. |
| No partial pixels, but both transparent and opaque pixels exist | The mask has a hard boundary. This can suit pixel art; inspect curves and small lettering for jagged edges. |
There is no universal percentage of transparent pixels that a good PNG must have. A tightly cropped badge and a small object on a large canvas can have very different counts. Check that the location and amount of transparency fit the intended composition.
How to read a sample report
The clean soft-edge sample is 420 by 420 pixels, or 176,400 pixels in total. The inspector counts 93,318 fully transparent pixels, 3,525 partial pixels, and 79,557 opaque pixels. The clear surroundings and the soft edge appear in separate counts, so you can distinguish them from the opaque part of the badge.
Its visible-pixel box runs from (55, 65) to (365, 355), with the right and bottom coordinates excluded. That makes the visible area 310 by 290 pixels. The non-opaque-pixel box spans the full canvas because the transparent surroundings reach its outer edges. That full-canvas box does not mean the subject itself is translucent.
A bounding box only encloses pixels. It cannot show every hole inside a shape, distinguish a wanted shadow from residue, or establish that every outside pixel is clear. Use the preview to check those details.
Compare five PNGs with different results
Try the checker's Painted checkerboard example, then Real transparency, and compare their results. These are original sample images created to demonstrate the differences below. The verification kit includes them if you want to try the same checks in an editor or with Python.

| Example | Observed result | What to notice |
|---|---|---|
| Real transparency | PASS_ALPHA_IN_USE | Clear surroundings and a partly transparent soft edge. |
| Painted checkerboard | FAIL_OPAQUE | All 176,400 pixels are opaque. The grid is part of the picture. |
| Unused alpha | HOLD_ALPHA_UNUSED | RGBA storage exists, but every alpha value is 255. |
| White-edge risk | PASS_ALPHA_IN_USE, with a light-edge review signal | Its alpha counts match the clean file, but pale edge colors produce a fringe on dark backgrounds. |
| Indexed tRNS | PASS_ALPHA_IN_USE | 94,783 pixels are clear and 81,617 are opaque, using palette transparency. |
If you use the Python inspector, the saved sample results let you compare its output with the expected outcomes. They cover these five images and three damaged or invalid files. Run the samples before relying on a batch report for your own assets.
Inspect edges, shadows, and holes at the size you will use
A PNG can contain transparency and still leave an ugly outline. Partly transparent boundary pixels carry both color and opacity. If their color includes white from the old background, a pale fringe can appear when the image is placed on a dark surface.

Look on white for dark residue, on black for pale residue, and on a saturated color for patches that blend into neutral surfaces. A checkerboard helps locate clear areas, but can make small edge defects harder to notice. Include the actual destination background if it differs from these test colors.
Inspect at 100% to see individual image pixels, then at the intended display size. Zoom further to locate a defect, but judge the repair at the size where people will see it. A tiny fringe that disappears on a large product photo may remain conspicuous around a small navigation logo.
| Asset | Inspect closely | Avoid this repair mistake |
|---|---|---|
| Logo or small text | Holes inside letters such as A and O, narrow gaps, curves, and the smallest display size. | Shrinking the mask until thin strokes or intended white details disappear. |
| Product cutout | Handles, spaces between parts, reflections, and contact shadows. | Deleting every white area, including labels or highlights on the product. |
| Hair, fur, or feathers | Stray background color between fine strands and abruptly clipped tips. | Forcing every edge pixel to be either fully opaque or fully transparent. |
| Glass, smoke, glow, or soft shadow | Whether the destination color shows through the effect naturally. | Removing all partial alpha even though translucency belongs in the asset. |
The checker's light-edge or dark-edge signal counts certain colors beneath partial alpha. It does not locate or diagnose every halo. A white subject can legitimately trigger the light signal, and a colored fringe can exist without triggering either signal. Compare the rendered image before changing its mask.
Fix transparency problems
A white rectangle or painted checkerboard remains
If the decoded image is opaque, return to the editable source. Hide an unwanted background layer or create a mask around the subject. On a flattened image, background removal can provide a starting mask, but inspect places where the subject and background share colors. Replacing the background with a drawn checkerboard only creates a different opaque background.
If the image already passes, identify which areas are transparent. A clear corner does not remove a white rectangle behind the subject. Check openings inside objects separately: a transparent outer edge can coexist with an opaque white patch inside a mug handle.
The file has alpha, but the background stays solid
Look for an enabled background layer, a disabled or inverted mask, or a mask attached to the wrong layer. When the source looks correct and the export does not, inspect the export preview and transparency option. Reopen the export in a new document so you are checking the saved result.
An opaque PNG is appropriate when the design intentionally includes a rectangular background. Only remove it when the destination requires a cutout.
A light or dark halo surrounds the subject
View the mask against the destination color and determine whether the problem is leftover background outside the subject or contaminated color in the soft boundary. Refine the mask for leftover areas; use edge-color cleanup carefully for a fringe within the boundary. Contracting the whole selection can damage lettering, fine hair, and thin product parts.
Keep a copy of the original and compare the repair at normal display size. Check both light and dark backgrounds after each change; a repair that hides a pale fringe on black can create a dark outline on white.
The subject looks faded or has vanished
If the subject should be opaque, check whole-layer opacity and whether the mask has gray values across the subject. For an unexpectedly invisible export, inspect whether the subject layer was hidden or the mask removed everything. An alpha range of 0 to 0 means the decoded image is entirely clear; another background color will not bring it back.
The checker reports damage or cannot open the file
Download the original again or export a fresh copy from the source. A screenshot creates a new picture of the displayed result; it cannot recover missing source pixels or the original alpha. A tolerant viewer may display a damaged file while another decoder rejects it. Matching checksums and a successful decode are useful checks, but the inspector is not a complete PNG conformance validator.
When transparency disappears on a website or after sharing
Compare the original PNG with the file that reached the destination. Save the delivered image file, rather than taking a screenshot of the page, and check that copy. This separates a changed file from a background supplied by the viewer or webpage.
- If the original is transparent and the delivered copy is opaque, examine the intervening export, upload, resize, or conversion step. Compare the actual file formats and dimensions.
- If both files retain the intended transparency, inspect the destination. A white image element or container background will show through clear pixels. Temporarily change that background to a contrasting color.
- If the subject itself is faded only on the page, inspect CSS opacity on the image and its ancestors. CSS opacity affects the rendered element, including its contents; it does not remove a particular background color from the file.
- If the wrong image remains visible after replacement, confirm the image URL and which file the page is loading before editing the mask again.
For a slide, design document, or message attachment, insert or download the actual image file. A screenshot records the current backdrop, and a copied preview may not be the original asset. Test the copy you receive instead of assuming the transfer preserved transparency.
A SHA-256 hash in the report identifies the checked bytes. Different hashes establish that the files differ, but do not tell you what changed: metadata or compression can change while the visible pixels remain the same. Decode the delivered copy to find out whether transparency survived.
Check an AI-generated PNG after downloading it
Request a transparent background, then inspect the downloaded output with the same methods. Asking for a checkerboard can produce a picture of a checkerboard. If that happened, edit or regenerate with a request to remove the background and preserve the subject's opaque details, then inspect the new download.
Keep image creation and file checking as separate tasks. The image prompting guide covers generation and revision instructions. This guide checks the resulting asset, including files from editors, stock libraries, or other image generators. A pass on one file says nothing about the success rate of future generations.
Use Python for a quick answer or a folder of images
Read one image's alpha range
Install Pillow with python -m pip install Pillow. Save the following as check_alpha.py in the same folder as logo.png, then run python check_alpha.py. Replace the filename in the script with your own.
from PIL import Image
with Image.open("logo.png") as image:
if image.format != "PNG":
raise ValueError("The file is not a decoded PNG.")
alpha = image.convert("RGBA").getchannel("A")
minimum, maximum = alpha.getextrema()
counts = alpha.histogram()
print("Alpha range:", minimum, maximum)
print("Fully transparent:", counts[0])
print("Partially transparent:", sum(counts[1:255]))
print("Fully opaque:", counts[255])
Pillow's getextrema() returns the minimum and maximum values in a band. Here, 255 255 means the converted image is opaque, 0 0 means it is invisible, and a minimum below 255 confirms transparency in the converted image. Converting to RGBA lets the check include palette transparency instead of relying on the original mode label.
This short script decodes the image; it does not audit the chunk structure or every animation frame. It also converts to an 8-bit RGBA view. Use the inspector for its additional structural checks, and read the precision limit below before evaluating a 16-bit source.
Save reports and stop a batch on non-pass results
Download the PNG Transparency Inspector for signature and chunk checks, decoded counts, bounding boxes, animation detection, and JSON output.
python png-transparency-inspector.py "logo.png" --output "logo-alpha-report.json"
# macOS or Linux: the shell expands the wildcard.
python png-transparency-inspector.py exports/*.png --fail-on-nonpass
# Explicit filenames also work on Windows.
python png-transparency-inspector.py "exports/logo.png" "exports/icon.png" --fail-on-nonpass
The JSON contains a results list, including when you inspect one file. Look inside each result for verdict, decoded, and file.sha256. Without the flag, the process can complete successfully while reporting an opaque image. With --fail-on-nonpass, it returns exit status 2 if any file has a non-pass verdict.
A batch that accepts every PASS result still accepts a nearly opaque image with one clear pixel, an entirely invisible image, or a file with a bad-looking edge. If a project requires an opaque subject and a fully removed background, inspect those properties separately before accepting the assets.
Technical limits: storage, 16-bit PNGs, and animation
An alpha channel is only one way to store transparency
The PNG specification defines explicit alpha and transparency through a tRNS chunk:
| IHDR color type | Transparency representation |
|---|---|
6: truecolor with alpha | An alpha sample accompanies each RGB pixel. |
4: grayscale with alpha | An alpha sample accompanies each grayscale pixel. |
3: indexed color | An optional tRNS table assigns opacity to palette entries. |
2: truecolor; 0: grayscale | An optional tRNS value makes one exact color transparent. |
A palette entry can be transparent without being used by any pixel. An explicit alpha channel can likewise contain only opaque samples. Checking the decoded pixels avoids treating unused storage as visible transparency.
PNG-8 and PNG-24 export names
PNG-8 uses an indexed palette and can have transparent areas. PNG-24 in an export menu does not automatically mean transparency is absent: Adobe's export documentation includes a Transparency option for PNG-24. Check the exported file instead of accepting or rejecting it by the preset name.
The checker's PNG bit-depth field describes the stored sample precision. It is a different label from the export preset's PNG-8 or PNG-24 name. For example, an RGB image with 8-bit samples uses 24 color bits per pixel before any alpha sample is added.
The reports use an 8-bit decoded view
A PNG may store 16-bit samples, where full alpha is 65,535. The browser checker reads an 8-bit canvas buffer through getImageData(); the Python inspector converts to Pillow's RGBA mode. Their reported alpha values run from 0 to 255, even for a 16-bit source.
Small differences near full opacity can disappear in that conversion. An opaque decoded result therefore cannot prove that every original 16-bit alpha sample equals 65,535. If exact source precision matters, inspect the original samples with a decoder that preserves 16-bit alpha. Resizing or converting the file for inspection changes the data you are trying to check.
One decoded frame cannot establish an animation's transparency
The inspector detects the APNG marker, but its Python report covers the initially loaded image. The browser checker samples one rendered image and does not produce a per-frame analysis. Later frames can contain a different background, and a default still image can differ from the animation.
For an animated PNG, review playback over the intended background and use a frame-aware decoder to examine composited frames, including blending and disposal. A single pass or an invisible first image cannot establish what the whole animation displays.

Before handing over the PNG
- Check the exact exported or delivered file, including any resized version that will actually be used.
- Confirm that transparency is in the required areas and that the intended subject remains visible.
- Inspect edges and internal openings against contrasting colors at the destination size.
- For animation, inspect the full sequence; for exact 16-bit requirements, inspect preserved source samples.
- If someone resizes or re-exports the file, check the new copy. The old report describes the old file.
