Transparent PNGs fail where they are actually displayed
Route `transparent-background-png` targets stickers, badges, and UI chrome. Halos that hide on white artboards scream on photos or gradients. Test on the real hex values your app uses—including subtle grays. If assets go to video or engines, watch premultiplied alpha and mip bias. Freeze bit depth, color profile, and compression so batches stay consistent.
Suggested steps for transparent-background-png
- Decide whether drop shadows or keylines are allowed and whether PNG weight is capped.
- Composite on brand light, brand dark, and neutral gray to catch fringe colors.
- Run through the real CDN pipeline to ensure optimizers do not crush alpha edges.
remove bg (transparent) Q&A
Looks fine in Figma but fringe in Chrome—why?
Trust the browser; verify export presets and color-managed previews.
Do we need separate assets for dark mode?
Usually yes—pair on-light/on-dark exports or standardize a neutral stroke.
Thumbnails look soft—who owns that?
Validate at the platform’s thumbnail size; downstream sharpening differs from full-size review.
After shipping `transparent-background-png` stickers, design switches to dark mode and halos appear—who owns the fix?
Document light/dark asset pairs or a standard keyline in the design system; single PNGs should name the intended background hex.
Motion needs the same sticker—extra checks?
Confirm premultiplied alpha, working color space, and sequence export settings; flat PNGs often fringe when imported to NLEs.