Why Add Images is a repeatable brand-ops workflow
Add Images standardizes how one base visual becomes multiple publishable variants for branding, campaign states, meme distribution, and watermark previews. Define anchor rules, scale ranges, and acceptance gates before batch export.
Anchor dictionary + light/dark proofs + split tracks: define allowed layer roles per base image, lock geometry and contrast, sign off through each channel’s compression chain
- Ticket the base use (hero, PDP, social, client preview), default mat lightness, and no-fly polygons for faces, price strings, and barcodes. Pick one anchor (e.g., inset from bottom-right 2%) and a max overlay area; stress-test on your busiest, darkest, and palest masters and log opacity/stroke numbers—not “looks fine” anecdotes.
- Stack `base → hero info → brand → promo → flair`; proof each addition on light gray, charcoal, and a near-real product background. JPEG resampling kills hairlines—re-check at the shipped long edge and add a faint outer keyline or bump weight to the minimum readable width.
- Name exports like `_brandA_promo_off_wm25` and mirror sliders in a spreadsheet row. Batch only clones signed presets; when a campaign ends, freeze retired badge layers in the DAM so “latest” never ships last season’s corner mark.
Add Images FAQ: anchor drift, light/dark failure, layer fights, recompression, rights-safe delivery tiers
One corner-mark preset reads on white appliances but vanishes on moody lifestyle shots—do we really need two files or is there a reusable engineering fix?
Opacity alone cannot span the luminance gamut: ship positive, reversed, and thin-stroke variants—or mandate a bright keyline on dark bases per brand rules. Acceptance must use three worst-case plates, not the brand template gray, or ops will “fix” brightness by hand and your parameter log dies.
Marks clear faces but cover decimal points—finance says OCR breaks; how do we quantify safe gutters during overlay?
Treat price bounding boxes like faces: anchor relative to the price hull with a fixed pixel buffer and screenshot at 100%. If the marketplace crops dynamically, re-proof in the merchant preview, not only on the untouched master.
Transparent PNG logos show rainbow fringe on video thumbnails—is that export settings or stack order?
Audit premultiplication and repeated non-integer scaling; try matting on a plate matching the final background or add a 1px solid rim. Composite marks after the last resize in the player pipeline—artifacts usually live in the chain, not a single toggle.
Brand, 618 badge, and partner marks all “must” land—legal caps layers while growth wants noise—how do we prioritize without meeting theater?
Hard-cap counts: ≤1 evergreen brand, ≤1 seasonal, ≤1 partner, with a combined area ceiling; contracts beat opinions. Email exceptions and tag DAM rows—ad-hoc “just this once” becomes permanent unless governance says no.
Client previews need theft deterrence but screenshots still look premium—how do we avoid ugly slabs without skipping the contract?
Pair sparse diagonals or corner credits with a lighter center, and ship `preview_wm` separately from contracted `clean` masters via expiring links. Write acceptable annoyance levels into SOWs—tools render pixels, commercial boundaries must precede them.