TL;DR.

  • Atlassian retired Loom's free Creator Lite tier in February 2026 and started auto-billing viewer seats. The community is shopping for somewhere to land.
  • Clipy now ships a free, no-card migration tool that lands every Loom share link in your Clipy library as a playable MP4 you actually own — not a hot-link to Loom's CDN.
  • Three paths: a single anonymous URL at /tools/loom-downloader, signed-in 20-per-run at /migrate/loom, and a CSV upload at /switch-from-loom for whole workspaces.
  • The 20-URL cap is intentional and quiet — we'd rather you came back tomorrow than have one user pin the server. For libraries past 20, the CSV path handles up to 1,000 URLs.
  • What gets imported: the raw MP4 + the Loom-reported title. What does NOT get imported: comments, transcripts, view analytics, or anything behind Loom's auth wall.

Why this page exists

If you'd told me in late 2025 that Loom — the video tool that defined async work — would be on Trustpilot at 1.4 / 5 within twelve months, I would have asked you what you'd been drinking. And yet here we are. Atlassian rolled price increases into existing Business and Business+AI Loom subscriptions starting November 2025. In February 2026 the free Creator Lite tier was discontinued: existing free accounts were capped at 5-minute recordings and a 25-video lifetime ceiling, new free signups blocked entirely. Then viewer seats started auto-billing — every person who'd ever opened a Loom on your workspace began counting toward your paid seat ceiling.

The community noticed. Twitter has a steady undercurrent of "my Loom bill just 3xed" and "Atlassian killed the only thing about Loom I liked." Trustpilot rolled over. Our sister piece — the Switching Off Loom 7-step checklist — gets into the timeline; this post is the how: how do you actually move your existing Loom library somewhere that won't auto-bill you for the privilege?

We built Clipy to be the calm landing spot. Today's piece is a walkthrough of the migration tool we shipped specifically for that — the free, no-card, sign-in-with-Google path to bringing every Loom you care about with you.

The three paths — pick the one that fits your library

We support three flows because "migrating from Loom" means different things to different people. Some of you have one Loom you need an MP4 of right now. Some of you have a folder of 15 you want to bring along when you cancel. A few of you are sitting on a 600-video workspace and need the whole thing imported in a way that doesn't melt anyone's afternoon.

Path 1 — Single URL, anonymous, instant

If you just need this one Loom as a downloadable MP4, paste the share link into /tools/loom-downloader and you get a download in about 10–30 seconds. No signup. No card. We don't store it in your account because there is no account — that page is fully anonymous. This is the path for "I'm screen-sharing this to a teammate, just give me the file."

Some adjacent flavors live on the same path:

  • /tools/loom-to-gif — single URL → GIF. Useful for GitHub bug repros or Slack reactions where an MP4 is overkill.
  • /tools/loom-to-mp3 — single URL → MP3. People grab this when they want the audio for a podcast clip or a transcription pass elsewhere.
  • /tools/loom-video-downloader-extension — the Chrome extension version of the same flow. One click on any Loom share page and the MP4 starts downloading.

Path 2 — Up to 20 URLs, into your Clipy library

This is the path most people end up on once they realize they want to migrate, not just download. Sign in with Google at /migrate/loom, paste up to 20 Loom share links, hit Migrate. Each one gets pulled from Loom's CDN, re-packaged as a clean H.264 MP4, and uploaded under your account at /videos. Stable share links forever. No re-upload step.

The 20-URL cap is intentional. We're a free service running on a real server bill, and one user kicking off a 500-URL migration at noon would pin the worker queue for everyone else. Our quiet rule is: if you have more than 20, use the CSV path or come back tomorrow. We won't make a big deal of it — there's no upgrade prompt, no "unlock" button. We just like everything to keep working for everyone.

Path 3 — CSV upload, for the whole workspace

If you're sitting on a 200, 500, or 1,000-video Loom library, the right path is the CSV uploader on /switch-from-loom. Drop a CSV with one Loom share URL per line (a demo CSV is linked from the page so the format is unambiguous), optionally with a desired title in the second column. We process it server-side within 24 hours. You don't need to keep a tab open.

The upper bound is 1,000 URLs per submission. If you have a bigger library than that, email support@clipy.online first so we can pace it sensibly — we'd rather have a conversation about a 5,000-video workspace than have your queue eat the worker for an entire day. So far the largest migrations we've seen are around the 250-video mark.

A step-by-step walkthrough (the signed-in 20-per-run path)

Let's walk the most common path — the 20-URL signed-in migration. You're a designer who has 14 Looms scattered across the last six months of demos and reviews, and you want to centralize them somewhere that doesn't auto-bill you.

Step 1 — Export your Loom URLs

Loom's web app at loom.com/looms/videos shows your library. Open each video you want to bring across, click the share button, copy the URL. If you have a lot of videos and Loom's UI is too click-heavy, Loom's CSV export (Workspace → Settings → Export) gives you a list with the share URLs. We accept the URLs as-is from that export. Note: private and password-protected Looms won't work — see the next section on what doesn't survive.

Step 2 — Paste into /migrate/loom

Head to /migrate/loom. If you haven't signed in with Google yet, the page will walk you through that — one click, no card, the whole thing takes about three seconds. Once you're in, paste your URLs into the textarea (one per line, comma-separated, or whitespace-separated all work). The page shows you a running count of valid Loom URLs detected; if you accidentally pasted a YouTube link or an old wiki bookmark, it'll flag those as invalid before you submit.

Step 3 — Watch them land in your library

Hit Migrate. The page shows a row per URL — each one transitions from "polling" to "ready" (or "failed" in the rare unlucky case) as the worker processes them. Concurrency is 4 server-side, so a 20-URL batch typically finishes in 5–8 minutes wall-clock. As each completes, the row gets a clickable "View in library" link. When it's all done, hit "Open library" and you'll see your migrated Looms in /videos alongside any recordings you've made directly in Clipy.

Every migrated video gets the same treatment as a recording made in Clipy: a watch page at clipy.online/video/<publicId>, an embed code if you want to drop it into a Notion doc or a wiki, a download button, and a public-link toggle so you can lock individual videos to private if you need to.

What gets imported — and what does not

This is the section I want every potential migrator to read before they start. We're upfront because the next worst thing to losing a video to Atlassian's pricing changes would be migrating it and finding out we don't have something you thought you'd have.

What comes across

  • The video itself. The raw H.264 MP4 at the highest quality Loom's CDN serves publicly. We re-package it for compatibility (the file plays cleanly in every browser plus QuickTime, VLC, and any modern editor) and we don't re-encode unless we have to.
  • The Loom-reported title. Whatever title the video shows in Loom's UI is what shows up in your Clipy library. If you'd renamed it manually on Loom, that name comes along. If you'd left it as the auto-generated default, that's what you get.
  • Stable share URLs. Each migrated video gets a fresh clipy.online/video/<publicId> URL that you can drop into emails, docs, or Slack. Your old Loom share URLs keep working too (until you cancel the Loom account), so you can roll the migration over slowly without breaking anything.

What doesn't come across

  • Comments and reactions. Loom's CDN doesn't expose comment threads. If you have a video with a long comment thread you care about, screenshot it before you cancel.
  • Transcripts. Loom's transcripts are paywalled behind the API. For now we don't have an OAuth import path, which means we can't pull them. The fallback: Clipy generates a fresh transcript on every recording we host — but it does NOT auto-transcribe migrated Looms today. If you need transcripts on every imported video, email support@clipy.online and we'll wire up the workflow you need.
  • View counts and analytics. Loom's view analytics live in their database, not on the share URL. We can't see how many times a Loom was watched, who watched it, or for how long. If those numbers matter, screenshot the analytics dashboards before you cancel.
  • Private and password-protected Looms. Loom's public CDN literally won't serve these without an authenticated session. If your library is mostly private, you'll need to flip them to public on Loom first (or do an OAuth-aware import — not something we offer today).
  • Workspace metadata. Custom thumbnails, custom CTAs at the end of videos, audience settings — these all live in Loom's product, not in the MP4 itself, and don't make it across.

I'd rather you went into this knowing what you'll have than discover something missing afterwards. If a migration feels too lossy because of the above, the right move is probably to do a hybrid: download the videos to Clipy for stability, and screenshot the Loom-side metadata you can't bring across.

Common pitfalls we see (and how to dodge them)

Pitfall: private Looms quietly skipped

The most common surprise is users discovering that 4 of their 20 imports failed because those Looms were marked private. The migration UI flags this in the per-row status, but if you ran the batch and walked away, you might come back and not realize anything's wrong. Always glance at the failure column. If you need a private Loom imported, flip its sharing settings to public on Loom (just for the duration of the import) and re-run.

Pitfall: trying to do more than 20 in one go

The page caps you at 20 — anything above gets truncated. We don't make a big deal of it (no "upgrade" prompt, no "go pro"), but if you tried to paste 47 and only got 20, that's why. Either run it again tomorrow, or use the CSV path which handles up to 1,000 per submission.

Pitfall: thinking you have to keep the tab open

The 20-URL flow on /migrate/loom polls each job in your browser, so closing the tab partway through means you stop seeing the progress. But the videos still finish on the server — they'll show up in your library either way. So if you close the tab and re-open /videos after 10 minutes, all 20 should be there. The CSV path doesn't need a tab open at all — once you upload, you can close everything.

Pitfall: a failed video and not retrying

Each row in the migration UI shows its error message inline if it fails. The most common reasons: the Loom is private (see above), the Loom was deleted but the URL still exists in your bookmarks, or our worker hit a transient Loom CDN hiccup. The fix in all three cases is the same: copy the failed URL back into the page and run it again. The successful ones stay in your library; you're not re-importing the whole batch.

Workspace migrations — the tactical guide

If you're moving a team off Loom (not just your personal stash), the tactics are different. Here's what's worked for the workspaces that have used the CSV path so far:

1. Do a 10-video pilot first

Pick 10 representative videos — a mix of recent and old, short and long, private and public — and run them through the 20-URL path. This catches edge cases (a video that was uploaded with a weird codec, a video Loom is currently transcoding so the CDN isn't ready, etc.) before you commit a 500-video CSV. The pilot takes 10 minutes. The peace of mind is worth it.

2. Split your library into archive vs. active

Most workspaces have 80% "old stuff we might want to look at someday" and 20% "actively-shared current content." Migrate the active 20% first using the signed-in 20-per-run path, redirect your team to those new Clipy URLs, then drop the archive 80% as a single CSV submission. The active stuff is unblocked immediately; the archive arrives over the next 24 hours without anyone needing to wait.

3. Pre-warn the team about comments and analytics

Before you submit the CSV, send a heads-up: "FYI, we're moving Looms to Clipy. Comments and view analytics don't come across, so if anyone needs to preserve those, screenshot now." 10 minutes of warning saves you a Slack message every other day for the next month asking where the comments went.

4. Keep Loom active during the overlap period

Don't cancel Loom the moment your migration submission goes in. Keep it active for at least 2 weeks after the import completes so people can verify their important videos are present in Clipy before the original sources go away. Loom is the source of truth for the import; if a few videos failed and we didn't catch it, you want them still recoverable from Loom.

5. Redirect old Loom URLs in your internal docs

Once Clipy has the imports and the team confirms they look right, the cleanup is mostly find-and-replace across your Notion / Confluence / Slack pinned messages: loom.com/share/<id> → clipy.online/video/<publicId>. The migration UI shows the publicId for each imported video, so building a mapping table is straightforward.

The economics — why we keep this free

People reasonably ask: if you're letting people migrate 100s of MP4s into your storage, what's the catch? There has to be a catch eventually, right?

The honest answer is: we don't have a paid tier today, we don't plan to gate the migration tool, and the underlying storage cost is small enough that we don't lose sleep over it. A typical 5-minute Loom comes out around 50 MB once we've re-packaged it. A 100-video migration is about 5 GB. On Backblaze B2 (where we keep our storage) that costs roughly $0.03 per month per user. We're not subsidizing yacht ownership — it's measurably cheaper than what you'd pay for hosting your own MP4s on a generic VPS.

We do reserve the right to gently rate-limit at the worker if a single user submits 50 CSV files in a day, but that's a fairness thing, not a money thing. As of writing, no individual user has hit that yet.

What we ask in return: that you're a real person using Clipy for real work. The 20-URL signup gate is the only place we ask anything of you, and that's because the videos need an owner — they have to land in somebody's library. Without a sign-in we'd have no way to do that.

Frequently asked questions

Why is the bulk cap 20?

It's the right balance between "useful" and "doesn't pin the worker for the next user." We tested 50 and 100 in dev; 20 is the cap that consistently feels fast (5-8 minutes wall-clock) without giving any one user the ability to monopolize the queue. For libraries bigger than that, the CSV path is the right tool — it's processed asynchronously so it doesn't compete with anyone's real-time 20-URL run.

Why don't you just do a Loom OAuth import like Cap?

It's on the table but not committed for the current quarter. Loom's OAuth setup requires verification from Atlassian's developer program, which has its own latency. In the meantime, the URL-paste path covers 95% of what people actually want from a migration. If OAuth turns out to matter for a class of users we haven't seen yet, we'll prioritize it.

How long does a 100-video migration take?

Via CSV, typically 1-3 hours of wall-clock after we start processing — sometimes faster if Loom's CDN is cooperative. We aim to start processing within 24 hours of submission (usually much sooner). If we ever hit the 24-hour SLA, we'll email you to let you know it's running.

Can I migrate private team Looms?

Not via the URL path — Loom's public CDN won't serve them. The workaround for now is to flip the sharing settings to public on Loom for the duration of the import, then flip them back. If you need to migrate large numbers of private Looms, email support@clipy.online — there are a couple of workflows that work depending on your Loom plan tier.

I already use Clipy — does this affect anything for me?

No. Migrated Looms land in your library exactly the same way as recordings you make directly in Clipy. They show up alongside your existing videos, with the same watch pages, embed codes, and share controls. If you're recording new content in Clipy already, the migration just brings the old Loom content into the same place.

Should I cancel Loom right after I migrate?

We'd suggest waiting at least 2 weeks. Loom is your source-of-truth during the overlap — if a migration missed something, you want to still be able to pull it. After 2 weeks of operating on the Clipy-side URLs, you should be confident enough to cancel without losing anything.

Start the migration

If you've gotten this far, here are the three doors:

Questions about something this post didn't cover? Email support@clipy.online — we're a small team but we read every message, and migrations are one of the few things we still answer ourselves.