Prepare Responsive PNG Product Cutouts

Remove a chosen RGB background, then download transparent PNG widths and a relative-path srcset snippet with every original source and native report retained.

• Choose one static PNG up to 1 MiB and 512 pixels per side. Enter a six-digit RGB key; tolerance and feather use encoded 8-bit RGB distance. Edge-only mode follows four-neighbor paths from the image boundary and preserves disconnected matching islands. Existing transparent pixels connect those paths. This does not detect a subject or correct spill. Choose 1–8 unique comma-separated widths, up to the source width; PNG variants retain supported alpha and use the original high-quality browser resize. The ZIP exposes every native variant and escaped relative-path srcset HTML, plus complete source, cutout/report and original native ZIP. Raw source metadata and private pixels remain. New PNG metadata follows the original container policy; color profiles and density may remain, so there is no anonymity guarantee. A width/alt refusal or cancellation retains the full cutout checkpoint. Upload files yourself and adapt the snippet paths.
• 32MiB outer ZIP/16MiB entry/4 CP/up to16 final entries. Source filename255 UTF16/1020 UTF8 bytes. Original60second tasks remain, owned90second connections. Consumer reruns only this newly supplied original key operation to verify source association, then calls the original responsive pack.
• PNG compression bytes are validated rather than predicted. Independent complete-file checks inspect every image pixel/chunk and every inner/outer ZIP member; resized boundary pixels use explicit interpolation bounds. Complete original native PNG/report compared byte-for-byte; original responsive ZIP compared across every complete member and every byte except exactly four original wall-clock DOS timestamp bytes per local/central header. Both complete raw archives and timestamps retained.