Running on Loom?

Loom embeds failing or SSO stuck? We sort it out.

Loom is lovely until a video refuses to embed inside a help center because the iframe policy was tightened, SSO breaks after the Atlassian acquisition realigned tenant mappings, or the Record SDK cannot capture system audio on a hardened laptop. We rewire the embed, bring the SSO onto Atlassian Access, and get the recorder working on the devices your team actually uses.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

loom-embed.log

still broken

What it is

Loom at a glance

Loom is an asynchronous video messaging tool founded in 2015 by Joe Thomas, Shahed Khan and Vinay Hiremath. It became widely used for quick video messages that replace a meeting with a recording: open the Chrome extension or desktop app, hit record, and send a link. Atlassian acquired Loom in 2023, and the product now sits alongside Jira, Confluence and Trello in the Atlassian line.

The platform covers screen and camera recording through a Chrome extension, a desktop app and a mobile app, plus a web recorder, with transcripts, AI titles and summaries, viewer analytics, workspace permissions and embed options. It offers a Record SDK for embedding the recorder into third-party products, an Embed SDK for playback controls, a REST API, OAuth 2.0 and webhooks on events like video uploaded and viewer identified. SSO moved from Loom-native to Atlassian Access after the acquisition, with SCIM provisioning available on higher tiers. The problems we see are usually embed-related (iframe policies, workspace privacy and CSP headers blocking videos), SSO-related (identity provider mapping after the Atlassian migration), or Record SDK integrations that fail on specific browsers or hardened endpoints.

Type
Asynchronous video messaging and screen recording platform
First released
2016, originally as Opentest
License
Proprietary SaaS, per-user pricing with Free, Business and Enterprise tiers
Maintained by
Loom, Inc. (an Atlassian company)
Typically used for
Async updates, product walkthroughs, customer support videos, bug reports, sales demos, embedded video in help centers

The honest version

Loom pros and cons

No technology is all upside. This is where Loom earns its place and where it tends to cause trouble.

Where Loom is strong

  • Recording is genuinely low frictionThe Chrome extension and desktop app start recording in a few seconds, the editor is simple, and the shared link is ready before you have finished speaking. For async updates this changes behaviour.
  • Transcripts and AI summaries are usefulAutomatic transcription, AI titles and summaries, and chapter detection make videos searchable and scannable rather than a wall of play buttons.
  • Viewer analytics beat sending a fileWho watched, how far they got, where they rewound, and whether they finished give the sender a real sense of engagement that email attachments do not.
  • Embed options are flexibleiframe embeds with privacy controls, workspace-only sharing, password-protected videos and custom domains cover most of the ways teams want to surface videos inside their own product.
  • Record SDK for embedded recordingTeams can embed the Loom recorder inside their own app, so a support tool, bug reporter or onboarding flow can capture video without users leaving the product.
  • Atlassian integration is now nativeSince the acquisition, Loom videos embed cleanly into Jira issues, Confluence pages and Trello cards, which closes a loop for teams already on the suite.

Where Loom bites

  • Per-user pricing jumps at BusinessThe Free tier is generous but capped on video length and library size, and the Business tier is where most useful features (transcripts, unlimited length, viewer insights) live, so teams usually end up paying more than they planned.
  • The SSO migration to Atlassian Access is disruptiveOrganizations that had Loom-native SSO have to move to Atlassian Access, which reshapes the identity provider mapping and sometimes breaks group memberships and SCIM provisioning during the transition.
  • Embeds hit CSP and iframe policiesModern help centers, documentation sites and intranets apply Content Security Policy headers and X-Frame-Options rules that block Loom embeds unless explicitly configured. The fix is on your end, not Loom's, and is not always obvious.
  • System audio capture is inconsistentCapturing tab audio or system audio depends on the browser, the operating system and the extension version. Safari in particular is limited, and hardened laptops with endpoint protection can block the capture entirely.
  • Video processing can take a long timeLonger videos spend time in processing before they are shareable, and a ten-minute recording occasionally sits in 'processing' for hours when the queue is busy. The sender does not know when to retry.
  • API is relatively limitedCompared to the larger Atlassian products, Loom's public API surface is narrower. Many workflows that would be API-driven elsewhere rely on webhooks or Zapier instead.

Sound familiar?

Common Loom problems we fix

The Loom problems that bring people to us, and what you have once each one is fixed.

X-Frame-Options SAMEORIGIN

Loom embed refused by the host page

A help center or docs site whose X-Frame-Options or Content-Security-Policy headers do not include loom.com or the Loom custom domain. The video renders as an empty frame or a warning banner instead of playing.

CSP and X-Frame headers aligned

SAML audience no longer matches

SSO breaks during the Atlassian Access migration

A tenant that moved from Loom-native SSO to Atlassian Access, with the SAML audience value changing in the process. Users who worked on Friday cannot log in on Monday.

SSO on Atlassian Access working

embed privacy: workspace-only

Embedded videos require a login that the viewer does not have

A video set to workspace-only visibility embedded on a public help center, so external viewers see a sign-in prompt rather than the video. The default was wrong for the context.

Embed privacy matches audience

Record SDK: system audio unavailable

Record SDK cannot capture system audio

An integration that expects system audio to always be available, with Safari users or Linux users seeing partial recordings. Endpoint protection on hardened laptops can also block the capture entirely.

Record SDK degrades gracefully

video stuck in 'processing' for 3 hours

Long videos get stuck in processing

A recording that exceeded the tier's max duration limit, or a queue backlog on the Loom side during a busy window. The sender does not know whether the video will complete or needs to be re-recorded.

Processing status monitored

SCIM: provisioning deferred

SCIM users do not appear in Loom after Atlassian Access change

A SCIM pipeline that was syncing to Loom-native directly, broken during the move to Atlassian Access. New hires have IdP sessions but no Loom workspace membership.

SCIM through Atlassian Access working

Zapier: deprecated endpoint returned 404

Legacy Zapier or API integrations break after endpoint changes

A Zapier zap or an older API client using an endpoint that has since been removed or renamed, usually after the Atlassian-era API consolidation. Workflows stop firing without a clear error.

Integrations on current endpoints

download blocked: workspace policy

Workspace policy blocks a legitimate download

A workspace with downloads disabled globally that is also used for one team that needs to archive legal recordings. The policy is too broad for the business.

Download policy scoped per team

What we do

Loom help, from embed to SDK

Call us for one failing embed, or let us own the Loom workspace and all the integrations around it.

Rescue
An embed that will not render, SSO locked out mid-migration, or the Record SDK crashing on specific browsers. We get viewers back to the video first and explain the cause second.
Embed configuration
iframe, custom domains, privacy settings and CSP headers worked out against your help center, docs site or product UI so videos render for the right audience.
SSO migration to Atlassian Access
Moves from Loom-native SSO to Atlassian Access with group mapping preserved, SCIM provisioning redirected, and the tenant edge cases handled.
Record SDK integrations
Embedded recording inside your own product, with browser fallbacks, hardware permission handling, and the hardened-endpoint edge cases documented.
Workflow automation
Webhook consumers, Jira and Zendesk sync, viewer analytics into the warehouse, and reporting that goes beyond the native dashboards.
Managed Tech
Monitoring on embed health, SSO certificate rotation, API deprecation watch as Loom aligns more deeply with Atlassian, and an engineer on call when something in the recorder breaks for a key team.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Loom alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Loom questions

Something else? Call+1 737 727 7327

Why does our Loom embed not render on our help center?

Three usual causes: the help center's Content Security Policy header does not list loom.com (or your Loom custom domain) as an allowed frame source, X-Frame-Options is set to SAMEORIGIN or DENY, or the video itself is set to workspace-only privacy which requires a sign-in. We work through all three in order: add loom.com to frame-src in your CSP, switch X-Frame-Options to a policy that allows the embed, and confirm the video privacy matches the audience.

How do we move Loom SSO to Atlassian Access without locking people out?

By running the two configurations in parallel for a cutover window rather than switching in one step. We add Atlassian Access as a secondary identity source, verify a sample of users can log in through it, then move the group mappings over and finally disable the Loom-native SSO. SCIM provisioning needs reconfiguration during the window so new hires do not fall into a gap.

Can we embed the Loom recorder inside our own product?

Yes, through the Record SDK. It drops a recorder into your app, handles screen and camera capture, and returns a video URL and metadata back to your code when the user is finished. There are edge cases around browser permissions, system audio capture on Safari and Linux, and hardened endpoint restrictions on corporate laptops. We build the integration with fallbacks for each so users always get something to send, even if the ideal capture mode is blocked.

Why do some of our Loom videos get stuck processing?

Usually because they exceeded the tier's max duration limit (the Free tier has a short cap) or because the Loom processing queue is busy during a traffic spike. Videos that stay in processing for more than a few hours usually need to be re-recorded on a tier that supports the length, or the sender needs to be told to split long recordings. Monitoring the webhook for the video.uploaded event helps surface problems quickly.

How do we handle Loom embeds for external customers while keeping internal videos private?

By using different privacy settings per video and a convention the team actually follows. Workspace-only videos stay internal, link-only videos are shareable to external recipients, and password-protected videos cover the middle ground for things like sensitive customer walkthroughs. We also recommend a convention for where videos live, since a 'public' folder in the workspace reduces mistakes more than individual privacy toggles.

How much does Loom help cost?

The estimate is free. Describe the symptom, the tier and whether you are mid-migration on SSO or the recorder, and we come back with a scope and a price before any engineer logs in.

Free estimate

Loom giving you trouble?

Embed troubleshooting, Atlassian Access SSO migrations, Record SDK integrations and workflow automation across the Loom surface. We work on the whole workspace rather than one video.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.