Brand asset injection

What it means & why it matters

What SessDev includes

• Ingestion of supplied brand assets via a structured handoff (Figma export panel, Google Drive or Notion) with one folder per asset family and a checklist of required variants and formats.
• Validation that each supplied file matches the required format and dimensions before integration begins — SVG with viewBox for logos, transparent PNG at documented sizes for icons, correct aspect ratio and weight budget for OG images.
• Wiring of the logo variants required by the design (full lockup, isotype-only, light theme, dark theme, monochrome) into header, footer and email templates — one Image component per variant, no hand-cropping.
• Generation and wiring of the favicon bundle from a supplied master (favicon.ico, 16/32/48 PNGs, Apple touch icon 180×180, Android maskable 192/512) into the app's icon manifest and head tags.
• Wiring of the Open Graph and Twitter card images supplied by the client (1200×630 for OG, 1200×600 for Twitter summary-large-image) into per-route metadata, with sensible fallbacks for routes that do not override.
• Setup of the web-app icon bundle for installable contexts — manifest.webmanifest entries, theme color, background color, display mode — from icons supplied by the client.
• Wiring of theme-color, msapplication-TileColor, mask-icon and Safari pinned-tab meta tags from the values supplied in the design handoff.
• Implementation of sensible fallbacks for missing variants — if only a single logo is supplied, the dark-theme slot reuses it with an inversion filter; if no monochrome variant is provided, the footer falls back to the full lockup. Fallback decisions are documented in the handoff note.
• Handoff document listing every asset slot, the file currently wired into it, the source filename received, and the procedure to swap an asset later without engineering involvement.

What is excluded

• Logo design, logotype creation or any form of original brand-mark authorship.
• Creation of new brand marks, sub-brand marks, product marks or campaign marks.
• Retouching of supplied artwork — fixing kerning, adjusting proportions, repairing low-quality scans, redrawing paths.
• Vector reconstruction of raster logos. If only a low-resolution PNG is supplied, the asset is rejected; reconstruction is a design-team activity.
• Color correction, profile conversion (CMYK to sRGB), gamma tuning or any photographic color work.
• Background removal, masking, alpha-channel creation or matte cleanup on supplied imagery.
• Original illustration, spot illustrations, mascots, hero artwork or supporting visual elements.
• Photo editing, compositing, retouching, beauty work or any image-manipulation activity beyond format conversion.
• Animated logo production — Lottie composition, SVG path animation, video intros or motion-design deliverables.
• Authorship of the brand system itself — defining usage rules, clear-space, minimum sizes, do/don't grids or brand guidelines documents.
• Mascot design, character design or any persona-based visual authorship.

Risks if this is mis-configured

• Wrong-format artwork blocks integration

  Logos delivered as flattened JPGs, icons supplied at the wrong dimensions, OG images compressed below the platform threshold — wrong-format artwork forces the design team back into the loop and slows the integration. Format validation in scope catches this early; reformatting itself is a design-team activity.

• Pixelated logo at retina or print scale

  A raster logo supplied at 200×60 looks crisp in a mockup and shameful on a retina header at 400×120. Without an SVG source or a high-resolution master, the live site downgrades the brand on every device. Reconstruction is out of scope; the only fix is a clean vector from the design team.

• Missing or stale favicon variants

  Browsers, bookmark bars, OS tab groups, Slack unfurls, search-result tabs and PWA installers each pull a different icon variant. Missing one variant produces a stale or generic icon in that context and erodes trust. The required-variants checklist in scope prevents this — provided the design team delivers every variant on the checklist.

• Broken or default OG image on share

  When a homepage or article is shared without a configured OG image, social platforms render a default crop or no preview at all — destroying click-through. We wire the supplied OG image and per-route overrides, but we cannot author the imagery itself. If the OG slot is empty in the handoff, the live site ships with a fallback only.

• Transparency or color-profile issues at runtime

  Logos saved with a white background instead of an alpha channel, PNGs in a CMYK profile, SVGs with embedded raster fragments — these surface as halos, wrong colors or render failures in production. Format validation flags them; correcting the source file is out of scope and returns to the design team.

• Trademark and rights unverified

  SessDev does not verify trademark registration, prior-art conflicts, or third-party rights on supplied artwork. If the client supplies a logo that infringes a registered mark, that liability remains with the client and its legal counsel. We integrate what is delivered; we do not clear rights.

• Asset sprawl and stale variants

  Without a single source of truth, multiple versions of the same logo end up scattered across header, footer, emails, social cards and PDFs — each subtly different. The handoff document in scope enumerates every slot and source filename so swaps are mechanical, but discipline must persist after launch. The Care retainer keeps the inventory tight.

Related scope items

• color_token_setupColor tokens consume the palette values supplied alongside the brand bundle. Tokens are wired here; palette authorship is excluded.
• typography_integrationTypography integration is the sibling activity — wiring the supplied typefaces and weights. Same exclusion principle: integration, not authorship.
• media_infrastructureMedia infrastructure provides the delivery primitives (next/image, CDN bindings, lazy-load) that serve the brand assets in production.
• content_injectionContent injection covers copy alongside imagery. Brand assets are imagery; copy follows the structured handoff defined there.
• technical_seoTechnical SEO consumes the OG image, favicon and theme-color metadata wired here for crawler and social-platform consumption.
• cms_blog_setupThe blog CMS reuses the brand asset slots wired here for per-article share images and editorial branding.

Frequently asked questions

Can SessDev design our logo?

No. Logo design and brand-mark authorship are design-studio deliverables and are explicitly out of scope. SessDev wires the final logo your design team or external studio delivers in the required formats.

Which formats must the brand bundle ship in?

Logo as SVG with a clean viewBox (no embedded raster). Favicon master as a high-resolution PNG or SVG. App icons as transparent PNGs at the documented sizes (180×180 Apple touch, 192/512 Android maskable). OG image as JPG or PNG at 1200×630 under the platform weight budget. The exact checklist is part of the kickoff handoff.

What if our supplied logo needs retouching?

It is returned to your design team for retouching before integration begins. SessDev does not retouch, redraw or color-correct supplied artwork. We integrate production-ready files only.

Can you design our OG share image?

No. We wire the OG image your design team supplies and configure per-route overrides for important pages. Authorship of the imagery itself — composition, typography on the card, art direction — is a design-studio activity.

How many favicon variants do you need?

The checklist covers favicon.ico, PNG variants at 16/32/48, Apple touch icon 180×180, Android maskable at 192 and 512, and Safari pinned-tab SVG when applicable. All from a single high-resolution master supplied by your design team.