Your Transparent PNG Looks Clean — Until You Put It on a Dark Background

Your Transparent PNG Looks Clean — Until You Put It on a Dark Background

Your sticker looks spotless on a white page — then it grows a dirty white ring the moment it lands on black. The background is already gone, so removing it again fixes nothing: what you are seeing is the faint residue the remover left along the edge. Run the PNG through the cleaner and it strips only that residue — anything under opacity 16, plus loose specks up to 30 pixels — and leaves the soft edge alone.

Try the toolClean Leftover Pixels in Transparent PNGsFind and remove faint pixels and small detached specks left behind in a transparent PNG. Your files stay in your browser and are never uploaded.loopyti.com

One caution before you start: if you already put the haloed PNG on a dark product photo and someone saw it, cleaning the file now does not unsee it. The halo is pixels inside the saved file, not a display glitch — clean the file and swap it in.

![Transparent PNG cleaner showing a coral star on a dark background before and after cleaning, with the white halo ring gone in the cleaned version](/blog/media/2026/11/a43e32e9-633d-4b3b-b0e2-d278f324cd2e.png

How to clean a transparent PNG in three steps

  1. Load the finished transparent PNGs. The tool takes transparent PNG or WebP files — up to 20 at once, 30 MB each. I loaded six 2000×2000 PNGs in one go: three with a white halo ring around a star, a heart, and a teal circle logo; two with three faint dots each; and one with a shadow touching the subject.
  2. Leave the defaults alone. The page shows them plainly: "Current settings: remove pixels below opacity 16 · remove detached specks up to 30 pixels · keep translucent edge pixels." The faint-pixel threshold is 16, the speck limit is 30 pixels, and "Keep soft translucent pixels along the subject edge (recommended)" is checked.
  3. Click "Find and clean", check the three views, then download. The red overlay marks what will be removed, the dark-background view shows what a buyer would actually see, and the checkerboard shows the real transparency. Download the cleaned PNGs — one file at a time, or all of them together as a ZIP.

Does it actually work? I tested six PNGs

Tested 2026-11-14, defaults unchanged, and re-tested the same day after the tool was fixed (the first version of this post described the old behaviour — see below). The halo rings measured alpha 9–11, about 12 pixels wide — just under the threshold of 16, so they were exactly the kind of residue the tool is built for. The dots measured alpha 8–13, radius 2–3 pixels, sitting 202–465 pixels from the subject. The shadow was an alpha-90 ellipse touching the circle logo.

Here is what came back, file by file:

  • Star, white halo ring: the ring is gone to the eye on a dark background. 18,987 faint pixels removed, 0 translucent edge pixels kept.
  • Heart, white halo ring: the same — the ring is gone. 28,068 faint pixels removed, 0 edge pixels kept.
  • Teal circle logo, white halo ring: the same — the ring is gone. 55,914 faint pixels removed, 0 edge pixels kept.
  • Star, three faint dots: all three dots are gone — I checked the pixel values at all six dot centres, and the alpha went from 8–13 down to 0. 5,712 faint pixels removed, 0 edge pixels kept.
  • Heart, three faint dots: all three gone. 4,554 faint pixels removed, 0 edge pixels kept.
  • Circle logo, attached shadow: the shadow is untouched in all three views. 4,899 faint pixels removed, 0 edge pixels kept — and the shadow itself is pixel-for-pixel identical: the count of alpha-90 pixels is 273,995 before and after.

![Red overlay view marking the faint halo pixels around a star for removal, with the cleaned star on the right](/blog/media/2026/11/f30dcba9-f553-4e5d-9fda-4eda62d554c2.png

The page totals it up as "Removed 194 detached specks and 118,134 faint pixels from 6 images." The faint-pixel total checks out — the six files add up to exactly 118,134. The 194 does not mean what it looks like. The two speck files each report "0 detached specks" even though their three dots are gone: faint dots land in the faint-pixel count, not the speck count. The 113, 22, and 59 on the halo files are one-pixel marks along the subject's outline, and 194 is just their sum. So read the total as 118,134 faint pixels removed, and ignore the 194 as a count of anything you would call a speck. Every file also reports "0 translucent edge pixels kept" now. That is the counter's wording for the faint band: the tool no longer keeps any pixel under opacity 16. The soft edge itself — the anti-aliased band at opacity 16 and above — is still there: on the star, 9,962 of 10,075 such pixels survive, and the checkerboard shows no rough edge.

![Teal circle logo on a dark background before and after cleaning, with the yellow halo ring visible in the original and gone in the cleaned version](/blog/media/2026/11/84d0f09d-2106-494e-b687-bd8c66eae3d2.png

One more honest check, on the downloaded files themselves: the halo is gone to the last pixel. Counting pixels with alpha 1–15, the star went from 18,987 down to 0, the heart from 28,068 to 0, and the circle logo from 55,914 to 0. In the dark-background view the cleaned files show no yellow dots at all, so the page's line "No dots in the cleaned image means it is clear" is now literally true. (An earlier version of this post said a thin, broken rim stayed — that was true before the fix, and it is fixed now.) At normal size the ring itself is invisible — and on the checkerboard all six files came out clean, with no rough or jagged edge anywhere.

![Checkerboard view showing the cleaned star on transparency with no rough edges](/blog/media/2026/11/4c87fc9f-c13d-4b11-a484-503dbaef2e2a.png

![Two times close-up of a star tip on a black background showing the faint fringe on the original and the cleaner edge after cleaning](/blog/media/2026/11/0056be6e-8f89-49d8-a7cb-4513878e4d09.png

Why the halo only shows up on dark backgrounds

A background remover does not cut a clean line. Along the boundary it leaves pixels that are neither fully transparent nor fully opaque — alpha 9 to 11 in my samples, just under the tool's default threshold of 16. On white, those pixels are white on white, so they disappear. On black, the same pixels read as a white ring. That is why "clean on white" and "dirty on black" can be true of the same file at the same time — and why the fix is not a better background removal, but a pass that removes pixels under the threshold, takes out detached clusters by size, and keeps the translucent pixels that touch the subject as its edge.

What about the other ways?

Re-running background removal works, in a way. But the same remover can leave the same boundary pixels again, and every pass shaves a little more off the subject's edge. You would be reprocessing the whole background to fix a rim.

Erasing the edge pixels by hand in an editor works too. It is also thousands of pixels around a 2000×2000 outline, and the three dots in my test are hard to even find at normal zoom.

Using the PNG only on white backgrounds works — until it doesn't. The file stays dirty, and the ring comes back the moment it lands on a dark listing photo or a coloured banner.

The cleaner's place is the middle case: the background is already removed, and only the boundary residue is left — stickers and logos headed for a dark background.

What it won't do — read this first

  • It does not remove shadows or glass effects that touch the subject. My alpha-90 shadow came out pixel-for-pixel identical — 273,995 pixels before, 273,995 after. The page says so plainly: "Translucent areas such as shadows or glass effects are kept when they touch the main subject."
  • The halo is now removed to the last pixel. I counted alpha 1–15 pixels in all six downloaded files: zero in every one. (An earlier version of this post said a thin rim stayed — that was true before the fix, and it is fixed now.)
  • The speck counter does not count faint dots. Two files with six dots removed between them both report "0 detached specks." Do not read that number as how many specks were removed.
  • Cleaned files now come out smaller than the originals. My star PNG went from 83,943 bytes to 55,104 — about two-thirds — and the six-file ZIP is 410,938 bytes against about 525 KB of originals. (An earlier version of this post said they ballooned to ten times — that was true before the fix, and it is fixed now.)
  • JPGs can't be cleaned. "Only transparent PNG and WebP images are supported. JPG files cannot contain transparent pixels." There is no transparency to clean in a JPG.
  • There is no zoom in the preview. Clicking the preview image does nothing, so I checked the edges by enlarging crops of the actual downloaded files instead.
  • Very faint pixels may shift colour slightly when saved — the page warns that "the difference is usually hard to see." I did not measure a colour shift.
  • Your files stay in your browser and are never uploaded. Every shape in this post's samples is made up, so there is no personal data or trademark in them either.

The one line to remember

Don't remove the background again — clean the edge it left behind.

Try the toolClean Leftover Pixels in Transparent PNGsFind and remove faint pixels and small detached specks left behind in a transparent PNG. Your files stay in your browser and are never uploaded.loopyti.com

FAQ

Do I need to remove the background again? No. This tool is for PNGs whose background is already removed — it only cleans the leftover pixels. If your image still has a background, remove that first, then clean the residue.

Will it remove the shadow under my product? No. Translucent areas that touch the subject, like shadows or glass effects, are kept on purpose. My alpha-90 shadow came out pixel-for-pixel identical, 273,995 pixels before and after.