The News, Explained
Google announced on October 12, 2026, that Google Meet calls are beginning to use post-quantum cryptography, or PQC. The first rollout covers laptop web clients and meeting room hardware. Google says mobile support is coming soon but gives no separate date for Android, iOS, or completion. The gradual web and room-hardware rollout may take up to 15 days from October 12. Source
Post-quantum cryptography refers to encryption methods designed to resist attacks from future, more capable quantum computers. The change does not signal that Google Meet encryption has been broken today. Google says a cryptographically relevant quantum computer capable of the threat described in the announcement does not currently exist. The purpose is to protect communications whose confidentiality may need to last for years. Source
The risk highlighted by Google is called Store Now, Decrypt Later. An attacker could collect encrypted call traffic today and keep it until a future quantum computer is powerful enough to attempt decryption. Under that model, waiting for such a computer to exist would leave older captured data exposed, so protection has to begin while the sensitive conversation is taking place. The post does not identify the specific algorithm, key-exchange construction, or compatibility mechanism used for this rollout. Source
The meeting interface and joining process do not visibly change. Administrators receive no separate control, and hosts and participants do not need to enable a setting or install another component. Google applies the required updates automatically. Coverage includes Google Workspace customers, Workspace Individual subscribers, and people using personal Google accounts, extending the change beyond managed company accounts. Source
Google Meet previously used quantum-safe encryption for client-side encrypted, or CSE, calls. CSE is an optional model in which media is encrypted with organization-controlled keys before it reaches Meet infrastructure. The new announcement extends post-quantum protection beyond that subset to all Meet calls. It does not say that ordinary Meet calls are adopting the same key-management model as CSE. Source
OYOPICK’s Take
A security-layer upgrade that arrives without making meetings harder to join is a useful direction. Even with uncertainty around the timing of practical quantum attacks, organizations whose conversations must remain confidential for years have a reason to migrate early. Default service-level protection can also reach more people than a feature that requires every participant to configure compatible settings.
The announcement does not give users a way to verify the protection used by an individual call. A mobile completion date, connection-level status, and documented compatibility behavior for older browsers and room hardware would make the rollout easier to audit. Automatic deployment and verifiable deployment should advance together when organizations rely on a security promise.
Post-quantum migration is a long standards and compatibility program rather than a single feature launch. Meet’s broad default rollout signals that an everyday communications service is treating future cryptographic risk as a present engineering task. We hope other services publish supported devices, algorithm-transition plans, and exception paths as they make the same move.