CDN and media assets
Upload, reference, list and delete images/media safely across tournaments, profiles and overlays.
Asset workflow
Use the CDN multipart upload API/UI for supported images and media. Store the returned asset identifier or URL in tournament artwork, badge/provider imagery, overlay nodes or pool art. Do not store binary data inside tournament settings or .bk.scene public properties.
The CDN resource supports upload, listing, image views and deletion. Global permissions distinguish manage/upload, deletion of one's own assets and deletion of all assets. Ownership checks still apply when an OAuth application has REST write scope.
Upload safety
Validate media type and size in the UI and API, use descriptive source filenames, and upload only content you may publish. Treat SVG and externally hosted URLs as active/untrusted content surfaces; never put secrets in query strings. Verify transparent edges and crop behavior for logos, banners, pools and overlay media.
Deletion and references
Deleting a CDN asset can break every record that references its URL. Search tournament branding, pool art, badge/provider records and overlay node assets before deletion. Replace references first, then remove the old asset. Scene exports may refer to asset GUIDs/URLs but do not necessarily embed the underlying media.
Broadcast media
Overlay media can use a CDN asset, external URL, WebRTC, HLS/LLHLS or Twitch. These sources have different autoplay, CORS, latency and audio behavior. Test from the actual browser/Electron environment and configure mute/control/loop explicitly.