Custom Branding

Burn-in logo watermarks vs. Player SDK overlay branding.

Custom Branding

There are two ways to put your brand on a video. Pick the right one for the right job — they solve different problems.

1. Burn-in watermark (transcoder)

At upload time you can choose CUSTOM branding and upload a PNG/SVG logo. FFmpeg burns it into every frame during transcoding — so the brand is in the pixels, indistinguishable from the source.

	Burn-in
When applied	At transcode time (one-shot)
Where visible	In the .ts chunks themselves
Removable by viewer	No
Cost	+0.5 credits / minute
Use it for	Long-term protection, “owned” feel

2. SDK branding overlay (Player SDK)

The Player SDK renders a small “Powered by …” string in one of four corners. It’s an HTML overlay — themed, positioned, and toggle-able at embed time.

	SDK overlay
When applied	At playback time (per embed)
Where visible	DOM only
Removable by viewer	Browser devtools (so don’t rely on it for protection)
Cost	Free
Use it for	Affiliate / partner attribution, light branding

<AnsdevPlayer
  apiKey={key}
  videoId={id}
  theme={{
    branding: {
      show:     true,
      text:     "Acme Films",
      position: "bottom-right",
    },
  }}
/>

Combining them

Most teams ship both — burn-in for the immutable brand mark, SDK overlay for context (channel name, episode number, partner credit). They don’t conflict; the SDK overlay sits on top of the video element.

Picking a logo

For burn-in, transparent PNG at the rendition’s resolution works best (the FFmpeg filter handles scaling, but you get the cleanest result feeding it the right size). For SDK overlay, it’s just text — no asset needed.