Meeting Guard – Auto Mute & Camera Protection, created by Sakif Mahmud Reshad, is a Chrome extension that prevents accidental audio and video broadcasts by disabling microphone and camera when joining meetings. It automatically mutes and defaults the camera off on entry, offers optional confirmation prompts, and exposes a lightweight settings panel. Aimed at remote workers, students, and privacy-conscious Google Meet users, it reduces the chance of unintended exposure and adds a cautious join behavior.

Automatically prevents unintended microphone and camera broadcasts

The extension activates immediately when you join a web meeting and applies two defensive defaults: auto-mute and camera-off on entry for Google Meet. Optional confirmation prompts require an explicit gesture before the browser hardware is enabled, which helps prevent accidental unmuting. The design supports a 'set-and-forget' workflow that focuses on join-time controls rather than in-call automation.

Has negligible impact on browser performance

Meeting Guard is described as extremely lightweight with zero impact on browser performance, so it imposes minimal overhead during sessions. The extension runs within Chrome and does not inject heavy scripts into pages, which the developer positions as a low-resource safeguard. That makes it suitable for standard desktop setups where added extension overhead is a concern.

Keeps permissions and settings under local control for privacy

The extension follows a privacy-first architecture and does not collect user data; settings remain on the device and the developer states there is no transmission of audio, video, or meeting analytics. Confirmation prompts are optional and operate through the browser UI rather than external services, so enabling hardware requires an explicit user action when prompts are active.

Fits Chrome-based Google Meet workflows but has limited cross-service reach

Built as a Chrome extension for the web version of Google Meet, it runs on Windows, macOS, and Linux desktops and exposes a compact settings panel via the extension menu. The developer plans to add support for additional meeting platforms, so current compatibility favors users who primarily use Meet. The lack of account-based sync means settings are tied to the local browser profile.

Useful defensive layer for cautious Meet users, with a platform scope trade-off

As a focused safeguard, the extension is a practical choice for professionals and students who prefer cautious defaults at join time and local-only settings. The extension enforces cautious behavior but does not replace broader meeting management tools, and its current focus on one meeting service means users who rely on multiple platforms should check compatibility. The extension suits workflows that prioritize local control over cross-service coverage.