Can't log in to Loom since the Atlassian move
Login loops, a support form that asks for a workspace URL you cannot see, and an account that is now an Atlassian one. The fix a user reported that worked, and how to tell which login you need.
If Loom sends you in circles when you try to sign in, you have run into the move to Atlassian. It is common enough to have its own thread, and there is a fix that a user reported working.
What the move changed
Loom says you are now in Atlassian if you signed up after February 2026, or if your older account has been integrated. Your account settings page says "Your Profile is linked to Atlassian" when that is true.
The practical effect is that signing in goes through Atlassian's single sign-on, and settings, users and billing for the workspace moved to Atlassian Administration. A poster on r/atlassian put it this way.
They described being redirected all over the place, a support centre that mixes Atlassian and Loom articles, and a contact form that asks for a workspace URL they could not find because they could not log in.
The fix that worked for one person
A commenter in that thread described the cause as stale session data left over from single sign-on across several domains, and gave steps. The poster who got stuck replied that it helped them out of the loop. The steps, in the commenter's words condensed:
- Open
atlassian.comorid.atlassian.com. - Open your browser's developer tools and go to the Application tab (in Chrome).
- Under Storage, expand Local storage, select each domain and clear it. Do the same for Session storage.
- Expand Cookies and clear them for each domain.
- Close the browser, reopen it and try Loom again.
The commenter warned that this may sign you out of other sites that use cookies, and said they had not found a way around it. It is one person's workaround and not an official fix. Try it, and do not count on it.
Finding the workspace URL
Loom's contact form asks for a workspace URL, and the poster could not give one because they could not sign in. I could not find Loom's own guidance on where to read it from. A teammate who can still sign in can read it from their address bar and send it to you.
If you also need to cancel
Cancellation moved too, and it is where the login problem turns into a billing one. Only Atlassian billing admins and organisation admins can cancel an Atlassian-managed Loom subscription, so someone has to be able to get in. The steps are in how to cancel Loom.
If the reason you are logging in is an invoice, why your Loom bill went up explains what to change. If it is a lost recording, Loom crashed and lost your recording lists what can be recovered. And if the recordings themselves are the problem, why a Loom recording is not the quality you set is next.
For the alternatives, see the best Loom alternatives for Mac.
A recorder with one sign-in at most
Prequel does not need an account to record, edit or export. Signing in is for sharing and for the licence, and it opens your browser with no separate signup: see share links. A recording is a folder in ~/Movies/Prequel whether or not you are signed in.
Record with nothing between you and the file.
Prequel needs an Apple Silicon Mac on macOS 14 or later. Download Prequel for Mac and try it free for 7 days, with no watermark on anything you export. After that it is $9 a month or $29 once. See what it costs.
Frequently asked questions
- Why does Loom keep redirecting me when I try to log in?
- Since the move to Atlassian, Loom signs in through Atlassian's single sign-on, and stale session data on atlassian.com can send the page round in a loop. A user on r/atlassian said clearing local storage, session storage and cookies for atlassian.com and id.atlassian.com got them out of it.
- Is my Loom account an Atlassian account now?
- Loom says you are in Atlassian if you signed up after February 2026, or if your older account has been integrated. Your Loom account settings page says "Your Profile is linked to Atlassian" if so.
- Why does Loom support ask for a workspace URL?
- Its contact form asks for one. People who cannot log in do not know theirs, which a user on r/atlassian named as a problem that did not exist before Atlassian. A teammate who can still sign in can read it from their address bar.
- Who can cancel a Loom subscription after the move?
- Only Atlassian billing admins and organisation admins can cancel an Atlassian-managed Loom subscription, according to Loom's documentation.
Keep reading
- Why your Loom bill went up, and how to leaveLoom's billing moved to Atlassian and free Creator Lite seats became paid ones. What changed, what people report paying, the step that stops the charge before the next invoice, and what to use if you are leaving.
- How to cancel Loom, including after the Atlassian moveLoom now has two cancellation routes: Atlassian Administration and Loom's own settings. How to tell which you are on, the clicks for each, what you lose, and why downgrading does not stop the charge. Checked 5 October 2026.
- Loom crashed and lost your recording: what you can get backLoom's own help pages say what can be recovered. Desktop recordings sometimes, Chrome extension and mobile recordings never. The page to try first, the folder to check on a Mac, and how to lower the risk.
- Why your Loom recording isn't the quality you setUsers report Loom recordings that go fuzzy after pausing, a 1080p setting that does not hold, and a webcam that lags only on an external camera. What they saw, and how to record at the full size of your screen instead.