Scenario value of Add Images in logo
`logo-overlay-corner` supports 品牌角标与联名标识场景. Keep hierarchy, readability, and destination consistency stable with pilot validation, staged rollout, and anomaly logging.
`logo-overlay-corner`: read the brand book for mono/reverse/min height, pick a corner anchor + no-fly polygons, ship light and dark raster packs
- Start with contractual primary/secondary ratios and spacing, then draw invisible safe zones—mark centers cannot enter face ellipses or price hulls. Lock one anchor (often bottom-right) for the house mark, place partners on a secondary anchor ~20–35% smaller or split with a vertical rule—never let two marks share an edge kiss.
- Proof on white, mid-gray, and near-black plates, swapping reversed vs solid fills; if pale mats swallow the mark, use approved dark solids before random drop shadows. Below minimum pixel height, refuse to shrink—switch to a bar lockup or footer rail or you lose both legal clearance and recognition.
- Export layered names like `logo_primary` / `logo_partner` with margin screenshots; simulate native “LIVE” or “Official” chrome before placing corners so you never ship double-stacked badges. Rasterize from vector at ~2× final display width on an even-pixel grid to kill subpixel mush.
Logo overlay FAQ: co-brand scale, reverse legibility, minimum size law, native chrome simulation, raster chain
The partner insists on equal size—dual-head branding—how do we push back with evidence?
Run thumbnail legibility: whichever mark reads first is de facto primary; equal weight usually violates house guidelines. Propose secondary anchor + divider and archive the email decision—layout tools don’t negotiate contracts, but side-by-side exports accelerate alignment.
Reversed marks fade on pale gray products; brand forbids drop shadows—what’s still compliant?
Request approved dark-solid alternates or hairline dark rims with written exceptions before improvising glow. Attach unreadable failure captures to the waiver—subjective fights lose to documented samples.
Ops wants −2 px to expose more product while we’re already at manual minimum—does “still visible to me” count?
No—minimums are contractual, not eyesight tests. Reflow the crop or switch lockup; if the business overrides, legal must accept infringement risk in writing. Post-takedowns cost more than one extra row of pixels.
Short-video covers stack our mark over the platform play affordance—how do we preflight?
Import the latest cover template chrome, move marks into the documented safe belt or flip anchors per platform. Proof on-device thumbnails—desktop Figma mocks lie about thumb collisions.
Dragging vectors from PDF into the browser tool yields fuzzy rims—color mode or too many resizes?
Usually fractional scaling chains: export even-pixel canvases, snap to integer coordinates, supersample 2× then downscale once. Avoid screenshot-of-screenshot pipelines—each hop eats fine strokes.