Loom recording downloader

One address shape, three levels of access

Loom is used for work recordings: a walkthrough of a spreadsheet, a bug report with the screen and a voice over it, a handover left for a colleague. Every recording gets an address built from the host name, the word share, and a long string of characters.

Those addresses are indistinguishable by eye. The characters carry no hint about who is allowed to watch, because access is a setting stored against the recording rather than something written into the link. Two addresses of identical shape can behave completely differently here, and the reason is always the setting the owner chose.

Open to anyone holding the link

The widest setting lets any visitor watch without signing in. Support articles, public product demos and recordings attached to a job application are usually set this way, because the person receiving them has no account on the sender's workspace.

These are the recordings that return rows here. Analyze reads the page the way a signed-out browser does, finds the published media, and reports each file with its height and its size in megabytes. Choose the row that suits you and press Download file on it.

Limited to the people in a workspace

A recording restricted to a workspace serves video only to a signed-in member of that workspace. Everything else gets a page asking for a sign-in.

Vidzilla reads every page signed out and belongs to no workspace, so it receives the sign-in page and reports an empty list. Your own membership makes no difference to that, because the request comes from our servers rather than from your browser session. If you need the file and you are a member, the download control inside Loom itself is the route, and it is available when the owner has left downloads enabled.

Held behind a password

Loom owners can put a password in front of a recording, which is common when a walkthrough contains customer data or unreleased work. The page loads and asks for the password before it will serve anything.

There is nowhere to supply that password here, so the results list is empty. This is the same class of answer as the workspace case: the page served a gate, and the gate is what got reported. Holding the password yourself does not change the request our servers make.

Long recordings that stay surprisingly light

A screen recording is mostly still. A spreadsheet sits unchanged for twenty seconds while somebody talks, then a cell changes, then a menu opens. Very few pixels move between one frame and the next, and video compression stores change rather than storing every frame in full.

The practical effect is that a twenty-minute Loom often weighs less than a three-minute clip of handheld footage. The size figure on each row is the real number, so read it rather than estimating from the runtime. Free use refuses any single file over 150 MB, and a great many work recordings of real length come in under that even at the top row.

Settings the owner can change after sending the link

Access is not fixed at the moment of sharing. An owner can narrow a public recording to their workspace, add a password later, or delete the recording entirely, and the address stays the same through all of it.

That is why an address a colleague sent last month returns nothing today while it worked when they sent it. Nothing changed on your side. Ask the owner whether the recording is still shared, and treat an empty list as a question for them rather than a problem with the address you pasted.

What free use covers, and whose recording it is

Free use covers 3 downloads a day with the count returning to three at midnight UTC, and the 150 MB ceiling applies to each single file. Pro removes the count, removes the ceiling and removes the advertising. Keep the tab open until the transfer finishes, and start it soon after the list appears, because a prepared file expires on a short timer.

A work recording usually contains somebody else's screen, voice and often their employer's information. The saved copy lives on your device, and what you are permitted to do with it comes from the person who recorded it and the organisation they made it for.

Related pages

• Business video hosted for a sales team
• Recordings embedded on a company page
• Restricted files shared from a Drive account
• Cloud share links that expire or get revoked
• A share page sitting in front of a stored video