Clip Champ and it's many bugs

Open Clipchamp with the personal Microsoft account already connected to your projects in an updated Edge or Chrome browser, because the repeated logout/loading behavior is a documented sign-in-loop symptom and does not by itself confirm a general Clipchamp outage.^1^

Break the sign-in loop safely

1. Close every stalled Clipchamp and Microsoft sign-in tab.
2. Open the Clipchamp personal-account sign-in page.
3. Select Continue with Microsoft.
4. Choose the personal Microsoft account previously connected to your Clipchamp projects. The address may differ from the email originally used for Clipchamp; signing in with another account will not expose the existing projects.
5. If it loops again, try that same account and page in the other supported browser:
   • Edge → Chrome, or
   • Chrome → Edge.
6. Try an InPrivate Edge window or Incognito Chrome window to test a separate browser session. A failure in Chrome Incognito is not conclusive because it can restrict third-party cookies.^1^

If Clipchamp works in the separate browser or private session, the problem is likely confined to the normal browser session:

• Check whether cookie controls or an extension is blocking the Clipchamp sign-in flow.
• Test one suspected extension at a time, preferably by creating a site-specific exception rather than disabling protections globally.
• Only if that fails, remove cookies and site data for the affected Clipchamp site, then reopen the personal-account sign-in page.

Caution: deleting site data can sign you out and may remove cached media or unsaved changes. Ensure uploads and saving have completed and retain the original media files. Do not clear data across all Microsoft domains.^1^

If this happens only in the Windows app

Use Clipchamp in Edge or Chrome as the immediate workaround. If the browser works but the app does not, that distinguishes an app-specific failure from an account-wide sign-in problem.

On a managed work or school network, the desktop app can also reject connections when a proxy or SSL-inspection device presents a certificate that cannot pass revocation validation. That condition must be corrected by the IT/network team; Microsoft does not support bypassing the certificate check.^2^

Report it without entering Clipchamp

Since the loop prevents the in-product report from being completed, use Microsoft support and select Can’t sign in if necessary. Microsoft explicitly provides this route when Clipchamp’s support chat is unavailable or the user cannot sign in.^3^

Include:

• Whether the failure occurs in the Windows app, a browser, or both.
• Browser/app version.
• Personal versus work/school account.
• Exact error text or code, if any.
• Date, time, and time zone of the failure.
• Whether another supported browser or private session worked.
• A screenshot of the loading screen, with account details obscured.

Do not send passwords, verification codes, or email sign-in links.

Microsoft documents repeated sign-in prompts and redirect loops, but the available official information does not establish why Clipchamp has “so many bugs” or confirm that this particular incident is service-wide. The browser/app comparison above is the quickest way to distinguish a damaged local session from an account or service-side problem.

References

1. Troubleshoot signing in to Clipchamp | Microsoft Support
2. Work and school account support in the Clipchamp app for Windows | Microsoft Support
3. How to get in touch with Clipchamp support | Microsoft Support