How to stop screen recording during paid Zoom and Meet classes
Zoom can keep meetings out of screen captures on supported apps, and both tools control their own recording, but neither stops a phone camera or forwarded links. Paid batches need more.
On this page 9 sections
- Why meeting tools leak paid classes
- What Zoom can and can't stop
- What Google Meet can and can't stop
- Settings worth turning on if you stay with Zoom or Meet
- If you use Zoom
- If you use Google Meet
- When to move paid classes to a protected live class
- Moving over without losing what works
- Frequently asked questions
Zoom and Google Meet control who can use their own record buttons, and Zoom can keep meetings out of screen captures on supported apps. Neither can stop a phone filming the screen, Google documents no Meet setting that blocks a participant's own recorder, and both rely on forwardable links. That is acceptable for a free demo class. For a paid batch, a protected live class is safer, because each student signs in with their own account and sees their own watermark.
Why meeting tools leak paid classes
Zoom and Meet were built for meetings, where everyone in the room is trusted. A paid batch is different: some people in the room have every reason to copy what they see, and a few want to sell it.
- Links travel. A joining link or meeting code posted in a batch group can be forwarded to anyone.
- Names prove nothing. Participants can join under any display name unless you require sign-in.
- Recording happens on the student's device. A meeting tool controls its own record button, not every other app on the laptop.
- Recordings get shared as links. A cloud recording or Drive link sent to the batch often keeps working for anyone who has it.
- Screen sharing works both ways. A student can share your class into a call with friends.
Each of these has a partial fix inside the tools. None has a complete one.
What Zoom can and can't stop
| Zoom feature | What it does | What it doesn't do |
|---|---|---|
| Recording permissions | The host decides who can use Zoom's own local and cloud recording | Controls only Zoom's recorder, not other apps |
| Prevent screen capture | Keeps the meeting window out of screenshots and screen-capture tools on recent Zoom desktop and mobile apps | Can't see a camera; people on the web app or Linux join with audio only; can't be changed mid-meeting |
| Watermark | Shows all or part of each viewer's email address over shared content and video | Works only when participants must sign in to join |
| Sign-in and registration | Only signed-in users join, and registrants get their own link | Students can still share their sign-in or their device |
See Zoom's support pages on preventing screen capture and adding a watermark for the current requirements. Settings like these change between versions, so check them before each new batch.
Capture prevention is useful, but it depends on every student using a supported app, and students on unsupported devices lose the video entirely. For paid classes the watermark matters more, because it also identifies the account behind a camera recording. Our guide to dynamic watermarking explains why a mark that names the viewer is the one that counts.
What Google Meet can and can't stop
- Recording is controlled. Meet recording is available only on some Google Workspace editions, and an administrator decides who can record. With host management on, only the host and co-hosts can record.
- Access can be restricted. Hosts can set a meeting to Open, Trusted or Restricted. Restricted admits directly only people invited through Google Calendar or added by a host, and it isn't available to personal Google accounts.
- Hosts can lock participation. They can stop participants sharing their screen or sending chat messages, remove people, and end the meeting for everyone.
- A watermark exists, with conditions. On eligible Workspace subscriptions, hosts can add a watermark showing the meeting code and each viewer's email address. Participants must be signed in on a supported app or browser, and Google says starting a recording or live stream turns the watermark off.
What Meet doesn't offer is screen-capture blocking. Google's help pages describe no setting that stops a participant's own screenshots or screen recorder. The watermark rule also means a class you record for the replay can't carry Meet's watermark while it is being recorded. See Google's guides to recording a meeting and watermarks in Meet.
Settings worth turning on if you stay with Zoom or Meet
If you use Zoom
- Require sign-in for every class, and use registration so each student gets their own link.
- Turn on the watermark and, where students' apps support it, screen-capture prevention.
- Allow recording by the host only, and never post cloud recordings as open links.
- Use a waiting room, and admit only names on your batch list.
- Stop participants sharing their screen unless a student is presenting.
- Use a fresh meeting for each batch, not a personal meeting ID reused for months.
If you use Google Meet
- Use Restricted or Trusted access, with invitations sent through Google Calendar.
- Turn on host management, so only you and co-hosts can record and control the room.
- Lock screen sharing and chat when you don't need them.
- Keep recordings in Drive with downloading and copying turned off, shared only with enrolled students.
Expect some friction. Requiring sign-in means every student needs a working Zoom or Google account. In a large batch, some of them will have trouble joining on the first day. Plan for that with a short joining guide and a test session before the batch starts.
These settings cut down casual leaks. They won't stop a paying student filming the class, or recording it on a device the tool doesn't protect. Our guide to stopping camera recording of online classes explains why that route stays open everywhere.
When to move paid classes to a protected live class
| What differs | Zoom or Meet | A protected live class in your own app |
|---|---|---|
| Who can join | Anyone with the link, unless you require sign-in | Only enrolled students, signed in to their own account |
| Identity on screen | An email watermark, if sign-in is required and conditions are met | The student's own details over the class |
| Screen recording | Blocked only on supported Zoom apps; not blocked on Meet | Blocked or detected in the apps, depending on the device |
| Replays | Cloud or Drive links | Inside the same app, under the same rules |
| Device rules | None tied to paid access | Device limits and one stream at a time |
| Fees and access | Managed separately from the meeting | Access ends when enrolment ends |
Signs it's time to move: your classes have turned up on Telegram, or batches are larger than a meeting comfortably handles. Another is a fee high enough that one leak costs real money. Keep Zoom or Meet for what they do well: free demo classes, parent meetings and small mentoring calls.
Moving over without losing what works
Teachers like meeting tools because students can talk back. Before you switch, check that the live class can still do what your teachers rely on:
- Doubt-solving with a student brought on stage, by voice or video.
- Chat and polls that keep up with the teacher.
- Attendance that matches your batch list automatically.
- Replays that appear soon after the class ends.
- Playback that copes with weak 4G and hostel Wi-Fi.
Large live classes often mix two delivery methods: a near-instant connection for the few people speaking, and a slightly delayed stream for everyone watching. Our explainer on WebRTC vs HLS for live classes covers the trade-offs. Pilot one batch first, tell students why the change protects their fees, and retire the old meeting link once the batch has moved.
Getting around a meeting tool's capture protection to copy a paid class can be an offence under section 65A of the Copyright Act, 1957. Sharing the copy also infringes copyright. This is general information, not legal advice.
Upclass runs courses, live classes and tests in an institute's own branded apps on Android, iOS, Windows and Mac. Fees go to the institute's own payment gateway. VidSafe adds dynamic watermarking, screen- and camera-recording detection, account-sharing prevention and VidSafe proprietary encryption. VidSafe adds visible and invisible watermarks that are extremely hard to remove, even after heavy re-encoding, so a leaked copy can be traced back to the account it came from. See our LMS for coaching institutes.
Frequently asked questions
Can Google Meet detect screen recording?
Google doesn't describe Meet detecting other screen recorders. Meet notifies participants when its own recording starts or stops. A participant using their device's recorder, or a second phone, triggers nothing. Treat anything shown in a Meet class as recordable.
Does Zoom's prevent screen capture stop phone recording?
No. It keeps the meeting window out of screenshots and screen-capture tools on supported Zoom apps, but a second phone pointed at the screen records normally. Zoom's watermark, which shows each viewer's email address over shared content, is what helps identify the source of a filmed copy.
Can participants record a Zoom meeting without permission?
Not with Zoom's own recording, if the host hasn't allowed it. They can still use other recording software where screen-capture prevention is off or unsupported, or film the screen with a phone. Zoom's recording permissions control Zoom's recorder, not the whole device.
Is Zoom or Google Meet safe for paid classes?
They're fine for free demos and small mentoring calls, but weak for paid batches. Links can be forwarded, recording can't be fully blocked, and replays are often shared as open links. For paid classes, a live class inside your own app, with personal logins and per-student watermarks, closes most of those gaps.