CleanShot X on Mac: how to set it up

A capture tool is one of those apps where the defaults decide the next six months. Whatever is configured in the first half hour becomes the muscle memory, and the settings nobody touches on day one tend to stay untouched forever.

This is an order of operations rather than a tour of every preference. Permissions first, because nothing works without them. Then shortcuts, because those are what get used hundreds of times. Then what happens immediately after a capture, which is where most of the friction lives. Recording comes last, and only matters to people who record.

Check what it will run on

The published requirement is macOS 13.0 or newer.

CleanShot requires macOS 13.0 or newer. Source: cleanshot.com

Older systems are served by named older builds. The published list states that 4.8.10 was the last version supporting macOS Catalina, 4.8.4 the last for Mojave, and 4.1 the last for Sierra and High Sierra. Anyone installing on an older machine should check that list first rather than after paying.

A cloud account comes with the licence, but the app does not depend on it. That decision can wait. On first launch it is fine to skip past it and come back later once it is clear whether sharing links is part of the workflow at all.

Permissions are the first real step

Capturing the screen requires a grant from macOS. On first launch the app asks for screen recording permission, which is approved in System Settings. That grant sometimes lapses after a major macOS upgrade or after the application is replaced, so it is the first thing to check whenever captures suddenly stop working.

Recording audio requires a second, separate grant. Enabling microphone input triggers its own permission request, and the changelog contains an entry about fixing a freeze that occurred while asking for microphone permission, which is a good indication that this is a common sticking point rather than an obscure one.

There is a practical trick to handling all of this at once. macOS asks for each grant at the moment the relevant feature is first used, so exercising every feature on day one collects all the prompts into a single session. Do the audio test on the first day even if recording is not needed yet, because the alternative is a permission dialog appearing in the middle of something urgent weeks later.

Decide how this coexists with the built in shortcuts

macOS already has screenshot shortcuts. Reassigning those keys to this app or picking new ones is a decision worth making deliberately, because keeping both systems alive means learning two sets of keys and mastering neither.

Assign a small number. In practice these are the ones that earn their place:

• Capture a selected area
• Recapture the previous area
• Start and stop a recording
• All-In-One mode, which reaches every capture mode from a single key

The last one suits anyone who would rather memorise one combination than five. The changelog records additional shortcuts added for switching capture modes inside All-In-One, so a single entry point does not mean fewer options once inside it.

Assigning a dozen individual shortcuts is the failure mode. Past a handful, the combinations are not recalled reliably, and the menu gets opened instead, which is what the shortcuts were supposed to replace. Start with three, and add a fourth only after wanting it three separate times.

Configure what happens after a capture

This is the setting that produces the largest difference in daily friction, and it is the one most often left at the default.

Multiple default post capture actions can be set. Most people fall into one of three patterns: copy to the clipboard for immediate pasting, save to disk for retrieval later, or open the annotation editor because arrows and boxes get added every time. Deciding which pattern applies takes one glance at last week's captures and how they were used.

Two related settings deserve a decision at the same time. Asking for a filename after every capture makes later retrieval much easier and makes every capture slower, so it fits documentation work and gets in the way of chat conversations. The changelog also includes a preference for disabling the retina suffix in file names, which matters for anyone processing captures with scripts.

Capture sounds can be muted. For anyone who captures during meetings, turning that off on day one avoids broadcasting the shutter into a shared call.

Set a save location too. Leaving the default means captures accumulate among documents, and cleaning them out later becomes a sorting exercise. One dedicated folder makes a monthly clear out trivial.

Fit the post capture overlay to the actual screen

After each capture, a small overlay appears in a corner offering save, copy, annotate and drag to another app. Its position, size and auto close timing are all adjustable, and the first instinct of finding it annoying is usually solved by moving it rather than disabling it.

The overlay has its own interactions worth knowing: pressing space previews the capture, a swipe gesture temporarily slides it out of the way, and a recently closed item can be restored. On a multi display setup, the option to show it on the active display prevents a walk across screens to retrieve something just captured.

When this overlay is doing its job, the whole path from capturing to pasting finishes in one corner of the screen without any menus being opened.

Learn three annotation tools, not twenty

The annotation editor has a long tool list. Three of them cover nearly everything: crop, redact, and point at something.

Redaction deserves a moment of thought. The published description states that the pixelate tool applies randomization for better security, and the blur tool offers a secure option. For anything leaving the organisation, those are the right choices rather than drawing a filled rectangle over sensitive text. Crop away what can be cropped, then redact whatever is left.

For pointing, arrows come in several styles including curved ones, with adjustable weight and colour. For step by step instructions, the counter tool that places numbered marks usually communicates better than a page covered in arrows.

Try each capture mode once, on the first day

Features that are never tried are never remembered when the moment arrives. Running each mode once takes a few minutes.

• Area capture, with the crosshair and magnifier options for precise selections
• Window capture, with choices for background, transparency and shadow
• Fullscreen capture
• Scrolling capture, for pages, long conversations and code that extend past the screen
• Self timer, for capturing states that cannot exist while clicking, such as an open menu
• Freeze screen, which stops the display so a moving target can be selected

Scrolling capture and freeze screen are the two that get discovered late. Anyone stitching long pages together manually, or repeatedly closing a menu by trying to capture it, is solving a problem the app already handles.

Recording has its own list

Skip this section entirely for still captures. For recording, more decisions arrive at once:

• Output format, video or GIF for short clips
• Quality, frame rate and resolution
• Audio, microphone and system audio being separate settings
• Whether notifications are suppressed during recording
• Whether the cursor is shown and clicks are highlighted
• Whether keystrokes are displayed
• Whether a camera bubble is overlaid

Audio is the one that cannot be fixed afterwards. A recording made without the microphone enabled has to be redone. Notification suppression and keystroke display, by contrast, are cheap to toggle per recording. Settle audio and quality on day one and leave the rest to be adjusted in use.

Hiding desktop icons pairs naturally with recording, since file names on the desktop end up in anything shared. Version 5.0, released on 1 September 2026, added a video editing mode with animated zooms and trimming, along with a redesigned settings layout, which means older written guides may describe preferences that have since moved.

Know how captures are found again

Captures land in a history. The published documentation states that up to one month of capture history is stored, with filtering by type, restoring, and deleting entries. That is why a capture can be recovered even without a deliberate save, and also why anything worth keeping beyond a month belongs in a real save location rather than in history.

Text recognition is worth one test on the first day. It copies text out of images, runs on device, supports more than 30 languages, and reads QR codes. It is hard to appreciate until it replaces retyping something by hand once.

Setting up the second Mac, and the one after that

Anyone who works across two machines, or replaces a Mac every few years, benefits from writing down what was changed. Four lines are enough: the shortcuts assigned, the post capture actions chosen, the save location, and any recording defaults. Reproducing that list on a new machine takes two minutes, while reconstructing it from memory tends to produce a subtly different setup that breaks the muscle memory built on the first one.

The licence side is simpler than the settings side. Activating on a new Mac automatically deactivates the previous one, so moving to a replacement machine costs nothing and needs no request. Running two Macs at the same time is a matter of adding seats through the licence manager rather than buying a second copy.

One more thing belongs on that list: the permissions. A new machine means granting screen recording again, and microphone access again if audio is used. Those grants do not travel with a settings file or a licence key, so the day one routine repeats on every machine. Running through it deliberately, rather than discovering each missing grant during real work, is the difference between a five minute setup and a week of small interruptions.

What to change first

Work in this order: confirm the macOS version, grant screen recording permission, assign three shortcuts, choose what happens after a capture, and set a save location. If recording is part of the job, record ten seconds with audio to clear that permission too. Everything after that can be adjusted while working.

Once setup is finished, the app takes a permanent slot in the menu bar, and whether it keeps that slot is a separate decision from how it is configured. A resident app can stay running while its icon is collapsed out of the visible row, and what matters in a menu bar organizer is whether a hidden item can still be clicked without expanding everything. Permission handling after system updates is the other thing to check, which the FAQ covers, along with the supported macOS versions listed on the download page.