How to Download Loom Videos in 2026 (MP4)

Loom is the default choice for async video communication in remote teams: quick screen recordings, product walkthroughs, client updates. You record once, share a link, done. The problem arrives when you need that video offline: for a client who lost access to Loom, for archiving a departing teammate's recordings, or simply for editing in your own workflow. Loom's native download button is gated behind certain paid plans, removed from older recordings, and missing entirely from many share pages.

This guide covers every practical method for how to download Loom videos in 2026, from the manual DevTools path to the automated one-click route. The fastest option by far is Vidora, whose v2.1 ships a dedicated Loom resolver that works locally, without touching any external proxy or scraping API.

1. Why Loom downloads are tricky

On the surface, downloading a Loom video sounds straightforward: it is just an MP4 sitting on a CDN somewhere. The complication is in how Loom surfaces that MP4 URL.

The official download button is disappearing

Loom has progressively restricted its native "Download" button across plan tiers. As of 2026, the button is either hidden or disabled on many Free accounts, and workspace admins on Business plans can disable downloads at the organization level. Even when the button is visible, it is only available to the video owner, not to viewers accessing a share link.

Viewer-facing share pages at loom.com/share/{id} almost never show a download button, regardless of plan. You are expected to watch in the browser player only.

The MP4 URL is buried in JavaScript-rendered HTML

Loom's share pages are server-side rendered with a large JSON blob embedded inside a <script id="__NEXT_DATA__"> tag. This JSON blob contains the video metadata, including the CDN URL for the raw MP4 stream. But this JSON is nested several levels deep, mixed with dozens of other properties, and the CDN URL contains a signed token that expires in minutes to hours.

Generic download tools that try to scrape Loom's HTML without parsing this structure come back empty. Tools that use an external proxy or a third-party scraping service expose your Loom share URL to a server you do not control, which is a privacy risk for recordings that contain sensitive information. Our free M3U8 Detector tool handles HLS streams well, but Loom's MP4 delivery is handled differently: the URL must be parsed from the page JSON, not captured from a live network request.

The two methods below both solve this correctly, just with different tradeoffs between speed and technical effort.

2. Method 1: Browser DevTools (manual, one-off downloads)

This method works on any Chromium-based browser (Chrome, Edge, Brave, Vivaldi) and Firefox. It requires no extension and no account. The tradeoff: it takes three to five minutes per video and the captured URL expires quickly, so you need to download immediately.

If you are new to using the Network tab, our DevTools M3U8 deep-dive walks through the interface in detail with screenshots and common gotchas. The Loom workflow is similar but targets an MP4 URL instead of an HLS manifest.

Step-by-step: capture the Loom MP4 URL

1. Open the Loom share page. Navigate to loom.com/share/{id}. Do NOT press play yet.
2. Open DevTools before playback. Press F12 on Windows/Linux or Cmd + Opt + I on Mac. Switch to the Network tab. In the filter bar, type cdn.loom.com to narrow results to CDN traffic only.
3. Press play on the video. The Loom player fetches the stream. Within one to two seconds, a request to a cdn.loom.com URL containing video or ending in .mp4 appears in the filtered list. That is your target.
4. Copy and download the URL. Right-click the request and choose Copy > Copy link address. Paste it into a new browser tab: the video streams directly. To save to disk, use curl -L -o loom-video.mp4 'PASTED_URL' in your terminal, or open the URL in a tab and use the browser's built-in video save menu (right-click on the video element, Save video as).

Why the CDN URL works without authentication

Once Loom's server has decided you are allowed to view the share page (public URL, or you have the password), it renders the signed CDN URL directly into the page HTML. That CDN URL is self-authenticating: the signature is baked in. Anyone who has the URL can download the file, until the signature expires. This is the same model as pre-signed S3 URLs.

3. Method 2: Vidora (one-click, batch, no DevTools)

Vidora v2.1 ships a dedicated Loom resolver that handles the entire extraction automatically. You open a Loom share page, click the Vidora toolbar icon, and get a download button. No DevTools, no copy-paste, no race against a token expiry clock.

How the Loom resolver works internally

Vidora's resolver fetches the public loom.com/share/{id} page HTML directly from your browser, then parses the embedded __NEXT_DATA__ JSON locally to extract the MP4 CDN URL. Every step happens in your browser, in your session, on your machine. There is no external proxy, no API key, no scraping server, no third party that ever sees your Loom share URL.

This local-first architecture matters if you are handling recordings that contain internal meetings, client calls, or product demos with unreleased features. Your share URL never leaves your machine.

Step-by-step with Vidora

1. Install Vidora from the Chrome Web Store (works on Edge, Brave, and any Chromium browser). It is a one-time payment of $9.99 with lifetime use.
2. Open the Loom share page. Navigate to loom.com/share/{id} in any tab.
3. Click the Vidora icon in your browser toolbar. The popup shows the detected Loom video with the title, duration, and a Download button.
4. Click Download. Vidora resolves the current MP4 URL on the fly and saves the file directly to your Downloads folder as a clean MP4. No re-encoding, original quality preserved.

For batch downloads, open each Loom share page in a separate tab and trigger the download from each one sequentially. Vidora queues them and processes them in order without competing for bandwidth.

Vidora vs. generic video downloaders

Most browser extensions that claim to download Loom videos are built as generic "video detector" tools. They watch the Network tab for any video request and surface the URL. This works on simple MP4 progressive downloads, but Loom's share pages often load the video metadata via a JavaScript data blob rather than a direct network request, so generic detectors miss it entirely or capture a low-quality preview segment instead of the full video.

The Loom resolver in Vidora specifically parses Loom's __NEXT_DATA__ structure, which gives it the correct full-quality MP4 URL every time. If you are comparing options, our comparison with Video DownloadHelper and the full alternatives overview show exactly where generic tools succeed and where they fail on Loom.

4. Edge cases: password-protected, team-only, and embedded Loom videos

Password-protected Loom videos

When a Loom video has a password set by the creator, the share page shows a password prompt before rendering any video metadata. Both the DevTools method and Vidora require you to enter the password first. Once the video player loads in your browser, the signed CDN URL is present in the page and both methods work normally. The password gate protects access to the page, not the CDN URL itself.

Team-only (workspace-restricted) videos

Workspace-restricted Loom videos only load if you are logged into a Loom account that is a member of the creator's workspace. If you see a "Sign in to view" or "This video is only available to workspace members" screen, no tool can download the video for you. Authentication cannot be bypassed. If you are a workspace member and the video plays in your browser, Vidora's resolver works identically to the public share page case.

Embedded Loom videos on third-party pages

Loom videos embedded on external sites (product documentation, course platforms, company wikis) use an iframe that loads the Loom player from loom.com/embed/{id}. The Vidora resolver targets share pages, not embed pages. The fix is simple: replace /embed/ with /share/ in the URL, open that tab, and then run Vidora on it. The ID stays the same; only the URL segment changes.

For course platforms that embed Loom recordings as part of a learning management system, the same logic applies. Once you have the underlying Loom share URL, the download works the same way as any other Loom video. If you regularly save video courses for offline use, our guide on how to save online courses offline covers the broader workflow across multiple platforms.

5. Legal and ethical considerations

Downloading video from the internet sits in a nuanced legal space. Here is a factual, neutral breakdown specific to Loom.

Your own recordings

Downloading your own Loom recordings is unconditionally fine. You own the content. Loom's terms of service confirm that you retain all rights to your recordings. The download button being hidden on some plans is a commercial UI decision, not a legal restriction.

Someone else's recording: the three questions

When the video belongs to someone else, three questions determine where you stand:

• Do you have legitimate access? If the share page requires authentication, a password, or workspace membership, and you have that, you are authorized to view the content. Downloading for personal offline use of content you are authorized to view is generally covered by fair use or private copy doctrines in most jurisdictions (US, EU, UK).
• Are you redistributing it? Sharing, re-uploading, or publishing someone else's Loom recording without permission is a copyright and potentially a confidentiality issue. Downloaders, including Vidora, are for personal archiving, not for redistribution.
• Does the platform use DRM? Loom does not use Widevine, FairPlay, or PlayReady DRM. The stream is an unencrypted MP4 delivered over a signed CDN URL. Vidora and the DevTools method both work at the transport layer, not by circumventing encryption. Vidora does not bypass DRM on any platform.

If you are downloading a recording of an internal meeting, a client call, or a session with business-sensitive content, make sure you have the right to retain that recording under your employment agreement or client contract. The tool is not the relevant legal instrument here; your permission to hold the data is.

For a broader comparison of Vidora's approach versus other tools on the market, see the Video DownloadHelper comparison and the Vimeo download guide, which covers the same ethical framework for a similar platform. You can also compare all available options in our Vidora alternatives overview.

6. Frequently asked questions