Find the task that matches
Several static PNGs need the same integer enlargement
Choose 2×, 4× or 8×, inspect each success or failure, then download named PNGs with their ZIP and outcome manifest. A failed peer must remain visible in the result mapping.
Batch resize pixel-art PNGs in the browser →You need a crisp reusable file with transparent padding
Compare actual PNG and JPEG exports from one original. Check transparency separately from lossy color changes, and see why saving JPEG as PNG cannot recover the original pixels.
Choose PNG instead of JPEG for a crisp transparent sprite →A transparent sprite has a white or dark halo
Compare the same edge on black and white with smoothing disabled. Inspect partial-alpha color to distinguish a matte already stored in the source from a resampling problem.
Diagnose white or dark halos around transparent sprites →An Aseprite source needs a reproducible pixel enlargement
Export the original source through the tested native CLI and compare the output dimensions and pixel blocks; keep the editor version and source project.
Batch resize PNG assets with the Aseprite CLI →A sprite needs a reusable visible-color palette
Extract the twelve-color original, inspect exact RGBA counts and download the JSON plus the actual swatch PNG.
Extract a usable palette from a pixel-art PNG →Two sprite colors need replacements while the outline stays fixed
Set explicit RGBA mappings, then check all 82 changed pixels, the 40 outline pixels, eyes and alpha against the decoded original.
Swap a sprite palette without changing its outline →Transparent pixels make a palette count confusing
Compare visible and all-pixel policies. Keep the actual 13 decoded RGBA values separate from the 14 raw source reference values.
Count visible colors versus RGBA values in a PNG →Transparent borders should disappear without losing placement
Trim the asymmetric PNG to 7×6 and keep its original 16×12 canvas and offset (3,2); reconstruct its original placement.
Trim a transparent PNG and retain its original offset →A PNG exceeds a browser processing limit
Distinguish input, geometry, output and memory admission, inspect the precise rejection and recover with a smaller valid selection.
Recover from a pixel-art image size or memory rejection →
Keep each diagnosis separate
The original palette project and original trim project include separate raw-source references. Each walkthrough distinguishes those from actual browser downloads.
Start with the original batch PNG input pack for the scaling task, or the original edge and PNG/JPEG comparison project for the two diagnoses. The child walkthroughs explain the steps, expected result and failure boundary for each download.
Integer scaling repeats decoded pixels and preserves existing blur or damaged edge colors. Browser decoding and canvas export can round partially transparent colors, discard invisible RGB or omit metadata. Keep your source files when exact file RGBA, color profiles or hidden RGB matter; compare the output rather than assuming a lossless round trip through every browser.
The PNG alpha specification and canvas pixel-readback reference explain the format and codec boundary. The walkthroughs provide the original examples and their scoped observations.