Private meeting recorders for Mac

Short answer: the private option is an app that taps your Mac's own system audio, transcribes it on the machine, and throws the audio away once it has the text. Nothing joins the call, nothing is uploaded, and no recording of the meeting is left behind. The catch is that "private" gets used for three different promises that do not always travel together, so most round-ups compare apps that are not actually offering the same thing. Below is what each of these apps really does with your audio, why every one of them asks for a permission that looks alarming, and where mine is the wrong pick.

At a glance

Prices and tiers were checked in August 2026 and they move around, so treat the figures as a shape rather than a quote.

"Local", "bot-free" and "nothing kept" are three different promises

This is the distinction the round-ups blur, and it is worth pulling apart before you compare anything, because an app can honestly claim one of these while failing the other two.

Bot-free is about the meeting. Does a new participant appear in the room with your name plus "Notetaker" after it? Everyone can see a bot, everyone knows you are recording, and on a call you do not host you often cannot add one at all. An app that captures your Mac's own audio output adds nobody to the roster.

Local is about the transcription. Does the speech recognition run on your machine, or is the audio uploaded to a service that sends text back? This is the one most apps mean when they say private, and it is the one that gets checked.

Nothing kept is about what is on your disk afterwards, and almost nobody asks it. An app can be bot-free and fully on-device and still write an audio file of the entire meeting into a folder, where it sits until you remember to delete it. A transcript is text you can read and prune. A recording is everything anybody said, including the five minutes before the meeting properly started.

Those three questions have different answers for every app on this page, which is why "private meeting recorder" on its own tells you almost nothing.

Why every one of these apps asks to record your screen

Install any of them and macOS will ask for Screen Recording permission, which feels wrong for something that only wants sound. It is not a mistake and it is not the app overreaching. On macOS, the framework that captures the audio coming out of your Mac is ScreenCaptureKit, and it is gated entirely by that one permission, listed as Screen & System Audio Recording on newer versions of macOS.

The part that explains the whole situation is that there is no alternative for a developer to reach for. ScreenCaptureKit access is controlled purely by the privacy database, with no code-signing entitlement that grants it, so an audio-only recorder cannot request a smaller permission instead. Since macOS 13 that standard Screen Recording grant is what lets an app tap system audio at all. In Parameety this is not abstract: it checks the grant with CGPreflightScreenCaptureAccess and asks for it with CGRequestScreenCaptureAccess, and without it there is no audio to transcribe.

There is a narrower route now. macOS 14.4 introduced Core Audio Taps, which needs only a System Audio Recording permission rather than the full screen grant. It is the more proportionate ask for an app that never wants pixels, and over time it is where audio-only recorders should end up. Until an app moves to it, the screen permission is the price of system audio, and you can reasonably ask a developer which of the two they use.

Parameety

Mine, so read this knowing that. It is a menu-bar app that records the sound coming out of your Mac, a Slack huddle or a Google Meet you do not host, and transcribes it locally with the Parakeet TDT model through FluidAudio. Nothing joins the meeting, because it is a passive tap on system output rather than a participant.

On the third question above, the audio buffer is discarded once it has been transcribed and is never written to disk. What you are left with is a markdown transcript in your Documents folder, one file per meeting. Your own voice is opt-in rather than on by default: the microphone is a separate permission and a separate toggle, and with it off the app records only the other participants.

Where it is the wrong pick, plainly. It does not label speakers. I built that, and then removed it, because the microphone and the system audio overlap and echo through speakers badly enough that the labels were confidently wrong, which is worse than no labels at all. It does not write summaries or pull out action items either. You get the model's raw text and nothing dressed on top. And it needs macOS 15 or later on Apple Silicon, so an Intel Mac is out. If you want speaker-attributed notes with a summary at the end, this is not the app and one of the others below will serve you better.

MacWhisper

The broadest of the local options and the one I would point most people at if Parameety does not fit. It transcribes locally using Whisper and Parakeet models, and it automatically records calls from Zoom, Teams, Webex, Skype, Chime and Discord with, in its own words, no bots joining. That platform coverage is genuinely wider than mine.

There is a free tier, and a Pro tier at 64 euros as a one-time purchase with lifetime updates, which adds system-wide dictation, more export formats and hooks into external AI services for the extra processing. Note that last part in light of the summarizing point further down: the transcription staying local does not mean everything else does, if you turn those integrations on.

MacParakeet

Free and open source under GPL-3.0, running on macOS 14.2 or later on Apple Silicon. It records microphone and system audio directly rather than inviting a bot, and keeps speech recognition on local models with no cloud speech service in the core meeting flow. It frames its pitch as privacy by architecture rather than by policy, which is the right framing: a promise you can verify from how the thing is built beats a promise in a terms document.

If you want this whole category for nothing and are comfortable with an open-source tool, start here rather than with anything paid, mine included.

Meetily

Also free, under the MIT licence, and the only one here that is not Mac-only: it runs on macOS, Windows and Linux, with Apple Silicon acceleration on the Mac. Transcription runs locally through Whisper or Parakeet, and it captures system audio directly rather than joining as a bot, mixing the microphone and system tracks together.

It goes further than the others by summarizing as well, which it does through Ollama. That is still on your machine if you run Ollama locally, and it is the cleanest example of why the transcription and summarizing questions have to be asked separately.

Local transcription is not local summarizing

This is the gap I would most want you to leave with, because the marketing language genuinely does not distinguish them.

An app can run speech recognition entirely on your Mac, so the audio never leaves, and then hand the finished transcript to a cloud model to write the summary and extract the action items. At that point the contents of your meeting have been uploaded. Not as audio, but as text, which is smaller, searchable and much easier to paste somewhere it should not go. "The audio never leaves your Mac" can be completely true while the substance of the conversation does.

You can see the seams in how these apps describe their own setups. Alter lists Ollama, LM Studio, bring-your-own-key or cloud providers, which means the privacy answer depends on which one you picked. Meetily summarizes through Ollama. MacWhisper's Pro tier integrates with external AI services. None of that is dishonest, it is just two questions where most people ask one. If a summary matters to you, ask where the summarizing runs, not only where the transcribing runs.

The subscription note-takers, and what you trade

Otter is the reference point for the other model. Its pricing page puts Pro at $16.99 per user per month, or $8.33 per user per month billed annually, with a Business tier at $30 and a free Basic tier, and it describes joining Zoom, Microsoft Teams and Google Meet to write and share notes automatically. Its pricing page does not state where the audio is processed, so I am not going to assert it here.

What you get for that is the part the local tools are weakest at: polished summaries, speaker attribution, search across every meeting you have ever had, and sharing that works for a team. What you trade is that something joins the call where everyone can see it, the meeting leaves your machine, and the cost recurs for as long as you use it. For a sales team that lives in meeting notes, that is a reasonable trade. For recording a handful of calls a month on your own laptop, you are renting an infrastructure you do not need.

How to choose

Start with the machine. On an Intel Mac, or on macOS 14 or earlier, the Apple Silicon tools are out and MacWhisper's broader compatibility is the first thing to check. If you need Windows or Linux too, Meetily is the only one here that crosses over.

Then decide whether you want a summary. If you do, take one of the tools that writes one and ask the question above about where that step runs. If you genuinely just want a text record of what was said, the simpler tools are less to manage and less to trust.

Then decide whether free is the point. MacParakeet and Meetily are free and open, and if that settles it then it settles it. What I built Parameety for is the narrow case: you want the meeting written down, you want nothing in the room, you want no audio file left over afterwards, and you would rather pay once than manage anything. That is a real preference and it is the only one I am claiming.

Whichever you pick, the routes themselves are compared in the pillar on how to record a meeting on a Mac, and the version where no audio file is ever created is covered in transcribing a meeting without recording it.

A word on consent (not legal advice)

Capturing audio on your own machine fires no notification to anybody. The platform does not announce it the way it announces a Zoom or Teams recording, and no bot appears for people to notice. That is the point of the approach and it is also the responsibility that comes with it.

Recording law varies by where you are and where the other participants are, and plenty of employers have a policy that is stricter than the law. The simple version that keeps you out of trouble everywhere is to say you are recording. I am a developer rather than a lawyer, so treat this as the obvious advice it is rather than as guidance for your situation.

About this guide

I make Parameety, one of the apps here, so read the whole thing with that in mind. I have tried to be useful rather than flattering: I have said plainly that mine does not label speakers or write summaries, that it needs macOS 15 on Apple Silicon, and that if you want this category for free you should look at MacParakeet or Meetily before you look at me. What the other apps do comes from their own pages and repositories rather than from memory, read in August 2026, and where a page did not state something I have left it out rather than filled it in. Prices and tiers move.

FAQ

What is the most private way to record a meeting on a Mac?

The one where the audio never becomes a file and nothing joins the call. That means an app that taps your Mac's own system audio, transcribes it on the machine, and discards the audio buffer once the text exists. Check three things separately, because they are three different promises: does a bot join the meeting, does the transcription run on-device, and is the audio kept afterwards. Plenty of apps pass the first two and quietly fail the third by leaving a recording of the whole meeting on your disk.

Why does a meeting recorder ask for Screen Recording permission?

Because on macOS that is the permission system audio sits behind. Apple's ScreenCaptureKit is the framework an app uses to capture the sound coming out of your Mac, and it is gated entirely by the Screen Recording entry in System Settings, listed as Screen & System Audio Recording on newer versions. There is no code-signing entitlement a developer can request instead, so an audio-only recorder still has to ask for the screen permission. Since macOS 13 that grant covers system audio, and macOS 14.4 added a narrower Core Audio Taps route that needs only System Audio Recording.

Can I record a meeting I am not hosting?

Technically yes, because capturing your Mac's own audio output happens on your machine and does not depend on the meeting platform granting you a record button. That is why this route works for a call you were invited to rather than one you run. Whether you should is a separate question from whether you can. Recording law varies by where you and the other participants are, plenty of workplaces have their own policy, and nothing about capturing audio locally fires a notification to the room, which makes telling people your job rather than the platform's.

Do local meeting apps still send anything to the cloud?

Some do, and the wording hides it. An app can transcribe entirely on-device and then send the finished text to a cloud model to write the summary and pull out action items, which means the contents of your meeting still leave the machine even though the audio never did. Alter lists Ollama, LM Studio, bring-your-own-key or cloud providers as its options, and Meetily pairs local transcription with Ollama summarizing. Local transcription and local summarizing are two separate claims, so check for both.