There is no established date for “Q-Day,” the arrival of a quantum computer capable of breaking today’s public-key cryptography. But the work to prepare for that possibility has real timelines: standards are available, migration takes planning, and some governments have set 2035 transition targets. Those targets are not a forecast of when quantum computers will arrive or a universal legal deadline for every organization.
When will quantum computers break encryption?
No reliable date is known. NIST says it is not possible to predict exactly when—or even whether—quantum computers will break present-day encryption. A year quoted in a forecast is an estimate from the person or organization making it, not an agreed Q-Day or an official standards deadline.
As an Amazon Associate I earn from qualifying purchases.
The term cryptographically relevant quantum computer (CRQC) means a quantum computer capable of breaking cryptography considered secure against classical computers. The existence of quantum computers today does not mean that they already have this capability.
Recommended Free Tools
It also helps to distinguish post-quantum cryptography (PQC) from quantum cryptography. PQC consists of mathematical algorithms designed to resist attacks from both classical and quantum computers; those algorithms run on conventional computing systems. Quantum cryptography instead relies on quantum physics.
#1 Best Overall
Is 2035 a real deadline?
2035 is a transition target in U.S. and UK government guidance, not a prediction that a CRQC will appear that year. The target’s meaning and applicability depend on the jurisdiction, the system involved, and the applicable policy, contract, or regulation.
| Date or milestone | What it refers to | What it does not establish |
|---|---|---|
| August 13, 2024 | NIST finalized its first three post-quantum standards: FIPS 203, FIPS 204, and FIPS 205. | It is a standards publication date, not a migration-completion date or a quantum-computer forecast. |
| 2035 — U.S. | The 2022 National Security Memorandum 10 set a goal of mitigating as much quantum risk as feasible by 2035. NIST’s transition direction aims to deprecate and ultimately remove vulnerable algorithms from NIST standards by then, with high-risk systems moving sooner. | It does not show that every private organization is covered by one identical law or contract deadline. NIST’s IR 8547 is identified in its publication record as an initial public draft, so its transition specifics are draft guidance. |
| 2035 — UK | The UK National Cyber Security Centre (NCSC) sets 2035 as a target for completing migration. | It is a separate UK target, not the same policy as the U.S. goal. NCSC acknowledges that some harder-to-migrate technologies may take longer. |
| 10 to 20 years | NIST says that moving a cryptographic standard into information systems has historically taken this long. | This is a general observation about standards-to-deployment lead time, not a forecast of when quantum computers will break encryption. |
When someone calls a date “the deadline,” ask what it measures: a forecast of quantum capability, a government planning goal, a standards transition, or a binding obligation for a defined system. Marketing can collapse those different things into a single countdown. The date alone does not establish who must act or what action is required.
Rank #2
What does “harvest now, decrypt later” mean?
“Harvest now, decrypt later” (HNDL) describes collecting encrypted information today in the hope of decrypting it if a future quantum capability becomes available. It creates a confidentiality risk before such a computer exists: an attacker could retain captured data until it can be decrypted.
The concern is greatest for information that must remain secret for many years. A useful way to assess urgency is to consider how long the data needs protection, how sensitive it is, and how exposed or important the systems carrying it are. HNDL concerns confidentiality; it is not by itself evidence that a current encrypted connection has already been broken.
Are post-quantum standards ready?
Yes. NIST published three final standards on August 13, 2024. They serve different cryptographic roles, so it is inaccurate to describe all three simply as encryption algorithms.
| Standard | Algorithm | Role |
|---|---|---|
| FIPS 203 | ML-KEM | Key establishment |
| FIPS 204 | ML-DSA | Digital signatures |
| FIPS 205 | SLH-DSA | Digital signatures |
NIST says these standards can and should be put into use now. That does not mean every organization should deploy an untested implementation everywhere at once. Products, services, and protocols need updates, and changes must work with the systems that connect to them. NIST’s separate transition report, IR 8547, is still labeled an initial public draft; its transition direction should not be confused with the final status of FIPS 203, 204, and 205.
Rank #4
Do I need to do anything now?
For an organization, the immediate task is to understand where vulnerable public-key cryptography is used and plan a risk-based transition. Joint CISA, NIST, and NSA guidance recommends a roadmap, vendor engagement, and a cryptographic inventory; NIST’s migration work also emphasizes prioritization and interoperability testing.
- Assign ownership and create a roadmap. Give a named team or accountable owner responsibility for coordinating readiness across security, IT, procurement, and affected business units.
- Ask vendors about their plans. Request product and service roadmaps for PQC support, including relevant protocols and dependencies. Record what vendors support now, what they plan to change, and when.
- Inventory public-key cryptography. Identify its use across hardware, software, services, and protocols—not just servers the organization directly operates. Record what each use protects and which systems depend on it.
- Prioritize by exposure and impact. Give attention to sensitive data that must remain confidential for many years, critical systems, and broad cryptographic infrastructure such as identity and signing systems.
- Test compatibility and performance. Plan interoperability work before production changes. A technically supported algorithm still has to work across products, services, and protocols in the organization’s environment.
- Sequence procurement and migration. Use the inventory, vendor support, system criticality, data lifetime, and applicable national requirements to decide what to address first and when.
This is an engineering and procurement program, not simply a cipher change on one machine. NIST’s mathematician and PQC standardization project head, Dustin Moody, put the recommendation plainly: “We encourage organizations to begin their transition to these standards immediately to ensure their data remains secure in the quantum era.”
The appropriate pace depends on an organization’s data lifetime, exposure, criticality, vendor support, and applicable rules. The available guidance supports beginning discovery and planning; it does not establish an identical deployment schedule for every organization.
How to read a quantum deadline claim
- Forecast: Who made the estimate, and is it clearly identified as a forecast rather than an agreed date?
- Jurisdiction: Is the claim about U.S. policy, a UK target, another country’s rules, or a private organization’s own plan?
- Scope: Which standards, systems, assets, contracts, or organizations does it cover?
- Milestone: Does the date concern quantum capability, migration planning, standards deprecation, or a binding requirement?
- Readiness: Does the plan account for inventory, vendor support, interoperability, and deployment constraints?
These questions separate a useful transition target from an unsupported countdown without dismissing the risk. The quantum break date remains uncertain; the standards and migration work are already real.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
