A transparent PNG can look sharp on a checkerboard and still show a white fringe in dark mode. The edge pixels may carry color left over from the source background. Test the exported file on the same light and dark colors that are likely to sit underneath it at delivery.
Make a pair of test surfaces
Picture an app badge that must fit a navigation rail. Place the same PNG at exactly 48 pixels on a light panel and a dark panel. Run the same check at the original export size. If the badge looks slightly bigger on dark, inspect the outer pixels for an opaque rim. If it seems thinner on white, look for holes where edge color merges into the backdrop. The difference between panels helps separate poor contrast from an alpha defect.
Trace the problem to the delivered file
Reopen the downloaded image in an editor that shows transparency. File names and extensions don't guarantee alpha exists. If the asset was flattened during an export or upload, an entire solid matte may be present. For assets with correct alpha but a colored halo, adjust only contaminated boundary pixels. Keep internal holes transparent when they should show the app surface and keep highlight details that belong to the subject.
Use the actual placement for the sign-off
Start with the background remover for a photographic cutout. Approve the export only after you view both variants at the size the interface uses. If a logo intentionally has a white outline, preserve it and document that choice so future reviewers understand why they see it on dark surfaces. For photos, check that the edge does not create an unintended stroke in either mode.


