Disclosure: I make Hindsight, one of the replacements below. The free options come first, and every competitor fact here comes from that project’s own page or README.

What is actually happening to RetroClip

Three things are true at once.

• It is abandoned. The Mac App Store listing still shows 1.0.6 from April 2020, a minimum of macOS 10.12, and release notes that end with “RetroClip is now totally free to use!” Nothing has shipped since.
• It is Intel-only. Rosetta Check, a community tracker of Intel apps, lists RetroClip 1.0.6 as Intel-only and says it has found no Apple silicon build anywhere. That fits the dates: the app froze before Apple silicon existed.
• Rosetta has an end date. Apple’s developer notice from September 1, 2026 calls macOS 27 the “final release to support Rosetta,” and its support article on Intel-based apps says that from macOS 28, Rosetta will remain only for certain older, unmaintained games. A screen recorder is not one of those games.

That is also why you may have seen a pop-up saying RetroClip “will not work with a future version of macOS.” Since macOS 26.4, Apple shows that warning whenever you launch an app that needs Rosetta. It is not a bug in RetroClip; it is the countdown.

One more practical snag: MacRumors reported that upgrading to macOS 27 Golden Gate removes Rosetta if you had it installed on Tahoe. If RetroClip suddenly will not launch after that upgrade, macOS will offer to reinstall Rosetta, and it will work again — for one more release cycle.

The complaints a replacement should fix

We read all 41 RetroClip reviews across six App Store storefronts while building Hindsight. People loved it — reviewers called it “the best and only Mac clipper” — but the same complaints kept coming back:

• No system audio (about nine reviews). People installed loopback drivers like BlackHole or Soundflower just to hear the game in their clips.
• Broken on newer Macs (about five): won’t launch, hangs, or a “failed to create pipeline state” error.
• Buffer length (about five): five minutes was the ceiling, and some people wanted short presets so they could skip trimming.
• Lag in games (about four).
• A 25 Mbps bitrate cap that looked soft on big and ultrawide monitors (two reviews, one on a 5120×1440 display).
• No way to pick a display on multi-monitor setups (two).

Most of these come from age. RetroClip predates ScreenCaptureKit, the capture framework Apple added in macOS 12.3, which is what gives modern apps system audio, per-window capture, and low-overhead frames out of the box. Any app built on it fixes the audio and display complaints almost for free. The performance side is explained in does screen recording slow down gaming on a Mac.

What replaces it

Same order as our 2026 Mac clipper roundup: free first, then paid.

1. Steam Game Recording — free, built into Steam, and it keeps a background buffer of Steam-launched games. If your library is mostly Steam, turn it on and you may be done. It cannot see games Steam did not launch.
2. OBS Replay Buffer — free and works for any window, with system audio. It needs setup each time: enable the buffer, bind Save Replay, start it each session, and use Apple VideoToolbox instead of x264. Walkthrough: OBS Replay Buffer on a Mac.
3. ReplayMac / ReplayCap — the closest in spirit to RetroClip’s “always on, one key” feel. Its README lists a 15–300 second buffer, system audio and mic, hardware encoding, and a universal build; free on GitHub or a one-time purchase on the App Store. Needs macOS 15.
4. Vestige and ClipForge — free, open-source menu-bar clippers for macOS 14 and later. Vestige does window-only capture with presets up to 10 minutes but ships an unnotarized DMG; ClipForge offers 15 seconds to 2 minutes with display or window capture.
5. Hindsight — the one I make. It holds one game window in a rolling buffer of 15 seconds to 5 minutes (the same ceiling RetroClip had), records that window’s audio without your Discord call, lets you pick 8 to 50 Mbps, and saves an MP4 when you press ⌥⇧C. macOS 14 or later, $19.99/year after a 14-day free trial on the Mac App Store. It is not a one-time purchase, and it does not stream.

RetroClip complaints, one by one

Switching without losing anything

1. Move your old clips first. Copy RetroClip’s saved clips folder somewhere you keep, before you delete the app.
2. Quit RetroClip and remove it from login items. Two always-on recorders mean two encoders running during every match.
3. Clean up the permission list. In System Settings → Privacy & Security → Screen & System Audio Recording, remove RetroClip and grant the new app. More on that panel, and why it re-asks about once a month, in Mac screen recording permission.
4. Drop the loopback driver if you only had it for RetroClip. The new app records system audio directly. Keep it if Discord or a DAW depends on it.
5. Save a test clip in a real game, fullscreen, with sound, before the next night you care about.

If you are torn between clipping a window or the whole screen, window vs display capture covers the trade-off.

FAQ

Does RetroClip still work in 2026?

Usually, yes, through Rosetta on Apple silicon. It has had no update since April 2020, and Apple says Intel-only apps stop running after macOS 27, so it will not survive macOS 28.

Is RetroClip discontinued?

Nobody has announced it, but in practice yes. The App Store version is still 1.0.6 from April 2020, and it has no Apple silicon build.

What is the best free RetroClip alternative?

Steam Game Recording if your games launch through Steam; otherwise OBS Replay Buffer. For RetroClip’s menu-bar, one-key feel for free, try ReplayMac on macOS 15 or Vestige on macOS 14.

Why does my Mac warn that RetroClip will stop working?

Since macOS 26.4, macOS warns whenever you open an app that needs Rosetta. RetroClip is Intel-only, so it triggers the warning on every Apple silicon Mac.

Why ShadowPlay never comes to Mac

NVIDIA’s own system requirements for ShadowPlay / Instant Replay point at GeForce GPUs that expose a dedicated video encode accelerator (NVENC). Modern Macs use Apple silicon GPUs (or older Intel + AMD configurations). None of them are GeForce cards, and Apple does not sell an NVIDIA option. The encode path ShadowPlay depends on is simply not present.

That is different from “NVIDIA abandoned the port.” There was never a local ShadowPlay product for macOS to abandon. GeForce Experience and the NVIDIA App are Windows (and Linux, for some pieces) tooling for NVIDIA hardware. Searching “ShadowPlay Mac” often mixes in two red herrings: cloud gaming pages for Shadow PC, and an unrelated game titled Shadowplay. Neither is Instant Replay on your Mac’s GPU.

One honest exception people bump into: GeForce NOW. NVIDIA’s cloud service documents Record and Instant Replay for Ultimate members inside the stream overlay (Ctrl+G), including on the macOS GeForce NOW app, with resolution caps. That is clipping a cloud session on a remote GeForce machine — not installing ShadowPlay against a local Mac game running under Metal, CrossOver, or GPTK. If your library is not on GeForce NOW, it does not help.

What “ShadowPlay-like” actually means

Instant-replay tools do not press Record when you hit the hotkey. They capture and hardware-encode continuously into a fixed-length memory ring, then remux the trailing window to an .mp4 on save — the mechanic covered in how to record the last 30 seconds on a Mac. On Windows, ShadowPlay is the brand name for that pattern with NVENC. On a Mac, the same pattern uses ScreenCaptureKit plus VideoToolbox on Apple’s media engine. Different APIs; same muscle memory.

The honest Mac ladder

Start free, climb only if the gaps matter. This is the same ladder we use elsewhere on the blog — not a funnel that skips the free options.

1. Steam Game Recording — free background recording for many Steam-launched titles. It will not see Battle.net, many CrossOver/GPTK sessions, or emulator windows Steam did not start. If your library is mostly Steam, try this first.
2. OBS Replay Buffer — free, works for any game once you enable the buffer, assign Save Replay, start it each session, and switch the encoder to Apple VideoToolbox instead of x264. It is still a broadcast console, not a one-key menu-bar clipper. Setup and limits: OBS Replay Buffer on a Mac.
3. A dedicated Mac rolling-buffer app — the category ShadowPlay occupies on Windows: stay armed, save after the moment, keep clips local. Soft pitch: Hindsight is built for that job on macOS 14+, captures one window, and is $19.99/year after a 14-day free trial on the Mac App Store. For a dated free-and-paid roundup, see best Mac gameplay clipping apps in 2026.

Side-by-side: ShadowPlay vs the Mac options

Prefer a clean game window over the whole desktop when you clip — menu bar and notifications stay out of the file. That choice is covered in window vs display capture. If Discord is leaking into the track, recording game audio without Discord explains the window-audio path. Performance anxiety (“will a buffer kill my FPS?”) is answered in does screen recording slow down Mac gaming.

AMD ReLive and Xbox Game Bar on Mac?

Same hardware story, different logos. AMD ReLive / AMD Software recording features target AMD Radeon GPUs on Windows (and AMD’s own driver stack). They are not a macOS product for Apple silicon. If you left a Windows desktop that used ReLive, the Mac replacements are the same ladder above — Steam, OBS, or a native rolling-buffer app — not an AMD Mac port.

Xbox Game Bar (Win+G / Win+Alt+G style capture on Windows) is part of Windows. There is no Xbox Game Bar for macOS. The “record the last 30 seconds” intent maps to OBS Replay Buffer or a Mac instant-replay app, not to a Microsoft overlay on Apple hardware. Built-in macOS Screenshot (Shift-Command-5) and QuickTime only start recording after you press Record — they do not hold a rolling buffer.

FAQ

Is there a ShadowPlay for Mac in 2026?

No native ShadowPlay or NVIDIA App Instant Replay for local Mac gaming. NVIDIA’s encode stack expects GeForce NVENC, which Macs do not have. Use Steam Game Recording, OBS Replay Buffer, or a Mac rolling-buffer app instead.

Does NVIDIA Instant Replay work on a MacBook?

Not against games running on the Mac itself. GeForce NOW Ultimate can expose Record / Instant Replay inside a cloud stream on the macOS GeForce NOW app, which is a different product from local ShadowPlay.

What is the closest free ShadowPlay alternative on Mac?

Steam Game Recording if the game launches through Steam; otherwise OBS Replay Buffer with Apple VideoToolbox. Both are free. Paid menu-bar apps exist when you want less setup — compare them in the 2026 Mac clipper roundup.

Is Hindsight a ShadowPlay equivalent?

It targets the same job — rolling buffer, hotkey after the moment, local files — using macOS APIs rather than NVENC. It is not affiliated with NVIDIA. Pricing is $19.99 per year after a 14-day free trial; clips stay on your Mac.

Disclosure up front: I make Hindsight: Instant Replay (often shortened to Hindsight), a paid native macOS clipper. This roundup still puts the free tools first, names honest limits on every option including mine, and only states competitor facts that appear on that project’s own site or README today.

How we picked

The job is gameplay clipping: save a short highlight after it happened, not stream a multi-hour session. That filters out generic screen-recorder listicles that only cover prospective capture. Each entry below had to (1) run on macOS in 2026, (2) offer a rolling replay buffer or an equivalent “save the last N seconds” path, and (3) publish price, system requirements, and feature claims on an official page we could open today. EaseUS-style aggregator posts are out of scope — they rarely verify Mac-native instant replay. Built-in Screenshot and QuickTime stay out of the table for the same reason: they do not go backwards.

Quick comparison

Sources for every row are linked in the sections below. If a detail was not on the official page today, it is not in the table.

Free options first

1. Steam Game Recording

If the title launches through Steam, start here. Valve’s Game Recording FAQ describes a background mode that keeps a temporary recording while you play so you can make a permanent clip afterwards. It is free and already sitting inside the Steam client on Mac.

Best for: people whose library is mostly Steam and who are happy inside Steam’s overlay and clip library.
Limits: Steam only knows games it launched. App Store titles, Battle.net, CrossOver, GPTK sessions, browser games, and emulators are outside that path. Step-by-step context is in how to record the last 30 seconds on a Mac.

2. OBS Studio Replay Buffer

OBS Studio is free and open source. Its Replay Buffer is a real retroactive recorder once you enable it under Settings → Output, set a maximum replay time, bind Save Replay, and start the buffer each session. On a Mac, prefer an Apple VideoToolbox hardware encoder over x264 when the format allows it — OBS documents VideoToolbox in its hardware-encoding guide, and the --startreplaybuffer launch option can arm the buffer automatically.

Best for: streamers and anyone who already keeps a scene graph.
Limits: it is a broadcast console, not a menu-bar clipper. Isolating one app’s audio from Discord is not native on macOS — most people add a virtual device. Full Mac setup notes live in OBS Replay Buffer on a Mac.

3. ReplayMac (App Store: ReplayCap)

ReplayMac on GitHub is a macOS menu-bar instant-replay clipper. The README states a continuous buffer of the last 15–300 seconds of screen and audio, hardware HEVC/H.264 via VideoToolbox, system audio plus microphone options, a clip library, and dual-display support. GitHub releases are free; the same app is sold on the Mac App Store as ReplayCap as a one-time purchase. Requirements listed today: macOS 15+, Apple silicon or Intel (universal from 1.6.9).

Best for: people who want a free or one-time menu-bar clipper with a long feature list and are already on Sequoia.
Limits: macOS 15 floor rules out Sonoma machines; the GitHub edition updates manually from Releases.

4. Vestige

Vestige describes itself as a free, open-source ShadowPlay/Medal-style menu-bar recorder for macOS. The README lists window-only capture, automatic game detection, replay presets from 30 seconds to 10 minutes, hardware HEVC or H.264, system audio and mic toggles, a local clip library, and no accounts, cloud, or telemetry. Requirement: macOS 14 Sonoma or later, with Apple silicon recommended. A DMG is offered; the project notes that build is unnotarized, so Gatekeeper will warn unless you build from source.

Best for: free local clips on Sonoma+ without a cloud account.
Limits: you must accept the unnotarized DMG warning or compile yourself; it is a smaller project than OBS or Steam.

5. ClipForge

ClipForge is a lightweight MIT-licensed Swift/SwiftUI clipper. The README lists a rolling buffer of 15s / 30s / 60s / 90s / 2m, hotkey save to MP4, optional manual session recording, display or window capture, system audio via ScreenCaptureKit, optional mic, a local clip library, trim, menu-bar controls, and “Ghost mode.” Requirements: macOS 14+, Apple silicon or Intel. Releases are published on GitHub.

Best for: a minimal free hotkey workflow.
Limits: early-stage open source — confirm the latest Release works on your Mac before you depend on it for a tournament night.

6. Rewinder

Rewinder is a native rolling-replay recorder. Its README lists buffer lengths of 15 / 30 / 60 / 90 / 120 seconds, a configurable save hotkey (default Ctrl+Option+R), system audio plus mic, menu-bar residence, and a free Developer ID–signed notarized DMG. Requirements today are strict: Apple silicon only and macOS 26 (Tahoe).

Best for: Apple silicon Macs already on Tahoe that want a free notarized install.
Limits: Intel Macs and anything below macOS 26 are out by the project’s own requirements list.

Paid options

7. ClipMac

ClipMac markets itself as native Mac gameplay clipping with an instant replay buffer, Metal-accelerated capture, game audio, in-app trimming, and cloud sharing. The site states macOS 15.0 (Sequoia) or later, support for Apple silicon and Intel, free cloud uploads, and optional paid plans that start at about $5.99/month for extra storage and higher recording limits. A 7-day free trial is mentioned on their clipping-software pages. Their compare page lists instant replay up to two minutes.

Best for: Mac gamers who want cloud upload and sharing baked in and are on Sequoia.
Limits: Sequoia floor; the clear price you pay depends on which storage/limit plan you pick. Feature-by-feature notes versus Hindsight live on Hindsight vs ClipMac.

8. Hindsight: Instant Replay

Hindsight: Instant Replay is the app this site is about — a native macOS menu-bar instant-replay tool from Eunoia Software LLC. It keeps a rolling buffer of one game window, and a hotkey saves the last 15 seconds to 5 minutes as an MP4. Capture is window-scoped with per-app audio (so Discord can stay out of the file), everything stays on your Mac, and there is no account. Requirements: macOS 14+. Price: $19.99 USD per year after a 14-day free trial — it is not a one-time purchase. Mac App Store: Hindsight: Instant Replay.

Best for: people who want a small always-armed clipper for any window (Steam, App Store, CrossOver, GPTK, emulators) without a cloud tier.
Limits (honest): paid annual subscription; the product is still new; it buffers one window at a time, not two monitors as separate streams; it does not replace OBS for streaming or multi-source production.

Which should you install tonight?

• Steam-only library: turn on Steam Game Recording and stop reading.
• You already stream in OBS: enable Replay Buffer with VideoToolbox — see the OBS Mac guide.
• You want free and local on Sonoma: try Vestige or ClipForge; on Sequoia, ReplayMac’s GitHub build is the feature-heavy free option.
• You are on Apple silicon + macOS 26: Rewinder’s notarized DMG is the simplest free install path among the GitHub apps.
• You want cloud sharing on Sequoia: ClipMac.
• You want a clear yearly price, macOS 14, one-window local clips: Hindsight: Instant Replay.

For the wider menu that also covers Screenshot and QuickTime (prospective recorders, not clippers), see how to clip gameplay on a Mac. Prefer a game window over the whole display when you can — window vs display capture explains why.

FAQ

Is there a ShadowPlay for Mac?

Not from NVIDIA — ShadowPlay is tied to GeForce Experience on Windows. On a Mac the same job is done by a rolling replay buffer: Steam Game Recording for Steam titles, OBS Replay Buffer, or a dedicated menu-bar clipper such as ReplayMac, Vestige, ClipForge, Rewinder, ClipMac, or Hindsight: Instant Replay.

What is the best Medal alternative on Mac?

Medal does not ship a supported macOS recorder (details and sources). Closest Mac-shaped substitutes are the free buffer tools above plus ClipMac and Hindsight: Instant Replay. None of them recreate Medal’s full social/cloud network; they recreate the “save what just happened” part.

How do I record the last 30 seconds on a Mac?

Use a tool that was already buffering: Steam background recording, OBS Replay Buffer set to 30 seconds, or a dedicated rolling-buffer app with a 30-second preset. Built-in Screenshot and QuickTime cannot save footage from before you pressed Record — full walkthrough.

What is the best free Mac gameplay clipper?

There is no single winner. Steam is best when every game is on Steam. OBS is best if you will configure a scene. Among dedicated free apps, ReplayMac, Vestige, ClipForge, and Rewinder are the ones with public READMEs we could verify today — pick by your macOS version (14 vs 15 vs 26) and whether you need notarization.

Does ClipMac work on macOS Sonoma?

ClipMac’s site requires macOS 15.0 Sequoia or later. On Sonoma, look at Vestige, ClipForge, OBS, Steam (for Steam games), or Hindsight: Instant Replay (macOS 14+).

Is Hindsight: Instant Replay a one-time purchase?

No. Current pricing is $19.99 per year after a 14-day free trial, sold on the Mac App Store. Clips stay local; there is no required cloud account.

Why hardware encode usually does not steal frames

Instant-replay tools never “start recording” when you hit the hotkey. They capture frames continuously, hardware-encode each one immediately (H.264/HEVC via the media engine), keep the encoded samples in a memory ring, and on save remux the trailing window into an .mp4 without re-encoding. That pipeline is documented in our last-30-seconds guide and measured in a proof-of-concept on Apple silicon.

The important performance claim is mechanical, not marketing: media-engine encode is described in that research as a few percent of one core with no GPU render impact. Compression work leaves the game’s Metal/render path alone. Capture still costs something — ScreenCaptureKit has to deliver frames — but the classic “recording melted my FPS” story on Mac is almost always an encoder or thermal story, not the ring buffer itself.

Real PoC numbers (not vendor marketing)

From a reproducible Apple silicon proof-of-concept on macOS (documented in the project research notes), not from a competitor’s landing page:

• Window capture at 960×664@60fps, 10 Mbps H.264: a 30s ring held in about 33 MB of RAM. Saving the trailing 8s produced an 8.86s clip (~10.7 MB) written in well under a second.
• Display capture at 2560×1654 with a 10s ring run for 25s: the buffer stayed between 10.1–11.9s (eviction snapped to ~2s keyframe boundaries) at roughly 12 MB steady memory.

Encoded-video ring memory scales with bitrate and duration roughly like this (PCM audio adds about 23 MB per minute on top):

Those figures are why a short clip buffer is cheap in RAM and why writing continuously to disk is a different product class. A ring that only flushes on hotkey avoids the sustained SSD write heat and wear of a full session recorder.

When recording does slow the game down

Hardware encode is the happy path. Recording still hurts when you leave it:

• Software encoding / x264 in OBS. x264 runs on the same CPU cores the game wants. Forum threads about “Replay Buffer high CPU” on Mac are usually this. Switch the recording/replay path to an Apple VT hardware encoder — the Mac-specific setup is in OBS Replay Buffer on a Mac.
• Intel Macs without the same media-engine story. VideoToolbox still helps for recording on many Intel Macs, but you do not get Apple silicon’s dedicated media engine the same way. Expect a thinner performance margin, especially alongside a second encode for streaming.
• High-bitrate display capture + thermals on thin Airs. Capturing the whole desktop at native Retina resolution multiplies encode work. Prefer a single game window when you can — see window vs display capture. Sustained heat on a MacBook Air can throttle the whole machine even when the encoder itself is “hardware.”
• Writing continuously to disk vs a RAM ring. A full session recorder that streams to an .mov for an hour is a different load than a fixed-length memory buffer that only touches disk on save. Disk I/O and thermals show up in the first model; they barely appear in the second until you hit Save.

If a vendor publishes a CPU percentage for their own app, treat it as their claim unless you measured both tools the same way. Do not mix self-reported marketing numbers into a head-to-head.

An honest ladder of Mac options

• Built-in Screenshot toolbar / QuickTime. Fine for start-from-now recordings. Neither saves the last N seconds after a play — they only begin after you press Record.
• OBS with Apple VideoToolbox. Free rolling buffer once you enable Replay Buffer, assign Save Replay, start it each session, and leave x264 behind. Still a broadcast console.
• Steam Game Recording. Free background recording for many Steam-launched titles; outside Steam (Battle.net, CrossOver, GPTK, emulators) it will not see the game.
• Rolling-buffer apps like Hindsight. Stay armed on one window, keep an encoded ring in memory, save after the moment. Soft pitch only: Hindsight is built on that media-engine + ScreenCaptureKit path — the same mechanic NVIDIA ShadowPlay-style tools use on Windows, adapted to macOS APIs. For the broader menu, see how to clip gameplay on a Mac.

Practical settings that stay out of the game’s way

1. Use a hardware encoder (Apple VT H.264 or HEVC), not x264, for any always-on buffer.
2. Capture the game window when you only need gameplay — smaller frames, cleaner clips, less accidental desktop chrome.
3. Keep buffer length honest (30–60s is enough for most highlights); long high-bitrate rings are RAM, not free.
4. On a thin Air, lower bitrate or resolution before you blame the whole category of “screen recording.”
5. If you stream and clip at once, avoid a second concurrent software encode — OBS’s “use stream encoder” option exists for a reason.

FAQ

Does screen recording always drop FPS on a Mac?

No. With hardware encoding on the media engine, a well-built rolling buffer is designed not to sit on the game’s CPU/GPU render path. FPS drops are common when you software-encode, capture more pixels than you need, or thermally load a thin laptop.

Is OBS bad for Mac gaming performance?

OBS is fine once Replay Buffer uses Apple VideoToolbox. It feels bad when left on x264 or when a second encode runs for streaming. Setup details live in the OBS Replay Buffer Mac guide.

How much RAM does a clip buffer use?

It depends on bitrate and length. The PoC held a 30s 10 Mbps window-capture ring in ~33 MB, and a 10s high-resolution display ring around ~12 MB steady. The 8/12/20 Mbps table above scales that intuition for longer buffers.

Does a RAM ring wear out the SSD?

The ring itself does not write continuously. Disk activity happens when you save a clip (or if you choose a full session recorder that writes the whole time). That is one reason rolling buffers feel lighter than hour-long captures.

What Medal actually supports in 2026

Medal’s platform guide is explicit about where the product runs. Supported platforms are the web site, Windows 10/11 desktop, Android, and iOS. Under unsupported platforms they list Mac, Linux, and Chromebooks. For Mac they write that Medal is not currently supported on macOS — all versions — and that there are no desktop or mobile apps for Apple laptops or desktops. Mac users are pointed at the web version, which they describe as limited.

The dedicated Mac download article goes further: they no longer support Medal for Mac download. If you still have an old Mac build installed, they cannot guarantee it will run cleanly and will not troubleshoot it. They also warn against installing the iOS Medal app from the Mac App Store on Apple silicon — it may appear installable, but they do not support that path and recommend avoiding it.

So “does Medal work on a Mac?” is really two questions. Can you clip gameplay with a Medal recorder on macOS? No — there is no supported Mac recorder. Can you still open medal.tv in a browser on a Mac? Yes, with the limits below.

Still on Medal? How to upload from a Mac

Plenty of people keep a Medal account for friends, clips, and the social feed even after they move their gaming PC workflow. If that is you, Medal documents two practical routes that still work from a Mac desk.

AirDrop a clip to your iPhone, then upload in the iOS app

This is the workaround Medal themselves suggest in the Mac download article: capture or export the clip on the Mac, AirDrop the file to an iPhone, and upload with the Medal iOS app. Steps that match how AirDrop usually behaves:

1. On the Mac, put the finished .mp4 (or whatever container you exported) somewhere Finder can see — Desktop is fine.
2. Right-click → Share → AirDrop, or open AirDrop in a Finder window, and send to your iPhone. Both devices need Wi‑Fi and Bluetooth on, and you need to be signed into iCloud or set AirDrop to receive from Everyone for 10 minutes if the phone does not appear.
3. On the iPhone, save the file to Files or Photos if the share sheet offers that, then open the Medal app and use its upload flow to publish.

You are using Medal as a sharing destination, not as the Mac capture stack. That is the honest shape of the workflow their support page describes.

Use medal.tv in a browser — knowing what it cannot do

Medal’s platform guide says you can open medal.tv in a modern browser on a Mac. The web experience is for watching clips and managing your profile. They are clear about the gaps: you get the general feed and clips you have already published; you cannot view unlisted, cloud-synced, or expiring clips in that web surface; and you cannot record or edit clips in the browser. Treat the site as a viewer and account hub, not a Mac clipper.

If someone tells you to “just download Medal on Mac from the App Store,” that is the unsupported iOS-on-Mac install Medal warns against. Prefer AirDrop + iOS upload, or stay on the web viewer, instead of leaning on an install they will not support.

What to use on a Mac when you want Medal-style clips

Medal’s Windows product is an instant-replay clipper: a rolling buffer of recent gameplay and a hotkey that writes a file after the moment. macOS has no built-in equivalent of that buffer — recording the last 30 seconds needs a third-party or Steam path. The practical ladder on a Mac looks like this:

• Steam Game Recording — free, already armed for many Steam titles. It only knows games Steam launched, so Battle.net, CrossOver, GPTK, and emulator sessions are out. Start here if your library is mostly Steam.
• OBS Replay Buffer — free, works once you enable the buffer, assign Save Replay, start it each session, and switch the encoder to Apple VideoToolbox. It is a broadcast console, not a menu-bar clipper; the Mac-specific setup and limits are in OBS Replay Buffer on a Mac.
• A dedicated Mac rolling-buffer app — the category NVIDIA ShadowPlay and Medal occupy on Windows. On macOS that means a native tool that stays armed and saves one window after the fact. Soft pitch: Hindsight is built for that job; the feature trade-offs versus Medal live on Hindsight vs Medal, not in this answer post.

A dated roundup of free and paid Mac clippers (Steam, OBS, ReplayMac, Vestige, ClipForge, Rewinder, ClipMac, Hindsight: Instant Replay) is in best Mac gameplay clipping apps in 2026.

For the broader menu — Screenshot toolbar, QuickTime, OBS, Steam, and instant replay — see how to clip gameplay on a Mac. When you do capture, prefer a game window over the whole display so the menu bar and notifications stay out of the file; that choice is covered in window vs display capture. If Discord is leaking into the clip, recording game audio without Discord explains the ScreenCaptureKit window-audio path.

FAQ

Is Medal available on Mac?

No. Medal’s platform support guide states that Medal is not currently supported on macOS and that there are no desktop or mobile apps for Apple laptops or desktops. The supported clipper lives on Windows; mobile social and upload tools live on iOS and Android.

What is Medal.tv macOS support status?

Unsupported. Their Mac download article says they no longer support Medal for Mac download, will not troubleshoot leftover Mac installs, and advise against installing the App Store iOS app on a Mac. The supported Mac-facing surface is the limited web experience at medal.tv.

Can I still upload clips to Medal from a Mac?

Yes, indirectly. AirDrop the file to an iPhone and upload with the Medal iOS app — the path Medal documents — or use the web site only for viewing and profile work after clips already exist on your account. The web UI does not replace a Mac recorder.

Will Medal bring Mac support back?

Their current docs do not announce a return date. They acknowledge interest in a macOS version and still list Mac as unsupported. Plan around the tools that exist on your Mac today rather than waiting on an unpublished client.

What you need before the buffer does anything

Install the current OBS Studio build from obsproject.com, not an old Homebrew cask if you can help it. Grant Screen & System Audio Recording when macOS asks — without that permission the preview stays black. OBS’s Quick Start Guide is clear that on macOS you add a macOS Screen Capture source (display or window). There is no Windows-style Game Capture on Mac.

Add one scene, one macOS Screen Capture source pointed at the game window you care about, and leave the rest of the scene empty until the buffer works. A complicated layout is not required for clipping.

Turn on Replay Buffer with Mac-friendly encoder settings

1. Open Settings → Output and set Output Mode to Advanced.
2. Open the Replay Buffer tab (or enable Replay Buffer under Output if your build still groups it there). Turn it on and set Maximum Replay Time — 30 to 60 seconds is a sensible clip length; multi-minute buffers chew RAM for little gain when you only want a highlight.
3. Under Hotkeys, assign Save Replay to a key you can hit inside a fullscreen game. Optionally assign Start Replay Buffer if you do not want to click the Controls dock every session.
4. On the Recording side of Advanced output, set the encoder to an Apple VT hardware encoder — Apple VT H264 Hardware Encoder is the safe default; HEVC is fine when you want smaller files and your players can decode it. OBS’s hardware-encoding guide documents VideoToolbox on Apple silicon and Intel Macs. On Intel Macs, VT is for recording; streaming still needs x264 because those Macs lack the constant-bitrate path most services expect.
5. If you also stream, set Replay Buffer (and recording, when you want the same trade-off) to Use stream encoder when that option is available. A second concurrent encode is a common reason Mac users report high CPU while the buffer sits idle in the tray.

Then click Start Replay Buffer before you play. The buffer does not arm itself. If you keep forgetting, OBS documents a --startreplaybuffer launch flag; on macOS the usual pattern is an Automator app or Terminal line of the form open -a "OBS" --args --startreplaybuffer.

Why the Mac feels laggy until you leave x264

Forum threads titled “Replay Buffer high CPU” and “OBS makes my game lag” are usually encoding stories, not mysterious Replay Buffer bugs. OBS’s bundled software encoder is x264. It runs on the CPU cores your game also wants. Apple VideoToolbox moves compression onto the media engine, which is the specialised silicon Macs already use for screen recording and export. Switching the recording/replay path to Apple VT is the single highest-leverage change for Mac gaming clips inside OBS.

Keep canvas resolution honest. Capturing at 4K when you only share 1080p clips multiplies encode work for no audience benefit. Match the game’s output, or downscale once in Video settings, then test a Save Replay once before a real session.

What OBS still cannot do cleanly on macOS

Be honest about the limits, because they are why people abandon a working buffer after a week:

• Per-app audio is not native. macOS mixes application sound before it reaches the speakers. A recorder reading that mix cannot separate the game from Discord by itself. OBS users solve this with a virtual audio device such as BlackHole or Loopback and careful routing — workable, but it is a second product to install and keep healthy. Window capture with ScreenCaptureKit can isolate one app’s audio without that stack; that path is covered in how to record game audio without Discord.
• It is a broadcast console, not a menu-bar clipper. Scenes, sources, profiles, and the Controls dock are the product. That is correct if you stream. It is overhead if you only want one shortcut that stays armed.
• You must start the buffer every session unless you automate launch flags. A buffer that was never started cannot save the play you just made.
• Window vs display still matters. A display capture includes the menu bar and notifications. Prefer a window-targeted macOS Screen Capture source for clean gameplay clips — same decision as window vs display capture.

When OBS Replay Buffer is the right answer

Keep OBS when you already live in it: you stream, you need multiple sources, you want free software, or you are fine arming a buffer from the Controls dock. For Steam-only titles, also consider Steam Game Recording before building an OBS scene — Valve’s background recording is free and closer to “already armed” for games launched through Steam. The broader menu of Mac options is in how to clip gameplay on a Mac and how to record the last 30 seconds.

If the job is only “save what just happened in this game window,” a dedicated rolling-buffer app is the smaller interface. Hindsight holds a fixed-length encoded buffer of one window, can take that game’s audio without Discord, and saves an MP4 after the moment. Our Hindsight vs OBS page spells out the trade without pretending OBS is a bad tool — it is the wrong weight class for some jobs and the right one for others. Free GitHub clippers and other paid Mac options are collected in best Mac gameplay clipping apps in 2026.

A 60-second smoke test

1. Start Replay Buffer. Confirm the Controls dock shows it running.
2. Move something distinctive in the game for ten seconds.
3. Hit Save Replay. Open the file OBS wrote and confirm picture, length, and audio.
4. If the clip is silent, fix audio devices before chasing encoder settings.
5. If the game stuttered while the buffer ran, re-check that the encoder is Apple VT and that you are not running a second encode for recording at the same time.

Once that smoke test passes, OBS Replay Buffer on a Mac is a reliable free clipper. Most of the horror stories are defaults and audio routing, not a missing feature.

What display capture actually grabs

A display capture records a monitor: every pixel that monitor is showing, including chrome that is not part of the game. Apple's Screenshot and QuickTime screen recording still centres on Record Entire Screen or a selected portion of the desktop. On macOS Tahoe 26 or later the toolbar also offers Record Selected Window, which is a welcome addition — but many guides, and many third-party tools, still default to the full display because that is the historically simple path.

Display capture is honest about what it is. If Discord is floating over the game, it is in the recording. If a calendar reminder pops while you clutch, it is in the recording. If you play on one screen and keep chat on another, a whole-display capture of the wrong monitor is an empty file. None of that is a bug in the recorder; it is the definition of capturing a display.

What window capture does differently

ScreenCaptureKit can filter to a single window (or a set of windows and apps) instead of a whole display. Apple's SCContentFilter API is explicit about that choice: you either target a display, or you target a window — including a desktop-independent window that follows the app as you drag it between screens.

That filter is what makes clean game clips possible on a busy desktop. The menu bar stays out. Notifications stay out. Other monitors stay out. And because the stream is tied to one application, ScreenCaptureKit can deliver that application's audio without the rest of the system mix — the same mechanism covered in how to record game audio without Discord. Window capture is not only a framing choice; on modern macOS it is also the path to per-app sound.

When display capture is still the right tool

Prefer the whole display when the desktop is the subject:

• Multi-window tutorials where the viewer needs to see Finder, a browser, and the game together.
• Desktop demos, settings walkthroughs, or anything that jumps between apps.
• Moments where Discord callouts or on-screen chat are part of the story you want to keep.

In those cases, cropping later is fighting the recording. Capture the display on purpose, and accept that everything visible is part of the take.

When window capture is the better default for clips

Prefer a single window when you want a shareable game moment:

• Clean gameplay clips without desktop junk.
• Discord-safe audio — game sound in, call out of the file unless you choose otherwise.
• Fullscreen or borderless games where you still want the buffer to track that one app.
• Rolling-buffer / instant-replay workflows, where the buffer should hold the game, not your email.

That last point matters more than it sounds. A rolling buffer is only useful if what it held was the thing you meant to save. Filling thirty seconds of memory with a menu bar and a notification is wasted history.

How this shows up in Steam, OBS, and built-in tools

The same distinction appears under different names elsewhere. OBS lets you add a Display Capture or a Window Capture source; for Mac gameplay clips the window source is usually the one that matches the intent. Steam Game Recording is aimed at the game Steam launched, which is closer in spirit to a game-scoped capture than to a desktop grab — with the structural limit that it only knows about Steam titles. For a broader comparison of those options, see how to clip gameplay on a Mac and how to record the last 30 seconds.

Hindsight is built around the window path on purpose: a rolling buffer of one game window, saved after the moment, with optional game-only audio. That is not the only honest answer on a Mac, but it is the answer when the job is “clip what just happened in this game” rather than “film my entire desktop.”

A quick way to choose

• Is the desktop part of the story? Display capture.
• Is the game the only thing you want in the file? Window capture.
• Do you need the game's audio without Discord? Window capture with app audio — not a display grab of the speaker mix.
• Are you saving something that already happened? Pair window capture with a rolling buffer, not with Shift-Command-5 after the fact.

If you only change one habit after reading this, make it the capture target. Resolution, bitrate, and encoder matter. Recording the wrong surface wastes all three.

Game Porting Toolkit 4 does not end that argument. It changes the math underneath it.

The hard part was never one benchmark

A Windows game does not become a Mac game because an M-series GPU can draw enough frames. A publisher has to decide that evaluating, porting, testing, shipping, and supporting another platform will earn back the work.

That first evaluation used to be expensive before a studio even knew whether the answer was promising. Apple's Game Porting Toolkit changed that by letting developers run an unmodified Windows build on Apple silicon, inspect its performance, and see how its shaders translate to Metal.

GPTK 4 makes that first answer better and makes the work after it less mysterious. That is more consequential than adding one more game to a keynote. It lowers the cost of saying, “Yes, a Mac version is worth a real investigation.”

The early numbers are difficult to ignore

In Macworld's beta testing, GTA V rose from roughly 106 frames per second under GPTK 3 to around 176 under GPTK 4 on the same M4 Pro MacBook Pro and settings. Red Dead Redemption 2 moved from about 60 to 75 fps.

One machine and two games do not establish a universal uplift. Different engines hit different bottlenecks. Beta software moves. Anti-cheat can prevent a game from launching before the GPU gets anything to do.

But the source of the improvement matters. No new laptop was required. The games did not receive Mac-specific patches. Apple found more performance in the path between DirectX and Metal. The same Mac simply had less translation work standing between it and the game.

GPTK 4 is becoming a route to shipping, not just a compatibility test

The visible part of GPTK is the evaluation environment: launch a Windows executable on Apple silicon and find out what happens. GPTK 4 adds more of the unglamorous machinery needed after that first successful launch.

Developers can evaluate against Metal 4 from the beginning. New command-line Metal tools can capture and inspect GPU work. Apple also published porting skills for coding assistants, covering jobs such as windowing, controller support, shader conversion, MetalFX, and debugging.

Apple's WWDC 2026 demonstration shows the distinction clearly. The engineer still makes the architectural decisions and reviews the work; the assistant handles more of the platform-specific translation and repetitive debugging. In one example, Apple added a Metal 4 path to Godot's production renderer in days.

This is not a magic port button. It is something more believable: fewer weeks spent rediscovering how the Mac wants a game to render a window, present a frame, read a controller, or explain a broken shader.

Most Mac gamers will never install it—and can still benefit

GPTK is officially for developers. Players encounter its evaluation technology through projects and products such as CrossOver, which Apple now mentions directly on the toolkit page. Improvements there can make unsupported Windows games more playable before a native port exists.

The bigger benefit is less immediate. When a studio can reach a credible first playable quickly, profile it with familiar tools, and see a path to a native release, the Mac becomes easier to put on a roadmap. Not certain. Easier.

That difference sounds modest until you remember that every Mac port begins as an optional line in somebody's budget.

This is not the “Mac gaming is fixed” moment

GPTK 4 cannot make a publisher care about the Mac. It cannot approve an anti-cheat vendor, fund QA, maintain a port for five years, or give macOS the back catalogue Windows accumulated over decades. A translated game that runs well is still different from a native release with first-party support.

The toolkit and macOS 27-era features are also in beta. Some games will gain little. Some will break. The most dramatic early benchmark will inevitably become the number repeated without its settings or caveats.

None of that makes GPTK 4 small news. It makes it infrastructure news. Infrastructure is rarely the final reason somebody buys a game, but it is often the reason the game exists on that platform at all.

A platform grows around the games

Healthy gaming platforms are more than a store and a GPU. They accumulate compatibility tools, performance databases, controller utilities, streaming software, modding communities, capture apps, and people who know how to make all of it work together.

Hindsight is a tiny example of that second layer. We built instant replay specifically for Mac gaming because waiting for a Windows clipping company to remember macOS had stopped looking like a strategy. More playable games create more Mac gamers; more Mac gamers make specialized tools worth building; better tools make the platform easier to stay on.

GPTK 4 does not prove the flywheel is spinning yet. It is the clearest sign that Apple is reducing the effort required to start it. For once, the most interesting Mac gaming question is no longer whether the hardware can run the game. It is how many developers will decide the port is finally worth shipping.

The Mac's built-in recorder cannot go backwards

Pressing Shift-Command-5 opens Apple's Screenshot app. It can record the whole screen, a selected portion, and, on macOS Tahoe 26 or later, a selected window. But Apple's own instructions still begin with choosing a mode and pressing Record. QuickTime Player's New Screen Recording command opens those same controls on current macOS releases. Neither tool has footage from before you started it.

That makes Screenshot and QuickTime good for a tutorial or a session you planned to capture. They do not solve “save what just happened.” For that, choose one of the three approaches below.

Option 1: Steam Game Recording

If the game runs through Steam, start here because it is free and probably already installed. Open Steam, then Settings, then Game Recording, and select Record in Background. Valve's Game Recording guide explains that the background recording is temporary: older footage is overwritten when the disk allowance fills, while clips you create from it can be saved permanently.

Steam is the best no-cost answer when all the games you want to capture are launched by Steam and you like its overlay and recording library. Its structural limit is also clear: Valve says Game Recording captures games played through the Steam client. It is not the same solution for an App Store game, an emulator, a browser game, or a title launched through another store.

Option 2: OBS Replay Buffer

OBS Studio has a genuine Replay Buffer. In Settings, open Output, enable Replay Buffer, set the maximum replay time to 30 seconds, then assign a Save Replay hotkey under Hotkeys. Start the Replay Buffer before playing; the save hotkey writes the recent window to a file.

On a Mac, select an Apple VideoToolbox hardware encoder rather than x264 when your recording format supports it. OBS's hardware-encoding guide documents VideoToolbox support on Apple silicon and Intel Macs. If forgetting to start the buffer is the problem, OBS also documents the --startreplaybuffer launch option.

OBS is the most flexible free option. It is also a broadcast application: you configure a scene, sources, output, encoder, audio, and hotkeys. That setup is worthwhile for streaming or multi-source production. If all you want is one shortcut that is already armed, it may be more interface than the job needs. Our OBS comparison covers that trade-off without pretending OBS is a bad tool.

Option 3: a dedicated rolling-buffer app

A dedicated Mac clipper reduces the workflow to selecting a game and pressing one shortcut after the moment. Hindsight keeps an encoded ring buffer in memory, continuously evicts the oldest samples, and writes an MP4 only when you ask it to save. Set the clip length to 30 seconds in Settings, then use the global shortcut inside the game.

Hindsight captures a window rather than requiring a game integration, so the same mechanic works for native Mac games, Steam, CrossOver, Parallels, browser games, and emulators. A window capture also keeps the desktop and notifications out of the file and can take the game's audio without the Discord call. It is a paid option after the 14-day trial; Steam and OBS are the honest free answers above. A wider 2026 field guide to those free GitHub clippers and the paid Mac apps is in best Mac gameplay clipping apps.

Why a 30-second clip can be slightly longer

Compressed video cannot begin cleanly on an arbitrary frame. It has to begin on a keyframe: a complete image that the following frames can refer back to. Hindsight asks its encoder for a keyframe about every two seconds and begins a save at the newest keyframe at or before the requested point. A “last 30 seconds” file can therefore contain roughly 30 to 32 seconds. Starting on that boundary lets the app remux existing encoded frames instead of re-rendering the clip.

In the original Hindsight proof of concept, a 960×664 capture at 60 fps and 10 Mbps held a 30-second video ring in about 33 MB of memory. Saving the trailing eight seconds produced an 8.86-second, 10.7 MB file in well under a second. Those are development measurements, not a promise for every resolution and Mac; they are included to make the mechanism inspectable rather than calling it “lightweight” without a number.

Which method should you use?

• Only Steam games: use Steam Game Recording first.
• Streaming, layouts, or multiple sources: use OBS Replay Buffer.
• Any Mac game with the shortest workflow: use a dedicated clipper.
• You know before the moment: use Shift-Command-5; no rolling buffer is necessary.

Whichever route you choose, test the hotkey once before a real session. A rolling buffer can save only what it was configured and permitted to capture, and thirty seconds spent checking is cheaper than discovering that after the play you wanted.

The question that decides it: before or after?

Every screen recorder falls into one of two groups. Prospective tools record from the moment you press start, so you have to know beforehand that something worth keeping is about to happen. Retroactive tools — instant replay, replay buffers, "save the last N seconds" — are always holding the recent past in memory, so you press the button after the thing has already happened.

Almost all the frustration people have with Mac recording comes from using a prospective tool for a retroactive job. You cannot know that the next thirty seconds will contain the best round of your life. If that is the problem you have, skip to the last section, because the first four options do not solve it.

1. Screenshot toolbar (Shift-Command-5)

Apple's built-in Screenshot app has recorded the screen since macOS Mojave. Press Shift-Command-5, choose Record Entire Screen or Record Selected Portion, and press Record. The file lands on your desktop as a .mov when you stop.

Good for: a quick capture of something you are looking at right now, with no install and no configuration. Bad for: gaming. It records the whole screen or a rectangle of it, so notifications, your menu bar and anything on a second display are in the file. It does not capture audio from your applications without extra software. And it is entirely prospective.

2. QuickTime Player

In QuickTime Player, choose File, then New Screen Recording. On current macOS releases this opens the same Screenshot controls, with QuickTime available for playback and trimming afterwards.

Good for: recording a session you intend to edit down later. Bad for: the same reasons, plus QuickTime writes uncompressed or lightly compressed files that get very large very quickly. A long session can fill a drive.

3. OBS Studio

Free and open source, and by far the most capable thing on this list. OBS can capture a specific window, mix several sources, stream, and — importantly for this discussion — it has a Replay Buffer, which is a genuine retroactive recorder.

The catch is that none of that is on by default. OBS opens with a blank scene; you add sources and confirm your audio devices before anything is captured at all. The Replay Buffer then has to be enabled in Settings under Output, given a length, and bound to hotkeys for Start Replay Buffer and Save Replay Buffer. And it does not arm itself: you press Start Replay Buffer every session, and if you forget, the moment you wanted was never in memory to save. OBS documents a --startreplaybuffer launch option for people who want to automate that step.

Good for: anyone who streams, needs multiple sources, or is already comfortable in OBS. It is free and it is genuinely excellent. Bad for: the case where you just want a clip and do not want to operate a broadcast console. Also worth knowing: isolating a single application's audio is not something OBS does natively on macOS, which is why so many Mac OBS guides end with "install an audio routing driver". The full comparison is here.

4. Steam's built-in Game Recording

Steam Game Recording includes a background mode that keeps a temporary recording while you play so you can make a permanent clip afterwards. If the game you play is launched through Steam, this is free and already installed.

Good for: Steam games, if you are happy inside Steam's overlay and its clip library. Bad for: everything that is not a Steam game. A large share of Mac gaming happens outside Steam entirely — App Store titles, launchers like Battle.net, emulators such as RPCS3, Dolphin and RetroArch, games running through CrossOver or the Game Porting Toolkit, and browser games. Steam structurally cannot record any of those, because it only knows about games it launched.

5. A dedicated instant-replay app

This is the category NVIDIA created with ShadowPlay on Windows and Medal built a company on. The app holds the last N seconds of your game in a memory buffer, continuously discarding anything older, and writes a file when you press a key. Nothing touches your disk until you do.

On Windows there are several. On macOS the category was empty for years: ShadowPlay is NVIDIA hardware and has never run on a Mac, Xbox Game Bar is Windows-only, and Medal's current platform guide says it does not support macOS. RetroClip did it well and stopped being updated in 2020. See the full Hindsight and Medal comparison.

Hindsight is our answer to that. It sits in the menu bar, holds 15 seconds to 5 minutes of a single game window, and writes an .mp4 in about a second when you press ⌥⇧C — including from inside a fullscreen game. Because it captures one window rather than your screen, notifications and your second display are never in the clip, and it can record that game's audio without your Discord call.

For a dated roundup of free and paid Mac clippers — Steam, OBS, ReplayMac, Vestige, ClipForge, Rewinder, ClipMac, and Hindsight: Instant Replay — see best Mac gameplay clipping apps in 2026.

So which one?

• You know in advance and just need a file: Shift-Command-5. It is already there.
• You stream, or need multiple sources: OBS Studio, and nothing else comes close.
• You only play Steam games and live in Steam: Steam's own Game Recording.
• You want to clip things that already happened, in any game: an instant-replay app.

Two things that catch people out on macOS

Permission. Every one of these tools needs Screen & System Audio Recording permission in System Settings, under Privacy & Security. macOS also re-confirms it periodically, so a prompt reappearing for an app you already approved is normal and clicking Allow keeps the existing grant.

Audio. macOS has historically had no way to record another application's sound, which is why older guides tell you to install a virtual audio driver like BlackHole or Loopback. That is no longer strictly true: ScreenCaptureKit can select individual apps and windows and deliver audio alongside the video, which is how per-app audio can work without a virtual device. Whether a given tool uses that path is another matter. More on that here.

Why macOS mixes everything together

The signal sent to a Mac's speakers is a single mixed stream: your game, Discord, Spotify, a notification chime, and any browser tab you forgot about. By the time audio reaches that output device it has already been combined, and a recorder reading only that mixed output cannot separate it again.

This is why, for a decade, every Mac recording guide ended the same way: install a virtual audio device. Tools like BlackHole or Loopback create an additional audio route, you send applications into it, and the recorder captures that route instead. It works, but it adds routing that has to be configured and understood when another app cannot hear the device you expected.

What changed

Apple's ScreenCaptureKit, the modern framework for screen capture on macOS, provides fine-grained filters for displays, applications, and windows and can deliver audio with the selected stream. A recorder can use that filtering to take the game's audio before it is reduced to the speaker mix.

That is the whole trick, and it has two consequences worth understanding:

• It requires a window capture, not a display capture. If a tool is recording your whole screen, there is no single application to isolate audio from, so you get the full system mix. This is not a setting anyone can toggle around; it follows from what a display capture is.
• It needs no extra software. No virtual device, no routing, nothing to uninstall later. Your speakers keep behaving normally while the recording gets a clean feed.

Getting the game and not the call

In practice, whatever tool you use, the recipe is the same:

1. Capture the game's window, not the display it happens to be on.
2. Set the audio source to the captured application only, rather than system audio.
3. Put your microphone on its own track if you want your own voice, so you can decide later rather than at record time.

In Hindsight those are two switches in Settings under Audio, and the microphone is a third. A window capture defaults to that game's audio alone, which is the case people want most of the time; one setting flips it to the entire system when the callouts are the reason you are clipping at all.

When you actually want the whole mix

Do not over-correct. A clip of a squad wipe is often better with four people shouting over it, and a reaction is not a reaction without the voices. The reason to separate them is not that voice is noise; it is that recording them separately means the choice is still available afterwards. Recording the mix bakes the decision in at the moment you are least able to think about it.

What about the other people on the call?

Worth a sentence, because it is a real question and not only a technical one. Recording a voice call means recording other people, and consent rules for that vary by country and by US state — some require every participant to agree. Whether your friends mind is usually the more immediate consideration, but the legal position is not uniform, and "it was in the game clip" is not a defence anywhere. Our terms put the same point more formally.

Quick reference

• Game only, no Discord: window capture, audio set to the captured application.
• Game plus callouts: display capture, or a window capture with system audio.
• Your voice too, but removable later: microphone as a separate track.
• Still on an older tool that cannot do any of this: a virtual audio driver is still the fallback, and still works.

What the permission is

Apple calls it Screen & System Audio Recording. Its current support guide places it in System Settings under Privacy & Security. Without the grant, a capture app cannot receive the screen or window content it asked for.

The reason it is guarded this heavily is that screen contents are the most revealing thing on a computer. Everything else you protect with a password is on screen at some point after you have typed it — your email, your bank, your messages, your password manager while it is unlocked. A screen recorder is, by definition, an app that can watch all of it.

Granting it

1. Open System Settings, then Privacy & Security.
2. Choose Screen & System Audio Recording.
3. Turn the switch on for the app.

Apple's ScreenCaptureKit documentation requires capture apps to request this permission. Hindsight detects the grant during onboarding and moves on without asking you to restart the app.

Why it keeps asking again

This is the part that feels like a malfunction. In our own testing and support cases, recent macOS releases periodically re-confirm screen recording permission even for an application that is still listed as allowed.

So the prompt returning is expected. Clicking Allow keeps the existing grant — you are not re-granting from scratch and nothing is reset.

What is not expected is the prompt appearing on every single launch. That usually means the permission entry has become inconsistent, often after an app was moved, replaced by an update, or restored from a backup. The fix is to rebuild the entry:

1. Go to Privacy & Security, then Screen & System Audio Recording.
2. Select the app and remove it with the minus button.
3. Launch the app again and grant the permission when it asks.

Why a recorder must be in /Applications

Always run the installed copy of a recorder. Launching one copy from a disk image and a second copy from Applications can leave two different application identities competing for one permission entry. Move the app to Applications, eject the disk image, then grant permission to the installed copy.

How to tell it is actually working

A screen recorder that lacks permission usually cannot tell you so in an obvious way, because from its point of view the capture simply produces nothing. Look for a signal in the app itself rather than trusting the settings window: Hindsight dims its menu bar mark when the permission is missing, and the buffer readout in the sidebar stays at zero rather than counting up. If the readout is climbing, capture is genuinely running.

What the permission does not grant

Worth being precise, because "it can see my screen" sounds alarming and the scope is narrower than it sounds.

• Microphone is separate. A different permission, asked for separately, and only if an app records your voice.
• Camera is separate. Screen recording permission grants no camera access at all.
• It does not imply network access. An app can be permitted to see your screen and still never send anything anywhere. Hindsight's App Store build makes no network requests whatsoever, and you can revoke the permission at any time to stop capture immediately.

If you want the specifics of what a recorder on your machine can reach, ours are written out on the security page.