Loom Video Downloader

Why Loom's own download button is greyed out for you

Loom is a workplace tool, so the recording you want is usually yours, made on company time, in an account you may not fully control. That changes what this page owes you.

Loom does have a download button in the video's options menu, and it produces a clean MP4. It is also switched off for a large share of the people who record on Loom, in three ways that feel identical from the outside.

The free plan. On Loom's Starter plan, downloading is not included. Not throttled, not watermarked: absent. Atlassian's documentation puts download rights on Business and Business+ AI for admins and creators, and on Enterprise for admins and members. On the free tier your own recording is watchable, shareable, and not saveable. That policy is why this search exists at 500 a month.

Your role in the account. Even on a paid team, seats are not equal. Creator Lite and Viewer roles carry no download permission on any plan. Someone added to watch and comment cannot save a copy, and a viewer not signed in to Loom cannot either, whatever the owner switched on. People read the greyed-out button as a bug. It is a seat type.

An admin turned it off for everyone. On Enterprise and Business+ AI, an admin can disable downloads across the whole account in one setting. It covers videos and transcripts, applies to every member, and has no per-video override for the person who made the recording. That is where a third-party tool is the wrong answer.

If the button is missing because of a plan tier or a seat type, using a link-paste tool on your own recording is reasonable. If it is missing because your employer's admin switched downloads off deliberately, that is a data policy, and routing around it is a decision about your job rather than about software. We will not pretend those two are the same.

Most people land in the first situation: a five-minute walkthrough recorded on a free account, needed in a deck or a help article, and the product will not hand over the file.

The owner is not notified when a recording is fetched through a link. Loom shows view counts and viewer names to owners on paid plans, so the play can register as a view. There is no download alert and nothing naming the tool you used.

How Loom stores a recording, and why an early download looks blurry

Loom uploads while you record, then transcodes afterwards. The share page goes live before that work finishes, which produces the most reported problem with saving Looms: you press stop, send yourself the link, download immediately, and the file is soft.

That file is not broken. In the first minutes after a recording, the only rendition that exists may be a low one, because the higher one is still encoding. Come back after the transcode finishes and the same link serves a sharp file. Long recordings take longer. If you saved something blurry minutes after recording, wait and fetch the link again.

We check for this. If the ladder only has a low rung when you paste the link, we say the recording is still processing instead of handing you a bad file.

The video is served from a CDN behind signed URLs that expire. Those signatures are short-lived and tied to the request that made them, which is why a media URL pulled from a browser's network tab works for a while and then errors. Paste the share link instead.

Loom links come in several shapes and all point at the same asset. loom.com/share/<id> is standard, loom.com/embed/<id> sits inside an iframe in a doc or a help centre, and teams on paid plans can serve recordings from their own subdomain, so a link that never says loom.com can still be a Loom. The long hexadecimal string is the recording, and everything before it is packaging.

The downloaded MP4 is the raw recording. Chapters, calls to action, captions, and filler-word or silence removal are player features on the share page. They do not travel into the file. If you edited out the "ums" in Loom, the file still has them.

Archiving your Looms before the account changes

The most common legitimate reason to bulk-save Loom recordings is that access is about to end. Two versions show up.

The first is leaving a job. Your walkthroughs live in a company account, and on your last day it is deprovisioned along with everything in it. If any of it is yours to keep, get it out before the offboarding ticket closes. Ask first, in writing, then save.

The second is a plan change. Loom's free tier caps recordings at five minutes and the library at 25 videos, including archived ones, and at that ceiling you cannot record anything new until you clear space. Teams that downgrade land with a library that is visible and frozen. Get the files out before you delete.

This tool takes one link at a time. There is no library sweep, because doing that means asking for your Loom credentials — the same limit applies to screen recordings from a browser tab like Vimeo Record. For hundreds of recordings, ask your admin for a workspace export.

If you need the words too, copy the transcript from the share page before you go. Transcripts and captions live on Loom's side and are not baked into the MP4.

What to do with a 20-minute walkthrough once you have it

The recordings worth saving are the long ones: the onboarding walkthrough, the architecture tour, the bug repro that turned into an explanation. Nobody watches them twice.

Unsora's AI clipping cuts it into short, captioned clips, one per topic. The onboarding tour becomes eight clips attached to eight help-centre articles. All of it is callable over MCP from the AI tools you already use, from $19/mo with a 3-day free trial.

Next steps

Published the walkthrough on YouTube? save your YouTube upload.

Recording runs long? turn the walkthrough into short clips.

Want a polished version? generate an explainer video.