Clipchamp for Mac: editing video where there is no Mac app

A search for Clipchamp for Mac runs into the same wall every time. The product pages talk about a desktop app, the download button leads to the Microsoft Store, and the Store entry is for Windows. Nothing on the way there says clearly that the Mac route is different, so the search continues, usually through a few download portals that nobody at Microsoft has heard of. There is no Mac installer, and that is a deliberate product decision rather than an oversight. Microsoft supports the Mac through the browser, in two specific browsers, and the useful question after that is not where to download but where to put the editing window so it stops behaving like a tab.

What Microsoft ships, and for which platforms

The support documentation is unusually direct about this. On Windows 11 the personal version of the editor is already included and is launched by searching for Clipchamp in the taskbar search field. On Windows 10 it is installed as an application from the Microsoft Store. The product site's own desktop app section says the same thing from the other direction: find the video editor in the Start menu on Windows 11, or download for Windows 10 from the Microsoft Store. Both sentences describe Windows and stop there.

For everything else, the route is the browser.

Clipchamp also runs in Microsoft Edge or Google Chrome on a desktop or laptop computer by navigating to app.clipchamp.com. This works on Windows, Mac, Linux, and Chromebooks. Source: support.microsoft.com

The same page rules out one adjacent hope: the desktop editor cannot be used on mobile devices such as tablets or smartphones, so an iPad is not a substitute for the missing Mac build. A separate mobile app exists for iOS, currently requiring iOS 14 or later, and it is a different and smaller product aimed at recording and quick edits on a phone.

The work and school version follows the same pattern. It is available on laptop or desktop computers running Windows, Mac or Linux, in Edge or Chrome, through several entry points including the Microsoft 365 Apps section, the Clipchamp start page in Microsoft 365 for the web, the Microsoft 365 Create New page, and an entry in the New menu in OneDrive and SharePoint on the web. A Mac user on a work account reaches the editor the same way a Mac user on a personal account does.

Only two browsers are named, and Safari is not one of them

This is the detail that changes what a Mac owner should actually do, and it is easy to skip past. The supported browsers are Microsoft Edge and Google Chrome. Safari does not appear in that sentence, and it does not appear anywhere else on the device support page.

That has a direct consequence for the obvious first idea. macOS has had a built in way to turn a webpage into a standalone window since Sonoma, documented by Apple as Safari web apps, created with File then Add to Dock. It is free, it takes ten seconds, and for most sites it is the right answer. It is the wrong answer here, because a Safari web app is Safari. Putting an unsupported browser in a nicer window does not make it supported, and a video editor is exactly the kind of application where an unsupported engine shows up as a missing codec or a failed export rather than a polite warning.

So on a Mac the shortlist is short.

Route	Engine	Supported by Microsoft	Own window in the Dock
Chrome or Edge, normal tab	Chromium	Yes	No
Safari web app, Add to Dock	WebKit	Not named	Yes
Chromium engine wrapper	Chromium	Same engine as Chrome or Edge	Yes
Windows desktop app	Chromium	Yes, Windows only	Not on macOS

The third row is the one that fits. A wrapper that uses an installed Chromium browser as its engine is running the same rendering engine Microsoft names, in a window with no tab bar. Nothing about the browser support question changes, because the browser underneath does not change. The general scope of what that kind of tool sets up is described on the Features page.

What the free plan actually exports

Pricing confusion is the second reason this search goes badly. Older articles describe a paid Clipchamp tier with its own monthly price, and that is no longer how it is sold. The current pricing page presents two columns: a free plan, and premium features that come with a Microsoft 365 Personal or Family subscription.

Feature	Free	Premium with Microsoft 365
Export resolution	Up to 1080p HD	Up to 4K UHD
Watermark free exports	Included	Included
AI video and audio editing tools	Included	Included
Screen, camera and voice recorder	Included	Included
Stock assets, filters and effects	Free library	Premium library
Brand kit for logos, colours and fonts	Not included	Single brand
Content backup on OneDrive	Not included	Included

The point worth taking from that table is that the free plan is not a trial. Exports are unlimited, they carry no watermark, and 1080p covers most work that ends up on a social platform or in a meeting recap. The reasons to go to premium are 4K, the premium stock library, the brand kit and OneDrive backup, and none of those are about basic editing. Anyone who wants to check the current wording can do so on the pricing page at clipchamp.com, which is where those two columns are published.

The Mac matters more than the window does

Before optimising the container, it is worth reading the hardware line on the same support page. Microsoft recommends a minimum of 8 GB of RAM, states that 16 GB or higher is better, and asks for a recent Windows, Mac or Linux computer for a smooth editing experience.

That recommendation is written for a browser tab with nothing unusual around it. A timeline with several video tracks, preview rendering and an export running is one of the heaviest things a web page can be asked to do, and on an 8 GB Mac it is competing with everything else in the same browser process tree. This is the practical argument for a separate window that has nothing to do with tidiness. A dedicated window is a separate browser profile with one page in it, so the editor is not sharing memory pressure with thirty tabs, a streaming site and a chat client, and it cannot be closed by a keystroke meant for the tab next to it.

The same logic applies to long exports. An export that runs for several minutes in a tab is an export that ends the moment somebody closes the wrong window. In a window of its own, the only thing that can close it is a decision to close it.

Which window belongs to which account

Clipchamp exists in two versions that look almost identical and behave differently, and on a Mac both of them arrive through the same browser. The personal version is tied to a personal Microsoft account, and premium features come with a Microsoft 365 Personal or Family subscription. The work and school version is tied to an organisation's Microsoft 365 tenant, and it is reached through the Microsoft 365 Apps section, the Clipchamp start page in Microsoft 365 for the web, the Create New page, or the New menu in OneDrive and SharePoint on the web.

Anyone who has both, which describes most people who edit video as part of a job, hits the account switching problem within a day. Projects saved under the work account are not visible under the personal account. Stock assets and brand kit availability differ depending on which subscription is behind the session. And the browser holds one signed in Microsoft identity at a time per profile, so moving between the two means signing out, signing in, and then discovering that the other tab has also changed underneath.

This is where separate windows stop being cosmetic. Two windows with two browser profiles means two signed in sessions that never touch each other, so the work editor and the personal editor sit side by side in the Dock, each already logged in, each pointing at the right storage. Naming them after the account rather than after the product is what makes the arrangement usable a month later, since two identical icons labelled Clipchamp is a problem rather than a solution.

There is a filing consequence too. Work projects belong in the organisation's storage and personal projects do not, and the fastest way to put a video in the wrong place is to edit it in a session signed in as the wrong identity. A window per account removes the decision entirely, because the window is the decision. Anyone setting this up for the first time can check the account behaviour they should expect on the FAQ section before committing to one arrangement.

Permissions are the first thing to check

Clipchamp's recorder uses the camera, the microphone and the screen. On macOS those are per application permissions, granted to the application bundle that asks for them, which means a new window is a new application as far as the system is concerned.

So the first session in a wrapped window should be a permissions session, not a real project. Open the recorder, start a camera capture, start a microphone capture, then start a screen capture, and answer each macOS prompt as it appears. If a prompt does not appear and the capture silently produces nothing, the setting to look at is in System Settings under Privacy and Security, where Screen and System Audio Recording and Camera list applications individually. A window created by a site to app tool appears there under its own name once it has asked.

Two other behaviours are worth testing in the same session. Sign in, including a work or school account, often opens a secondary window, so popup handling needs to be permissive or set to a smart mode rather than blocked outright. And file handling runs in both directions: importing local footage and saving a finished export both go through the browser's file dialogs, so confirm that a download lands where expected before committing to a deadline. The step by step for setting a window up is in the Guide, and the list of sites commonly handled this way is on the Supported services page.

What to change first

Open app.clipchamp.com in Chrome or Edge, because those are the two browsers Microsoft names, and finish one small project in a normal tab to confirm the Mac handles it. Then move that page into a window of its own with a Kagemusha profile, and spend the first ten minutes on camera, microphone and screen permissions rather than on editing. Skip the Safari Add to Dock route for this one site, since Safari is not on the supported list.