CleanShot X not working on Mac: what to check
A shortcut gets pressed and nothing happens. A recording starts and ends early. A capture is taken and never appears in the save folder. The menu bar icon has gone missing. The symptoms look unrelated, but the causes cluster into three places: the installed build is behind the operating system, macOS has not granted a permission, or another resident app is competing for the same key or the same device.
Working through those three in a fixed order beats poking at settings, because two of them can mask the third. Permissions that look correct do nothing on a build that predates the current macOS. A perfect build does nothing without the permission. The order below reflects that dependency.
Start with the build, not the settings
The published changelog shows how often compatibility work lands. Version 4.8.1 on July 14, 2025 fixed a crash on a macOS beta. 4.8.2 the following day fixed area screenshots. 4.8.3 on September 10, 2025 improved compatibility again. 4.8.5 on December 2, 2025 brought a redesigned interface for the new system. On July 13, 2026, 4.8.9 addressed window screenshots and the hide desktop icons feature on the next system release, and on July 21, 2026, 4.8.10 shipped a security update described as recommended for all users along with capture history performance work.
Then version 5.0 arrived on September 1, 2026, adding Studio Mode and a rebuilt settings screen. A machine that has not been updated in a year is therefore several compatibility passes behind, which is enough on its own to explain a lot of odd behaviour.
The minimum supported system is published as macOS 13.0 or newer. Older machines have a documented ceiling instead: 4.8.10 was the last build for Catalina, 4.8.4 for Mojave, and 4.1 for Sierra and High Sierra. On those machines the absence of an update is not a fault, it is the end of the support line, and no amount of permission fiddling changes it.
Permissions fail quietly, which is what makes them hard
If the build is current and nothing happens, permissions come next. macOS splits the relevant capabilities across separate switches, and each one covers a different part of the job.
| Capability | Where it lives | What breaks without it |
|---|---|---|
| Screen and system audio recording | Privacy and Security | Captures produce nothing, or recordings come out black |
| Accessibility | Privacy and Security | Global shortcuts do not fire, simulated keys do nothing |
| Microphone | Privacy and Security | Recordings have video but no voice |
| Files and folders, or Full Disk Access | Privacy and Security | Saving to certain locations silently fails |
The trap is the absence of an error. A capture that lacks screen recording permission does not throw a dialog explaining the problem. It looks like it worked and produces no file. That is why the correct move is to open the list and look at it, even with no reason to suspect anything.
The second trap is re-authorisation. Updating an app, reinstalling it, or launching it from a different location can make macOS treat it as a new binary and ask again. The name stays in the list while the grant no longer applies. When that happens, remove the entry, add it back, then quit the app fully and relaunch it. Apple documents the privacy settings panel on Apple support.
Match the symptom against the changelog
Several specific failures have already been fixed in specific builds. If the symptom matches a row below, updating is the whole answer.
Fixed a bug where hover states weren't captured when using All-In-One with the Freeze Screen option Source: cleanshot.com, read September 10, 2026
| Symptom | Fixed in | Released |
|---|---|---|
| Capture history will not open after restoring a file | 4.8.9 | July 13, 2026 |
| Hiding desktop icons stops working | 4.8.9 | July 13, 2026 |
| Window screenshots fail | 4.8.9 | July 13, 2026 |
| The name prompt after a capture does not take keyboard focus | 4.8.10 | July 21, 2026 |
| Microphone through an audio interface records only the left channel | 4.8.8 | March 23, 2026 |
| Window screenshots come out with sharp corners | 4.8.8 | March 23, 2026 |
| Emoji render incorrectly in the annotation editor | 4.8.8 | March 23, 2026 |
| Crash during screen recording | 4.8.7 | December 22, 2025 |
| Launcher extension broken, URL scheme permissions mishandled | 4.8.6 | December 4, 2025 |
| Error when converting a video that has sound | 4.8.5 | December 2, 2025 |
| Hover states missing when freezing the screen | 4.8.5 | December 2, 2025 |
The table has exactly one use: check whether the current symptom is listed. If it is, update and stop. If it is not, carry on to the sections below.
Audio problems are usually about routing
When the picture is fine and only the sound is wrong, the fault is rarely in the capture app itself. The March 23, 2026 release notes record a fix for microphone input arriving on one channel only when routed through an audio interface, which confirms that this class of problem is real and involves the path rather than the recorder.
Three checks in order. First, open the sound settings in macOS and read which input device is selected, because meeting apps frequently leave a virtual device selected after they quit. Second, check whether the recording is set to capture the microphone, the system audio, or both, since a recording meant to preserve someone else's voice needs system audio rather than the microphone. Third, make the sample rates match on the interface, because a mismatch between playback and capture destabilises the whole audio stack on macOS and shows up as dropouts and channel oddities across every app.
Testing the same recording in a different app is a fast way to place the fault. If the problem follows the device, replacing the capture tool will not fix it.
A missing menu bar icon is usually not a fault
Three explanations cover almost every case where the icon disappears.
The first is a setting inside the app that hides the menu bar item while leaving the app resident. Shortcuts still work, which is what makes it confusing. Launching the app from the Applications folder brings the settings window back.
The second is width. On a MacBook with a notch, the centre of the top edge is reserved for the camera, so bringing forward an app with a long menu pushes the right hand status icons off the visible strip. The tell is that the icon row changes as apps are switched.
The third is a menu bar manager already installed and currently collapsed. Expanding it reveals the icon.
None of these affect whether captures work. If screenshots are being taken and saved, a missing icon is a display question rather than a fault, and it does not need to be fixed urgently.
Captures that were taken but cannot be found
Files that do not appear in the expected folder are usually placed somewhere else rather than lost.
Check the save location setting first, since the export path and the save path are often separate options and only one of them may have been changed. Then look at the small overlay that appears in the corner after a capture. Its auto close behaviour is configurable, and how it is dismissed can determine whether the file is written or discarded. Finally, use the capture history, which keeps recent items and can restore them. Note the caveat from the table above: restoring from history had a bug that stopped the history reopening afterwards, fixed on July 13, 2026.
One more variable is worth eliminating during troubleshooting. If the save folder sits inside a synced cloud directory, the sync client starts working the instant a file is written, which makes the file's state in Finder harder to read. Pointing the save location at the Documents folder for the duration of the investigation removes that noise.
Duplicate login items cause repeat offenders
Settings that revert after every login, or an app that reappears after being quit, often trace back to duplicated startup registration. macOS keeps a list of login items, and the app has its own launch at login setting. Registered from both sides, two instances try to start and one gets terminated, which produces intermittent and confusing behaviour.
A related case is worth ruling out at the same time. Some Macs end up with two copies of the application itself, one in the main Applications folder and one inside a user level Applications folder or a Downloads folder, left behind by an interrupted update. Each copy registers separately, and macOS treats them as different binaries for permission purposes, so the granted permission applies to whichever copy is not the one launching. Searching for the app name in Finder and keeping a single copy resolves a surprising number of stubborn cases.
Open the login items list in the General section of System Settings and look for the same name appearing more than once. Remove the duplicate. Entries accumulate after reinstalls and after launching a copy from a different folder. This is worth checking early, because no amount of permission work changes anything when a second instance keeps winning the race.
If it still fails
Work down this list in order.
- Quit the app fully, restart the Mac, and repeat the exact action that failed.
- Check the shortcut for a collision with the built in macOS capture keys or another resident utility, since a later registration sometimes loses.
- Create a second user account and try the same action there. Working there points at settings or at another resident app in the original account.
- Move the save location to a plain local folder for the test.
- Report the symptom with both version numbers attached, through the contact page.
Including the app build and the macOS version removes one round trip from any support conversation, and a symptom that is not in the changelog is new information for the developer.
The crowded menu bar is a separate problem
Troubleshooting tends to end with a hard look at the top right of the screen. A working Mac usually carries about ten status icons once cloud storage, chat, password management, backup, meetings, input switching and capture are counted, and only two or three of them get clicked on a normal day.
A capture tool driven by keyboard shortcuts belongs in the second group, which makes hiding it sensible. Removing it entirely is worse, because the settings window becomes harder to reach exactly when troubleshooting needs it. Collapsing the row behind a menu bar manager keeps the icon reachable while freeing the space, and what matters is how a hidden item is clicked when it is needed. How it compares covers where those tools differ, and pricing shows the cost shapes.
What to change first
Check the version number before touching anything else, then open the Privacy and Security lists and read them rather than assuming. Match the symptom against the changelog table, and if it appears there, update and stop.
Once the app is working again, collapse the status icons instead of uninstalling any of them, which keeps every settings window one click away. Koffret lists the macOS versions it supports.
Frequently asked questions
A keyboard shortcut does nothing. What comes first?
Check the installed version and update it if it is behind, because permission work has no effect on a build that predates the current macOS. Then open Privacy and Security and confirm the app appears and is ticked under both screen recording and accessibility. Missing permissions fail silently rather than showing an error.
The permission is already granted but nothing works.
Remove the entry from the list, add it back, then quit the app completely and relaunch it. Updating, reinstalling or moving an app can make macOS treat it as a new binary and require a fresh grant, which leaves the old name visible in the list while the permission no longer applies.
Screen recordings only capture audio on one side.
A fix for microphone input through an audio interface arriving on the left channel only shipped in 4.8.8 on March 23, 2026, so check the version first. After that, confirm which input device macOS has selected, since meeting apps often leave a virtual device active after quitting, and make the sample rates match on the interface.
The menu bar icon has disappeared. Is the app broken?
Usually not. Either the app is set to hide its menu bar item while staying resident, or a notch equipped MacBook is pushing status icons off the visible strip when an app with a long menu is in front, or a menu bar manager is currently collapsed. Captures continue to work in all three cases.