Batch PNG→TIFF: poison files, ambiguous ICCs, and sloppy naming corrupt whole libraries faster than single obvious decode errors
`batch-png-tiff` supports DAM normalization where inputs hide wrong extensions, nested ICC tags, and crop metadata while outputs must feed TIFF-only ingest pipelines. Divergent default color management makes the same SKU diverge between mobile mocks and print contracts; missing alpha QA introduces gray mist on white products. Use content hashes, atomic writes, and error-class queues; enforce decode timeouts and RSS ceilings so one bad frame cannot stall overnight jobs.
Batch migration: freeze naming templates and default color science, stress-test mixed samples for memory, then reconcile manifests and quarantine failures
- Freeze manifests and templates like `{collection}/{sku}_v{rev}.tif`; smoke-test transparent, P3, sRGB, and oversized PNG mixes; tune concurrency only after measuring failure rates and RSS.
- Post-run, compare expected keys, success counts, and alpha histogram watchdogs; quarantine tiny files or sudden alpha shifts; spot-check barcodes and 7 pt type for systematic blur.
- Publish to read-only prefixes and invalidate CDN caches; archive prior manifests; change logs must capture compression defaults, ICC embedding, and converter builds—no verbal tweaks.
PNG to TIFF (bulk governance) FAQ: idempotency keys, parallel overwrites, Display P3 soup, immutable releases, and compliance sampling
Night jobs fill disks to 90% and emit truncated TIFFs—how do we stop silent bad publishes?
fsync temp files, atomic rename after close, validate TIFF magic and minimum byte thresholds, and pause workers when free space drops below reserved watermarks.
Two workers race the same object key and last-writer-wins clobbers assets—what naming fixes that?
Use content hashes or immutable version suffixes with conditional writes; on conflict, diff exporter settings before manual merges.
Libraries mix Display P3 and sRGB PNGs—how do we branch policies instead of assuming sRGB everywhere?
Record source ICC per row, branch transforms, or unify with explicit reports; silent sRGB guesses will explode finance color-matching disputes.
Finance demands Zip compression; printers want uncompressed for compatibility—how do we encode exceptions?
Split lanes: derivatives may use Zip while press masters follow shop-written uncompressed rules; encode lanes in filename prefixes to prevent mis-shipments.
Some “white background” PNGs are sloppy desktop captures with shadow halos—how does QA intercept them?
Route non-pure backgrounds to manual review; mandate controlled photography or approved masking services; block ops from swapping hero assets without design sign-off.