DDR5 now, DDR6 direction
Compare data-rate ranges, reported sub-channel concepts, module ecosystems, and platform dependencies without assuming draft details are settled.
Open the comparison tableIndependent standards reference
The DDR6 Generation, Explained.
A reference for the next DRAM transition—separating published standards from draft work, reported architecture, and vendor roadmaps.
Read headline numbers carefully. Reported interface targets are not the same thing as a frozen specification, validated controller, available module, or shipping platform.
Orient yourself before comparing numbers.
DDR6 and LPDDR6 belong to the same broad transition, but they are distinct standards paths with different interfaces, packaging, power goals, and deployment schedules.
01 / SYSTEM CONTEXT
What is DDR6?
Why another DRAM generation is being developed, and how bandwidth, latency, power, signaling, and controller design interact.
Explore architecture → 02 / STANDARDS SPLITLPDDR6 vs DDR6
LPDDR6 is a published low-power standard. It does not mean desktop DDR6 DIMMs or compatible PC platforms are available.
Separate the standards → 03 / ROADMAPTimeline
A cautious 2025–2029 tracker for standards work, validation, server adoption, and possible client-platform transitions.
View the tracker →What can be said with confidence?
This site marks the status of each technical claim instead of blending standards text with reporting.
Confirmed
LPDDR6 is published as JEDEC JESD209-6. Its low-power architecture targets mobile and tightly integrated systems, including on-device AI workloads.
Reported
Desktop and server DDR6 remain an emerging generation. Architecture directions and data-rate ranges discussed in industry reporting are not treated here as final specifications.
Platform dependent
Memory availability alone does not create an upgrade path. A deployable system also requires controller, PHY, package or module, firmware, board, and CPU-platform support.
Two useful ways into the reference.
Compare the generational direction, or inspect the evidence behind each status label.
Evidence before conclusions
Consult standards bodies, vendor technical briefs, and reputable reporting. Every roadmap statement should retain its date and uncertainty.
Review sources and methodology