Google said its gradual rollout of post-quantum cryptography for Google Meet began October 12, 2026, with laptop web clients and meeting-room hardware. The update applies to Google Workspace customers, Workspace Individual subscribers, and people using personal Google accounts. Google says it is automatic, so users and administrators do not need to turn it on. (Google’s announcement)
When the update appears—and what users need to do
There is no setting to enable: Google says it applies the necessary updates automatically. On Rapid Release and Scheduled Release domains, feature visibility may take up to 15 days. That window describes when the feature may appear, not a date by which every account is guaranteed to have it.
Google says mobile support is coming soon. The company’s announcement does not give a date for that rollout. (Google’s announcement)
Why Google is expanding post-quantum protection
Post-quantum cryptography (PQC) is designed to resist attacks from future quantum computers. Google describes the concern as “store now, decrypt later”: an attacker could record encrypted traffic now and try to decrypt it if a capable quantum computer becomes available later. Google said no cryptographically relevant quantum computer existed at the time of its October 12 announcement. (Google’s announcement)
Google also says Meet had previously used quantum-safe encryption for client-side encrypted (CSE) calls. The new rollout expands that protection to Meet calls more broadly. (Google’s announcement)
Google Cloud’s algorithm applies to a different service
Google’s documentation names hybrid X25519MLKEM768 for specified TLS connections handled by Google Cloud Load Balancing. That is a load-balancer specification, not a description of Google Meet’s cryptography. (Google Cloud Load Balancing documentation)
