Google sets 2029 for migration to post-quantum cryptography

Google announces a clear deadline: 2029 as a key year to secure the quantum era by migrating to PQC (post-quantum cryptography). Why does this matter for you, your company, or your favorite app? Because quantum computing is advancing and could break the protections we use today to encrypt data and verify identities.

What Google proposes and why it makes sense

Google lays out an ambitious timeline for the transition to PQC, based on real progress in quantum hardware, quantum error correction, and estimates about quantum factoring. This isn't science fiction — it's a practical response to a tangible risk.

The company highlights two distinct threats:

• The immediate risk: store-now-decrypt-later attacks. An attacker can capture encrypted traffic today and wait for a future quantum computer capable of breaking it.
• The future risk: digital signatures. These need migration to PQC before a Cryptographically Relevant Quantum Computer (CRQC) exists.

Google has already adjusted its threat model to prioritize PQC migration in authentication services, because digital signatures are a critical point for online security. And they urge other engineering teams to follow suit.

What concrete changes Google mentions

• Direct integration in products: Android 17 includes PQC digital-signature protection using ML-DSA, aligned with NIST recommendations.
• Support already deployed: Google Chrome has PQC support and Google Cloud offers solutions and guidance for the transition.
• Shared leadership: as an early player in quantum hardware and PQC, Google proposes its timeline to give the industry clarity and urgency.

What can you do today? (practical steps)

• Cryptographic inventory: identify where you use encryption and digital signatures. Which libraries, protocols, and keys are in production?
• Prioritize authentication and signatures: follow Google's recommendation and advance PQC protection in services that manage identities and signatures.
• Test hybrids: implement hybrid schemes (classical + PQC) to minimize risk during the transition.
• Follow standards: stay aligned with NIST and official documentation; avoid proprietary solutions without public review.
• Train the team: don't underestimate the human factor; getting your team to understand PQC and why it matters speeds adoption.

Impact for users and companies

For end users, the migration to PQC should be invisible: apps and services update behind the scenes. For companies, it means technical planning, testing, and coordination between infra, security, and product teams.

Does it take time? Yes. Is it worth starting now? Also yes. A deadline like 2029 is not meant to alarm you, but to create the right urgency so changes happen calmly and securely.

Brief reflection

The arrival of quantum computing won't erase today's security overnight, but it does shift the agenda: the prudent move is to prepare now so the transition isn't a last-minute sprint. Google offers a date and concrete steps — the question is whether other players will follow, and how fast your organization will move.

Original source

https://blog.google/innovation-and-ai/technology/safety-security/cryptography-migration-timeline