A zoom meeting record app joins your calls on its own, records or transcribes them, and tells everyone in the meeting that it is there. The method has four parts: get into the meeting even when you are not the host, start from your calendar without a click, give notice and a way to say no, and let any participant remove the recorder. Zoom's own recorder answers to the host, so the apps below differ mostly in how they handle the host and the consent step.
What a Zoom meeting record app has to cover
A complete setup is not one switch. It is four jobs that have to work together, and most frustration comes from a tool that does three of them well and quietly skips the fourth.
- Joining without being the host. A sales rep on a prospect's Zoom, or a consultant on a client's Teams call, does not control the Record button. The app needs a route in: a bot the host admits, a calendar connection, or a desktop app that captures your own device audio.
- Recording automatically from the calendar. The point is not having to remember. A good app reads your connected calendar and joins the meetings your rules select: all of them, only external ones, or only the ones you pick.
- Notifying people and handling consent. That means a visible bot, a chat message, an email before the call, or a consent prompt. Federal law sets one party's consent as the minimum, but about 11 states primarily require the consent of every party [1].
- A way out for participants. Someone who did not invite the recorder should be able to remove it or opt out without hunting for the host.
This is general information, not legal advice. The rules themselves, including calls that cross state lines, are in our guide to call recording laws and meeting consent. The table shows how each app handles the two parts that trip people up most.
| App | Getting in when you are not the host | How a participant stops it |
|---|---|---|
| Otter.ai | Teams and Meet through your connected calendar, though the host may have to admit it; on Zoom the host must allow it | Anyone can remove it; typing stop otter in chat removes every Notetaker |
| Fireflies.ai | Auto-joins calendar meetings whether or not you host; Zoom asks a host who is not on Fireflies to allow recording | Remove it from the participant list or type /ff leave; opt-out link in the optional compliance email |
| Fathom | The desktop app route works with free or paid Zoom; the Fathom Zoom app needs the host on a paid Zoom account | Remove it from the participant list; decline the consent email |
| Read AI | Joins only meetings you are invited to; on Zoom the user must have connected Zoom and be in the meeting | Read stop (report kept) or Opt out (everything deleted) |
| Avoma | On another company's Zoom, its bot joins when someone from your organization with Zoom connected attends | Under Permission required (Enterprise), one decline stops the recording |
| Krisp | The desktop app records bot-free with no host permission; the Krisp Bot needs the host to admit it | A removed Krisp Bot cannot rejoin |
| Granola | No bot; it transcribes your device audio live | Nothing to remove, so disclose out loud |
Recording a Zoom meeting as a participant: where the built-in way stops
Zoom, Teams and Meet all have a built-in recorder, though which accounts and plans include it varies. The catch is who holds the button. On Zoom the recording permission sits with the host, which is why every bot below either asks the host or goes around the host with a desktop app. If you are only a participant, the free route is asking the host every time. The exact clicks for hosts and guests are in our step-by-step guide to recording a Zoom meeting.
How to automatically record a Teams meeting
Teams has a native answer, but it belongs to the organizer. When an admin turns on the auto-recording policy, the Record and transcribe automatically option appears in meeting options set to Off, and organizers must switch it on for each meeting they want captured [2]. Admins can push it through meeting templates, but only organizers with a Teams Premium license can use assigned templates. If you did not organize the meeting, the option is not yours.
Before you connect a calendar, decide which meetings the app joins. Read AI joins all calendar events by default, and its own help warns that users who skip the settings get surprised.
So the built-in way works for one person who hosts everything on one platform. It breaks when you are a guest, when your week mixes Zoom, Teams and Meet, or when nobody remembers to press Record. That gap is the whole job of a recording app. The groups below follow the situation you are in, not a ranking.
If you mostly join other people's meetings
Guests gain the most, because the native recorder is closed to them. Three routes fit.
Its Notetaker auto-joins the meetings on your connected calendar whether or not you host, posts a chat message with a privacy link, and can email guests an opt-out link before the call.
Fireflies.ai's Notetaker auto-joins the meetings on your connected calendar whether or not you host. On Zoom, when the host is not a Fireflies user, Zoom asks that host to allow recording. An admin can set a team auto-record policy and add recording rules by keyword, email or domain. Accounts created on or after 1 September 2026 keep unlimited transcription on Free only while calendar auto-join stays on.
The Otter Notetaker joins from your connected calendar, needs no host role on Teams and Meet, posts a live-transcript link in chat, and leaves the moment anyone types stop otter.
Otter.ai covers the same ground from a different angle. On Teams and Meet you need not be the host if your calendar is connected, though the host may still have to admit the Notetaker; on Zoom the host must allow it. The full flow per platform is in our guide to setting up Otter on Zoom, Teams and Google Meet. To keep it out of one meeting, flip the per-event switch at least 30 minutes before.
The desktop app records audio, video or screen with no bot and no host permission; adding assistant@krisp.ai to an invite brings the Krisp Bot in automatically.
Krisp suits the guest whose host will not admit bots. The desktop app records audio, video or screen with no host permission at all. Nobody sees a bot, though. Krisp can notify participants, but some platforms block that message, so you have to tell people another way.
Desktop capture shows nothing to the other side. Otter.ai, Read AI, Fathom and Fireflies.ai all leave notice and consent with the user, with or without a bot.
If you host client calls and need consent on record
Hosts have the opposite problem. Getting in is easy; proving that people were told is the hard part.
Auto-record follows your choice of All, External, Internal or No Meetings; the visible Notetaker never records silently, and external meetings you host with one guest can get a consent email.
Fathom records automatically on every plan, with a choice of All, External, Internal or No Meetings. Its Notetaker is visible and never records silently. Consent emails go out only for external meetings you host with exactly one guest. A guest who declines turns off auto-record for that call, but when a guest never answers, Fathom still joins. Our page on Fathom's two Zoom routes explains when the host must be on a paid Zoom account.
Its chat notice gives everyone two commands: Read stop ends recording and keeps the report, Opt out leaves and deletes everything. One opt-out stops it for all.
Read AI puts the exit in every participant's hands. Its chat notice offers Read stop, which ends recording and keeps the report so far, and Opt out, which deletes everything. One opt-out stops recording for everyone. Calendar auto-join covers all events by default, so turn off Add Read for a meeting at least 15 minutes before it starts.
Admins pick one of four consent levels; under Permission required a participant who declines stops the recording, and reminder emails carry a recording disclaimer before meetings.
Avoma gives admins a named consent setting. There are four levels: Disabled, Notified only, Acknowledgment required and Permission required. Reminder emails with a recording disclaimer go out before meetings. Avoma says plainly that recording law is the customer's job. Our walkthrough of Avoma's consent levels and bot rules shows which level sits on which plan.
A bot in the participant list is easy to miss. Open the call with one sentence saying it is recorded and how to opt out; Granola recommends disclosing out loud for in-person and phone calls.
If a recording is what you want to avoid
Some teams want notes from a call without any recording sitting on a server. That is a different answer to the same problem.
No bot and no audio kept: it transcribes your device audio live, and it can post a chat message and show a camera watermark so people know.
Granola keeps no audio or video on any plan. It transcribes your device audio live, with no bot in the call. Other participants see nothing unless you turn on its chat message or camera watermark. It also never starts automatically for every meeting, so it does not cover part two. That is why it counts as partial here.
Combinations that cover the gaps
One tool rarely covers all four parts for every meeting you have. These pairings fill the holes.
- Native plus a bot. If you organize Teams meetings, use Teams' own auto-record for those. Add Fireflies.ai or Otter.ai from your calendar for the meetings other people host.
- Free first, then upgrade for consent. Start on Fathom Free set to External, or Otter.ai Basic. Move up once you need Fathom's banner removal or Read AI's advance opt-out emails.
- Two tools by meeting type. Use Granola for internal one-on-ones where a bot feels heavy. Use Read AI or Avoma for external calls where a documented opt-out matters.
Mixing tools has one cost. Notes end up in two places. Pick the split by meeting type and keep it, so you always know where a call lives.
How to choose a Zoom recording setup
Start with the meeting you have most often, not the feature list. Then match it.
- Mostly a guest? Fireflies.ai or Otter.ai, joining from your calendar. Krisp if hosts refuse bots, and then you give notice yourself.
- Need a recorded opt-out? Read AI, where one Opt out ends the recording for everyone, or Avoma's Permission required level.
- Hosting one-guest client calls? Fathom's consent email is built for exactly that shape.
- Internal calls where a recording feels wrong? Granola, with disclosure out loud.
- People in several states? Follow the strictest rule everywhere. Otter itself advises users to apply all-party consent practice universally.
Federal law allows recording when one party consents [3], yet a single attendee in an all-party state changes the picture. Tell people early. It costs one sentence.
Frequently asked questions
Can I record a Zoom meeting as a participant without the host knowing?+
Otter.ai's desktop app and Granola capture your own device audio without showing anything to others, and Krisp's desktop app records with no bot and no host permission. That removes the notification, not your duty to tell people, and in all-party consent states recording without everyone's consent can break the law.
Does a visible meeting bot count as consent?+
It counts as notice. Granola says its chat message and watermark give notice, not consent, and Otter.ai calls its settings safeguards rather than legal compliance.
What happens if someone removes the recorder mid-meeting?+
It depends on the app. Read stop keeps Read AI's report up to that point, a Fireflies.ai Notetaker removed in its first 3 minutes leaves no transcript, and a removed Krisp Bot cannot rejoin.
How do I automatically record Teams meetings I don't organize?+
Teams' own Record and transcribe automatically option belongs to the organizer. For other people's meetings, a calendar bot is the route: Otter.ai joins Teams as an anonymous guest the organization must allow, and Fireflies.ai needs guest access or a lobby bypass.
The bottom line
A good Zoom meeting record app is really four parts: a way in when you are not the host, rules that join from your calendar, notice with a real chance to say no, and a one-step exit for anyone in the call. Guests should look at calendar bots or bot-free desktop capture. Hosts who need proof of notice should look at opt-out commands, consent emails and consent levels. Whatever you pick, say out loud that the call is recorded, because every vendor here leaves that duty with you.
- [1] Reporters Committee for Freedom of the Press (Nov 2026) https://www.rcfp.org/introduction-to-reporters-recording-guide/
- [2] Microsoft Learn (Nov 2026) https://learn.microsoft.com/en-us/microsoftteams/manage-teams-auto-recording
- [3] Cornell Law School (Legal Information Institute) (Nov 2026) https://www.law.cornell.edu/uscode/text/18/2511