QUICK ANSWER
To move a Loom library to Clipy, install the free Clipy Chrome extension, open your Loom library and press Import library. It copies every video you own, private ones included, keeps folder names, and changes nothing on Loom. Your first five single imports are free; moving two or more in one run needs Clipy Pro.
Moving a Loom library to Clipy now takes one pass from your Loom library page, private videos included. This guide covers the three ways in, what comes across and what does not, what it costs, and how to run a team migration without losing anything.
Updated October 2026. An earlier version of this post said private Looms could not be migrated and that bulk migration was free. Both have changed, and this version reflects how it works today.
TL;DR
- Fastest route: install the free Clipy Chrome extension, open your Loom library, and press Import library. It brings every video you own, private ones included, keeps your folder names, and changes nothing on Loom.
- Other routes: paste share links on the import page, or upload a CSV of public links on the Loom migration page.
- What arrives: each video gets its own Clipy watch page and share link, plus Loom's own transcript and an AI summary where Loom has a transcript it can serve.
- Cost: your first five single-video imports are included with a Clipy account. Moving two or more videos in one run is part of Clipy Pro, $6 a month billed yearly or $9 month to month.
- Only need files? The Loom downloader saves public links as MP4, up to 10 per run, with no account. For private ones, see how to download a private Loom video.
Why are people moving their Loom libraries?
Mostly because of plan limits that are now written down. Loom's pricing page limits Starter screen recordings to five minutes each and 25 videos per person. Atlassian's download guide says Starter admins and creators cannot download their videos, and Creator Lite users cannot download on any plan. Atlassian's billing guidance also says Creator Lite users convert to paid Creator status after a grace period unless an admin deactivates them.
Put together, a lot of people are sitting on a library they cannot easily download and do not want to keep paying for. If you are weighing the timing, our switching-off-Loom checklist covers the order of operations, and what happens to your Loom videos when you downgrade covers the deadline.
Which route fits your library?
Three questions settle it.
- Are any of the videos private? Use Import library, Import selected or Add to workspace from the Loom page. They are the only routes that can read private videos, because they work through your own Loom login.
- Do you already have a list of share links? If they are public, paste them on the import page or upload them as a CSV. If some are private, the import page offers to fetch those through the extension.
- Do you only need files, not a library? Then this is a download, not a migration. The Loom downloader saves public links as MP4s with no account, and the extension saves private ones one at a time.
Most people moving their own library want the first route. It is also the only one that keeps folder names.
The three ways to move a Loom library into Clipy
Route 1: Import library, from Loom itself (recommended)
This is the route for most people, and the only one that handles private videos in bulk. The Clipy Chrome extension adds Clipy buttons to loom.com. Because it runs in your own browser, it can read every video your Loom account can open, without Clipy ever seeing your Loom password.
- Install the Clipy Chrome extension and sign in to Clipy with Google.
- Open your Loom library at loom.com in the same Chrome profile, signed in to Loom.
- Press Import library to take everything, or tick the videos you want (Clipy's ticks or Loom's own checkboxes both work) and press Import selected.
- Confirm. Before anything runs, it tells you what it will take: every video you own, private ones included, with your folder names kept and nothing on Loom changed.
- A Clipy tab opens and shows progress. Each recording appears in your Clipy library as it finishes.
For one video, open it on Loom and use Save to Clipy, then Add to workspace.
A run handles up to 1,000 videos. If your library is bigger, the status under the button says how many are queued for the next run; press it again. Videos you already imported are skipped, so re-running never creates duplicates.
Route 2: Paste share links on the import page
If you already have a list of Loom links, sign in and paste them on the import page. Clipy pulls each recording server-side, so you can close the tab and the videos still land. Public links go straight through. If some links turn out to be private, the page offers to fetch them through the Chrome extension instead of just failing them.
Route 3: Upload a CSV for a large public library
The Loom migration page takes a CSV of Loom share links, one per line, up to 1,000 per submission. It runs as an assisted import and we aim to finish standard submissions within 24 hours. This route works without your Loom login, so it can only reach public links. If your library is mostly private, use Route 1.
For a library past 1,000 videos, contact us and we will plan the run with you.
How does Import library work?
It helps to know what happens when you press the button, because "import my private videos" can sound like something that gets around Loom's permissions. It does not.
- The extension reads your Loom library page in your own browser tab, the same page you are looking at.
- For each video you picked, it asks Loom, as you, for the media address Loom's own player uses. This request runs with your existing Loom login, so it sees exactly what you can see.
- It sends those addresses to your Clipy account in small batches, with each video's ID, title and folder name. Your Loom password and cookies never leave your browser.
- Clipy's servers fetch each video from that address, store their own copy, and add it to your library. A hand-off that is not used expires after about an hour.
Because the lookup uses your login, a video you cannot open on Loom cannot be imported, and nothing about a video changes on Loom. A run handles up to 1,000 videos, and videos already in your Clipy library are skipped, so you can run it again as often as you need.
What comes across, and what does not
Read this before you cancel anything. It is better to know now than to find a gap after Loom is gone.
What comes across
- The video. Clipy stores its own copy, so it keeps playing after you cancel Loom.
- The title as it appears in Loom.
- Folder names, when you use Import library from the Loom page.
- Loom's transcript wherever Loom has one, plus an AI summary written from it.
- A Clipy watch page and share link for every video, with an embed code, a Download button, and sharing controls you set per video.
What does not come across
- Comments and reactions. Screenshot any thread you need before you cancel.
- View counts and analytics. Export or screenshot them on Loom first.
- Loom-only extras such as custom thumbnails, end-of-video calls to action and audience settings.
- Videos you cannot open on Loom. The extension works through your own Loom login, so it sees exactly what you see. Deleted videos cannot be recovered by any route.
How do you check that the migration is complete?
Before you rely on Clipy, and long before you cancel Loom, confirm that everything arrived.
- Compare the counts. Note how many videos your Loom library shows, then count what arrived in your Clipy library. If the numbers differ, run Import library again; it fetches what is missing and skips the rest.
- Spot-check a sample. Open a handful of videos across different ages and lengths. Check that each plays to the end, that the title is right, and that the transcript is there for videos that had one on Loom.
- Test sharing. Send one share link to a teammate, or open it in a private window, to check it works for the people who will use it.
- Check private videos specifically. If a private video is missing, open it on Loom in the same Chrome profile. If it plays there, use Save to Clipy, then Add to workspace on that video alone.
What happens to your old Loom links?
Nothing, at first. Importing a video into Clipy does not touch it on Loom, so its Loom link keeps working for as long as the video and the Loom account exist. When you delete the video or close the account, that link stops working. Loom will not redirect it to Clipy.
So the real work after a migration is updating the places that point at Loom: wiki pages, onboarding docs, pinned Slack messages, support macros, README files. Every imported video has its own clipy.online/video/... link, and it keeps its Loom title, so you can find the matching recording in your Clipy library by name. Start with the documents people open most, and do this during the overlap period while the old links still work.
What does migrating cost?
Plainly, so there is no surprise halfway through a library:
- Trying it: every signed-in account gets five single-video imports included. Use them to see what a migrated recording looks like before you commit.
- Moving a library: importing two or more videos in one run, including Import library and CSV uploads, is part of Clipy Pro, $6 a month billed yearly or $9 month to month. After that, Loom imports are unlimited.
- Just downloading: saving public Looms as MP4 with the Loom downloader needs no plan and no account. Saving a private video you can open needs a Clipy account and the extension.
What can you do with the videos once they are in Clipy?
An imported video behaves like any recording made in Clipy:
- Share it with its own watch page and link, and choose per video whether it is private or viewable by anyone with the link.
- Embed it in docs and wikis, or download the MP4 whenever you need a file.
- Search it. Library search covers titles and, for videos that arrived with a transcript, what was said in them.
- Hand it to a coding agent. Claude Code, Codex and Cursor can read a recording's transcript and summary through Clipy's MCP server or CLI, the same way they read a recording made in Clipy.
New recordings you make in Clipy land in the same library, so the old Loom videos and the new ones live side by side.
Moving a team off Loom
A team migration is less about the tool and more about not losing anything people rely on. What works:
Who should run the import?
Import library brings across the videos you own. On a team, that means each person runs it for their own videos, or the Loom videos of someone who has left need their own plan. If you can open a teammate's video on Loom, you can bring that single video into your own library with Save to Clipy, then Add to workspace. It cannot pull a whole library that belongs to someone else. Settle who imports what before anyone's Loom account is closed, because a closed account takes its videos with it.
1. Run a small pilot first
Pick ten representative videos, a mix of old and new, short and long, private and public, and import them with Save to Clipy or a small Import selected run. Check that they play, that titles and transcripts look right, and that the share links work for the people who need them.
2. Move active videos first, archive second
Most libraries are a small set of videos people still link to and a long tail nobody opens. Move the active set first, update the links people use, then bring the archive across in one run.
3. Tell the team where the videos live
A short heads-up saves a month of questions: share the new Clipy links so everyone knows where each video now lives.
4. Keep Loom running during the overlap
Do not cancel Loom the day the import finishes. Give it at least two weeks so people can check their important videos are in Clipy while the originals still exist.
5. Replace old Loom links in your docs
Old loom.com/share/... links in Notion, Confluence and pinned Slack messages stop working when the Loom account goes. Each imported video has its own clipy.online/video/... link to swap in.
What does a realistic two-week move look like?
For a solo library, the whole move is an afternoon. For a team, spreading it over two weeks keeps the risk low and gives people time to notice anything missing. A plan that works:
- Day 1: pilot. Import ten representative videos, check them as described above, and confirm the share links work for the people who need them.
- Day 2: active videos. Import the recordings people still link to and watch, and tell the team where they now live.
- Days 3 to 5: links. Replace Loom links in the most-used docs, wikis and pinned messages with the Clipy links.
- Day 5: the archive. Run Import library for everything else. It skips what already arrived, so there is no harm in running it across the whole library.
- Week 2: overlap. Keep Loom running. Ask the team to report anything missing, compare counts once more, and re-run Import library if anything is short.
- Day 14 or later: cancel. Only once the counts match and the main docs point at Clipy.
Before you cancel, save anything that does not come across: comment threads you care about, and any view numbers you want for reporting.
Common pitfalls
Signed in to the wrong Loom account
If you have both a personal and a work Loom login, the extension reads whichever one Chrome is signed in to. Check the account in the corner of loom.com before you press Import library.
Using the CSV route for a private library
The CSV route only reaches public links, so private videos in a CSV will fail. Use Import library from the Loom page for those.
A run that says some videos could not be read
Run Import library again; it picks up the rest and skips what already arrived. If the same videos keep missing, open one on Loom. If it plays, try Save to Clipy, then Add to workspace on that video alone.
Cancelling Loom before the overlap ends
The most expensive mistake is the easiest to make: the import finishes, the library looks full, and the Loom subscription gets cancelled that afternoon. If a handful of videos failed, or a teammate's videos were never imported because only you ran the import, there is no source left to fetch them from. Keep Loom running for two weeks, compare counts at the end, and cancel only when they match. A couple of weeks of overlap costs far less than recording a lost onboarding video again.
Frequently asked questions
Can I migrate private Loom videos?
Yes. Use Import library, Import selected or Save to Clipy from loom.com with the Clipy Chrome extension. It reads private videos through your own Loom login and changes nothing on Loom. The CSV route cannot reach private videos.
Is migrating from Loom to Clipy free?
Your first five single-video imports are included with a Clipy account. Moving two or more videos in one run is part of Clipy Pro. Downloading public Looms as MP4 is free with no account.
Do my Loom folders come across?
Yes, folder names are kept when you use Import library from the Loom page.
Do transcripts come across?
Loom's own transcript comes across when Loom has one for the video and can serve it, and Clipy writes an AI summary from it.
Does migrating change or delete anything on Loom?
No. Import library reads your videos and copies them into Clipy. Nothing on Loom is changed, moved or deleted, and your Loom links keep working until you remove the videos or close the account.
Can I migrate videos that someone else owns?
Import library only takes videos you own. If you can open a teammate's video on Loom, you can bring that one video into your library with Save to Clipy, then Add to workspace.
Will my old Loom links redirect to Clipy?
No. Loom controls its own links, so they keep pointing at Loom. Replace them in your docs with each video's Clipy link during the overlap period.
How long does it take?
Videos appear in your library one by one as they finish, so you can start using them before the whole run is done. CSV submissions are assisted, and we aim to finish standard ones within 24 hours.
Should I cancel Loom right after migrating?
Wait at least two weeks. Keep Loom as the source of truth until your team has checked the videos they care about in Clipy.
Start the migration
- Whole library, private videos included: get the Clipy Chrome extension and press Import library on loom.com.
- A list of links: the import page.
- A large public library as a CSV: the Loom migration page.
- Just the MP4 files: the Loom downloader.
Something this post did not cover? Get in touch. Migrations are one of the things we still answer ourselves.