How to Resolve: Loom “Custom Branding” not applying to shared links

When custom branding fails to display on shared Loom links, recipients see standard Loom logos, default background palettes, and generic link previews instead of your company’s logo, custom colors, and personalized video frames. This disconnect happens when a video is saved outside the branded team workspace, an individual video override is active, or a link preview service is serving stale cached metadata.

Fast Fix

Move the video from your Personal Library to your Team Workspace folder. Custom branding assets (logos, custom colors, and custom subdomains) only apply to videos stored inside paid Team or Enterprise workspaces. If the video is already inside the workspace, check its individual settings to verify that “Default Workspace Branding” is toggled on.

---

Diagnostic Snapshot

Parameter	Operational Detail
Failure Layer	Workspace permission inheritance or external oEmbed/OpenGraph caching
Affected Assets	Custom logo, player accent colors, custom domain, CTA buttons
Plan Requirements	Loom Business, Business + AI, or Enterprise subscription
Admin Access Required	Admin needed to configure global assets; Creator access to move files

---

Diagnostic Path: Locating the Branding Breakdown

Use this quick check to identify why your branding is missing:

Custom branding missing on shared link
       │
       ├──> Where is the video file saved?
       │      ├── In "Personal Library" ──► Move file to "Team Workspace" folder.
       │      └── In "Team Workspace"   ──► Check file-level branding overrides.
       │
       ├──> Does branding show on Loom.com, but disappears when pasted into Slack/LinkedIn?
       │      └── YES: OpenGraph / oEmbed social cache is stale.
       │
       └──> Are you viewing the link as a Workspace Member or an External Guest?
              └── Member: Members may see internal player controls. Test in an Incognito window.

1. Workspace Location (Most Common): By default, desktop recorders and browser extensions may route new recordings to your private “Personal Library.” Personal libraries do not inherit company branding rules; only files housed under the shared Team Workspace display your custom theme.
2. Account Plan Mismatches: If your organization’s paid subscription lapsed, downgraded, or a user was accidentally provisioned into a free seat, custom branding features are automatically disabled.
3. Individual Video Settings Overriding Workspace Rules: Loom allows creators to disable player branding or adjust button styles per video. If you also have trouble displaying clickable links, consult Fix: Loom “Cta Button” not appearing on published video.

---

Step-by-Step Resolution

Step 1: Move Videos to the Team Workspace

Verify the storage location of the affected video:

1. Navigate to your Loom Library.
2. Look at the left sidebar navigation:
   • If the video is located under Personal, it will not display custom branding to outside viewers.
3. Hover over the video card, click the three dots (…), and select Move.
4. Choose your Team Workspace or a specific shared folder inside it. For issues organizing shared directories, refer to How to Resolve: Loom “Team Workspace” missing shared folders.

Step 2: Confirm Global Workspace Branding Configuration

Workspace Admins must ensure branding assets are active and saved globally:

1. Click your Workspace Name in the top left corner of the dashboard.
2. Select Settings > Branding.
3. Check each branding element:
   • Logo: Confirm a transparent .png or .svg (recommended minimum width 300px) is uploaded.
   • Accent Color: Ensure your company hex code is selected for player controls.
   • Custom Favicon: Verify your favicon is uploaded if on an Enterprise tier.

• Logo: Confirm a transparent .png or .svg (recommended minimum width 300px) is uploaded.
• Accent Color: Ensure your company hex code is selected for player controls.
• Custom Favicon: Verify your favicon is uploaded if on an Enterprise tier.

1. Click Save Changes at the bottom of the page.

[Admin Configures Branding Settings]
                 │
                 ▼
     [Team Workspace Folder] ─────────► All Videos Inherit Branding Automatically
                 │
                 ▼
    [Personal Library Folder] ────────► Standard Default Loom Player (No Branding)

Step 3: Refresh Stale Social and Messaging Previews

If the branding displays properly when you visit the link directly in a browser, but displays standard Loom previews when pasted into Slack, Microsoft Teams, or LinkedIn:

• The platform has cached the original OpenGraph (OG) metadata.
• For LinkedIn: Paste the link into the LinkedIn Post Inspector and click Inspect to clear the cache.
• For Twitter/X or Slack: Append a harmless query parameter to the end of the URL (e.g., https://www.loom.com/share/VIDEO_ID?v=2). This forces the messaging platform to crawl the link as a brand-new page and fetch your updated branded thumbnail.
• If your video cover image is also failing to update across external platforms, follow How to Resolve: Loom “Thumbnail” not updating after edit.

Step 4: Audit Embed Codes vs. Direct Share Links

When embedding Loom videos into websites (WordPress, Webflow, Notion):

• Using a stripped <iframe> code without your workspace parameters can bypass your branding.
• Always click Share > Embed on the Loom video page and use the full responsive embed code generated by Loom to ensure your custom player controls and logos load correctly.

---

Verifying Successful Application

To confirm your branding works as intended for external clients:

1. Copy the public URL of your video.
2. Open a clean Incognito or Private window (where you are not logged into your Loom account).
3. Paste the URL. You should see:
   • Your custom logo in the upper player frame or header.
   • The play button and progress scrubber rendered in your chosen accent color.
   • The absence of Loom’s default upgrade prompts.

• Your custom logo in the upper player frame or header.
• The play button and progress scrubber rendered in your chosen accent color.
• The absence of Loom’s default upgrade prompts.