Does Google Meet Record Your Entire Screen? What a Meet Recording Captures

What Google Meet can see at all

• Whatever you present: a tab, a window, or your entire screen
• Your camera and microphone, when they are on
• The active speaker, in a recording
• The chat conversation, saved alongside a recording in some configurations

Present is a choice with three settings

Google Meet's presenting documentation lists exactly three options: a tab, a window, or your entire screen. Which you pick decides what everybody else sees, and it also decides what happens to audio — presenting a Chrome tab shares that tab's audio by default, while presenting a window or your entire screen shares audio only if you enable "Also share system audio".

One detail catches people out: your camera does not turn off when you present. Google notes that if your camera is on, your video stays active while presenting, so you are visible and your content is visible at the same time.

What a recording actually contains

Google is more specific here than most vendors. It states that video recordings include the active speaker and anything presented, and that captions can be saved too. Then it states the limit directly: other windows or notifications are not saved in the recording, and pinning a participant to your own screen does not change who appears in it.

That last pair of sentences is the answer to the question this page is named after. A Meet recording is a recording of the meeting — the speaker and the presented content — not a recording of a participant's desktop. If you present your entire screen, that presentation is what is recorded.

Recording is also not a silent act. Google says participants get a notification when the recording starts or stops, and that people outside the organisation and mobile app users are notified even though they cannot control it.

Meet is not the thing evaluating you

It is worth being blunt about scope. Google Meet documents no proctoring features: no screenshot interval, no webcam anomaly model, no browser lockdown, no application blocking. It is a meeting product, and in an interview it usually sits beside a coding tool that does have those features.

So if the real question is what an interview can see, Meet answers only a slice of it. The coding platform — CoderPad, HackerRank, CodeSignal, Codility — is where the integrity controls live, and each has its own page in this cluster.

What is recorded, and what is only flagged

An artefact a reviewer can open later is a different thing from an event counted on a report, and both are different from an action the platform simply prevents. Every control Google Meet documents, tagged and sourced:

What Google Meet's documentation does not say

The gaps are as useful as the features, and they are the part nobody else writes down. Where Google Meet states a limit, it is quoted below. Where it is silent, the entry says it is silent — undocumented is not the same as absent, and we are not going to present it as one.

• Google states that other windows and notifications are not saved in a Meet recording.
• Pinning does not change the recording. Google says that if you pin a participant to your screen, it will not change who is shown in the recording.
• Meet documents no proctoring capability — no periodic screenshots, no webcam anomaly detection, no browser lockdown, no application blocking. It is a meeting product.
• Recording is not universally available to participants: Google describes the host recording by default, with participants able to record only under specific organisational conditions.

What candidates get wrong about Google Meet

The most persistent belief is that a Meet recording somehow captures more than what was on the call. Google states plainly that other windows and notifications are not saved, which is about as direct a denial as a vendor gives.

The second is not realising the camera stays live while presenting. Candidates present, relax their face, and forget they are still on video in the corner of everyone's screen.

The third is the audio surprise. Presenting a tab shares that tab's audio automatically; presenting a window or a screen does not, unless you turn on system audio. Half the "we can't hear the video" moments in interviews are this.

The fourth is assuming Meet's behaviour extends to whatever coding tool is open next to it. It does not — those are separate products, and the coding tool is the one with proctoring features.

Worth knowing before you sit down

• Presenting a single tab is a documented option and the most narrowly scoped of the three, which matters mostly because it also affects audio.
• Google's own advice for avoiding the infinite-mirror effect is to present a new window or a specific tab rather than the meeting window.
• Your camera keeps running while you present, so you are on video and on screen at the same time.
• A recording notification appears for everyone when recording starts and stops. If it is being recorded, you will know.
• In some configurations the chat is saved alongside the recording as a separate file, so what you type in chat can outlive the call.
• Nothing here constrains the coding tool. If the problem lives in a proctored assessment platform, that platform's rules apply regardless of Meet.

What this means if you use an AI assistant

The failure mode is the same one that applies everywhere: present your entire screen and you are presenting a composited image of the desktop. Present a tab or a window and the scope is that tab or window. Google documents the three options; it does not document how the underlying capture pipeline treats windows that ask to be excluded from it, and neither does anyone else.

Which option you use is usually the interviewer's call, not yours. Nothing on this page is advice about which to pick — it is a description of what each one covers.

Meet's recording is the narrowest surface on this page. Google states other windows and notifications are not saved, and the recording follows the presentation rather than the presenter's desktop.

The camera is the channel that never stops. It stays on while you present, it is in the recording as the active speaker, and it is pointed at a room rather than at a screen.

Stealth Interview is a desktop app for macOS and Windows that is not captured by screen-sharing or meeting software, and it transcribes interviewer audio in real time. Google Meet's documented behaviour is above, from Google's pages, and the coding platform's rules are a separate question with a separate page.

Google Meet proctoring: common questions

Sources

Every page below is published by Google Meet or its parent company. Last checked in August 2026; vendors change these features often, so check the date on the page you land on.

• Google Meet — Present during a video meeting
• Google Meet — Record a video meeting

Product home: Google Meet

Other platforms you may be facing

• Every platform in this cluster — assessments, live coding tools and meeting software, side by side.
• The blog — how the technical interview loop is actually scored.
• AI interview assistant — what Stealth Interview does during a live interview.