Diagnosing dark sprite edges: a practical alpha compositing check

A transparent asset might appear flawless in an image viewer but appear darkened in a game. To determine the cause, verify that the image data and renderer agree on alpha representation. Mismatches can occur due to filtering, atlas padding, and color management. Straight and premultiplied alpha differ in how they store color and opacity.

Straight alpha stores color independently of opacity, while premultiplied alpha incorporates opacity into the stored color. To test, apply each formula per color channel using values between 0 and 1. A tiny numerical check with straight source value 1.0, alpha 0.5 and opaque black background (0.0) yields 0.5 for both formulas. However, an accidental multiplication of the premultiplied value by alpha again results in 0.25, causing a darker edge.

This simplified example does not account for color-managed rendering or real-world pipelines. To isolate the cause, use a single partly transparent test image and compare it over black, white, and saturated backgrounds. Check the importer, texture upload, shader, and blend settings together. Do not assume a filename indicates the GPU representation, as data may be converted during import.

Compare nearest and linear filtering, then inspect atlas padding. If the fringe changes with filtering, consider sampling. Recheck the actual target engine and export. Different viewers and blend modes may interpret data differently. For animations, inspect the same boundary on multiple frames to catch soft edges. MotifDeck allows artists to inspect extracted character frames, making this diagnostic applicable to transparent artwork generally, regardless of its creation method.