
HBM is a type of high-bandwidth memory that vertically stacks multiple layers of DRAM and connects them to GPUs, AI ASICs, and other compute chips through an ultra-wide interface. AI servers depend on HBM not because ordinary memory is completely insufficient, but because large model training, long-context inference, and high-concurrency services require much higher memory bandwidth, capacity, energy efficiency, and shorter packaging distance. Once you understand HBM, you can better understand the competitive logic behind AI chip and memory companies such as NVIDIA, AMD, SK hynix, Samsung, and Micron.

HBM stands for High Bandwidth Memory. It is still a form of DRAM, but its structure is different from ordinary server memory modules. HBM vertically stacks multiple DRAM dies, connects them through TSV and other vertical interconnects, and then packages them together with a GPU or AI accelerator. Its core role is not long-term data storage, but high-speed delivery of model parameters, activations, cache, and intermediate results during computation.
Ordinary DDR memory is usually installed on the server motherboard and serves the CPU, operating system, databases, and general-purpose workloads. HBM sits much closer to the GPU or AI ASIC, with shorter connection distance and a wider interface. You can think of DDR as the server’s large-capacity main memory, while HBM is the high-speed data supply layer close to the compute chip. Both are important, but they serve different positions and performance goals.
HBM is composed of multiple DRAM dies, a base die, TSVs, micro bumps, an interposer, and a package substrate. TSVs are vertical channels that pass through silicon and connect different DRAM layers. The interposer provides high-density interconnects between the GPU and HBM. In the HBM4 standard, JEDEC expands the interface width to 2048-bit to meet AI and HPC demand for higher bandwidth, greater capacity, and better energy efficiency.
| Component | Location | Main Function | Impact on Performance |
|---|---|---|---|
| DRAM Die | Inside the HBM stack | Stores data during operation | Determines capacity and part of speed |
| Base Die | Bottom of the stack | Manages interface and signal transfer | Affects energy efficiency and customization |
| TSV | Through silicon | Vertically connects multiple chip layers | Improves stacked data transfer efficiency |
| Micro Bump | Between chip layers | Enables precise connections | Affects yield and reliability |
| Interposer | Beneath GPU and HBM | Provides high-density interconnects | Determines package scale and bandwidth |
| Package Substrate | Bottom of the module | Connects the accelerator module | Affects power delivery, signaling, and cooling |
The “High Bandwidth” in HBM does not come simply from pushing frequency higher. It comes from increasing total throughput through much wider data channels. GDDR often relies on higher per-pin speeds, while HBM transfers data through more parallel channels. This design is better suited to AI accelerators with strict power and space constraints, because package area around the GPU is limited and memory chips cannot be spread out indefinitely.
Another common misconception needs to be clarified: HBM is not SSD and not NAND Flash. Like ordinary DRAM, HBM is volatile memory and cannot retain data after power is lost. It also cannot fully replace DDR memory in servers, because HBM is usually packaged together with the GPU, is expensive, has costly capacity, and is not easy to expand. It is more suitable for storing high-value data that the compute chip needs immediately.
Summary: HBM is a stacked DRAM technology designed for high-performance computing. Through multiple DRAM layers, TSVs, a base die, an interposer, and advanced packaging, it brings memory closer to the GPU and delivers extremely high data throughput through an ultra-wide interface. The difference between HBM and ordinary DDR is not that one is advanced and the other is obsolete, but that they serve different positions in the system: DDR handles general system memory, while HBM supplies high-speed data close to the AI accelerator. Once you understand this, you can see why AI chip launches always emphasize HBM capacity, bandwidth, and generation.

AI servers depend on HBM because GPU compute capability has grown far beyond the speed at which traditional memory can feed data into compute units. If data cannot continuously enter the GPU, many compute cores will wait for memory, preventing expensive AI accelerators from running at full load. This bottleneck is often called the “memory wall.” HBM does not directly create compute power, but it determines whether GPUs can continuously receive enough data.
Large model training repeatedly reads model weights, activations, gradients, and optimizer states. The larger the model, the more parameters and intermediate data it has, and the stronger its dependence on memory bandwidth and capacity becomes. Inference is also demanding, especially when long-context models, reasoning models, multi-turn conversations, and high-concurrency requests expand KV Cache. In its introduction to Blackwell Ultra, NVIDIA emphasizes that 288GB of HBM3E is critical for long-context, multi-trillion-parameter models, and high-concurrency inference. This shows that AI accelerator competition has expanded from compute alone to the memory system.
During training, the first value of HBM is improving GPU utilization. GPUs are good at large-scale parallel computation, but only if data is continuously supplied. If HBM bandwidth is insufficient, matrix compute units may wait, and theoretical FLOPS cannot fully translate into real throughput. The second value is reducing model partitioning. When a model or training state cannot fit inside the HBM of a single GPU, it must be split across multiple GPUs, increasing communication, synchronization, and scheduling complexity. The third value is energy efficiency. Data movement itself consumes significant power. Because HBM sits close to the GPU, it can increase throughput under relatively controlled power consumption.
HBM is becoming increasingly important during inference. In earlier stages, many people assumed that training depended more on HBM, while inference was mainly a compute-cost issue. Long-context and agent applications have changed that view. KV Cache grows with context length, concurrent users, and generation length, continuously occupying HBM. NVIDIA H200 comes with 141GB of HBM3E and 4.8TB/s of memory bandwidth; AMD Instinct MI325X comes with 256GB of HBM3E and up to 6TB/s of peak memory bandwidth. These specifications show that AI accelerator vendors are not only adding compute, but also increasing memory capacity and bandwidth.
| AI Workload | Main Data Pressure | More Dependent on Bandwidth or Capacity | Role of HBM |
|---|---|---|---|
| Large model pretraining | Weights, gradients, activations | Both bandwidth and capacity | Improves GPU utilization |
| Instruction tuning | Model weights, training state | More capacity-sensitive | Reduces model partitioning |
| Real-time inference | Weight reads, KV Cache | More bandwidth-sensitive | Reduces generation latency |
| Long-context inference | Large-scale KV Cache | More capacity-sensitive | Holds longer context |
| High-concurrency service | Multi-user cache and state | Both bandwidth and capacity | Improves per-GPU throughput |
| Multimodal models | Image, video, and text features | Both bandwidth and capacity | Supports complex data flows |
HBM also affects the total cost of ownership of AI servers. If a GPU can only release part of its performance because of a memory bottleneck, cloud providers need to buy more GPUs to complete the same task. In contrast, larger HBM capacity and higher bandwidth may increase single-GPU throughput and lower infrastructure cost per token or per training task. Of course, real costs also depend on model architecture, precision, parallelism strategy, network interconnects, and software optimization, so HBM should not be viewed as the only variable.
Summary: AI servers need HBM because large model computation is increasingly constrained by data supply. Training needs bandwidth to improve GPU utilization and capacity to reduce model partitioning. Inference needs bandwidth to reduce latency and capacity to support KV Cache, long context, and concurrent requests. Without enough HBM, GPUs may suffer low utilization, higher cross-GPU communication, longer inference latency, and higher unit service costs. HBM is not a secondary spec of AI chips; it is a core system resource that determines AI server efficiency.

HBM, DDR, and GDDR are all based on DRAM technology, but they serve different positions and goals. HBM focuses on extremely high bandwidth and energy efficiency inside the package. DDR focuses on general capacity, standardization, and scalability. GDDR focuses on high bandwidth on graphics cards at relatively controlled cost. AI servers usually do not rely on only one type of memory, but allow HBM, DDR, and other storage layers to work together.
Server DDR5 is usually installed in memory slots on the motherboard and serves the CPU, operating system, databases, data preprocessing, and general-purpose computing tasks. HBM, by contrast, is packaged close to the GPU or AI ASIC and serves the data currently being processed by the accelerator. Even if an AI server contains multiple GPUs and each GPU has large amounts of HBM, the server still needs system DDR memory for CPU tasks, the network stack, scheduling systems, and data preparation.
GDDR is more common in consumer GPUs, workstation graphics cards, and some accelerator cards. It is usually placed around the GPU on the PCB and achieves high bandwidth through higher per-pin speed. Compared with GDDR, HBM has a wider interface, better energy efficiency, and tighter packaging, but it also has much higher cost and manufacturing complexity. This is why gaming GPUs usually continue to use GDDR, while top-tier AI accelerators are more likely to use HBM.
| Comparison Dimension | HBM | DDR5 | GDDR |
|---|---|---|---|
| Main Location | Near GPU/AI ASIC package | Server motherboard | Graphics card PCB |
| Main Goal | Extremely high bandwidth and energy efficiency | General capacity and scalability | Graphics and GPU bandwidth |
| Interface Feature | Ultra-wide, short distance | Standardized memory channels | Higher per-pin speed |
| Cost Level | Highest | Relatively lower | Between HBM and DDR |
| Upgradability | Mostly fixed after packaging | Expandable through memory modules | Usually fixed on the graphics card |
| Typical Applications | AI, HPC, data center GPUs | CPU servers, databases | Gaming GPUs, workstations |
HBM cannot fully replace DDR. The reason is straightforward: HBM is expensive, is not easy to expand like DIMMs after packaging, and its capacity cost is not suitable for carrying all system memory. A large amount of data preprocessing, file caching, CPU inference, databases, and system scheduling in AI servers still require DDR. HBM is more suitable for storing high-value data that the GPU currently needs, rather than putting all data in the server into HBM.
HBM will not fully replace GDDR either. Consumer GPUs and many workstation applications are cost-sensitive, and most gaming, rendering, and lightweight AI workloads do not necessarily require HBM-level bandwidth or packaging cost. HBM becomes more reasonable only when the gains in performance, energy efficiency, and package density justify the cost. The use of different memory solutions across AMD, NVIDIA, and other vendors’ product lines is essentially a trade-off among performance, cost, power consumption, and market positioning.
Summary: HBM, DDR, and GDDR do not simply replace one another; they divide labor. DDR is suitable for general system memory, GDDR is suitable for graphics and GPU scenarios with greater cost sensitivity, and HBM is suitable for AI and HPC chips that need the highest bandwidth, capacity, and energy efficiency. For AI servers, HBM solves high-speed data supply near the GPU, DDR solves system memory for the whole machine, while SSDs and HDDs handle data storage at farther layers. Efficient AI infrastructure depends on coordinated layers of memory and storage, not just stacking a single memory type.
HBM is expensive and slow to expand not only because DRAM wafers are costly, but because it requires multiple known-good dies to be thinned, etched, stacked, bonded, packaged, tested, and then validated together with the GPU at system level. Any issue in one chip layer, connection, or packaging step can affect the yield of the entire HBM stack. Increasing wafer capacity does not mean sellable HBM increases at the same pace.
HBM manufacturing usually starts with advanced DRAM wafers. Manufacturers first produce DRAM dies, then perform wafer thinning and TSV formation, and then screen for dies that are suitable for stacking. Multiple dies must then be precisely aligned, bonded, and connected to the base die to form a complete HBM stack. That stack must also be integrated with the GPU, interposer, and package substrate, before going through electrical testing, thermal testing, reliability testing, and customer platform qualification.
CoWoS often appears together with HBM because top-tier AI GPUs usually need advanced packaging to place the GPU and multiple HBM stacks within the same module. TSMC CoWoS is a 2.5D packaging technology that uses an interposer to integrate logic chips and HBM, providing high-density interconnects for high-performance computing. The concepts should be separated clearly: HBM is memory, CoWoS is a packaging platform, and the GPU is the compute chip. Together, they form an AI accelerator module.
| Manufacturing Step | Core Task | Common Bottleneck | Impact on Final Product |
|---|---|---|---|
| DRAM wafer | Produces memory chips | Advanced process yield | Affects capacity, speed, and cost |
| TSV formation | Builds vertical channels | Etching and metal filling difficulty | Affects stacked connection quality |
| Die screening | Selects qualified chips | Defect detection accuracy | Affects overall yield |
| Stack bonding | Connects multiple chip layers | Alignment, warpage, bonding defects | Determines stack reliability |
| Base die | Manages high-speed interface | Logic design and process choice | Affects energy efficiency and customization |
| Advanced packaging | Integrates GPU and HBM | CoWoS and similar capacity | Determines shipment pace |
| Testing and qualification | Validates stability | Test time and customer standards | Affects mass-production timing |
| Thermal management | Controls stack temperature | Higher power density | Affects performance and lifetime |
HBM is difficult to scale because it consumes more manufacturing resources. A high-end AI accelerator may carry multiple HBM stacks, and each stack requires multiple DRAM dies. Compared with ordinary DRAM, HBM consumes more wafer, packaging, testing, and material resources. SK hynix’s 2026 memory market outlook also notes that HBM3E and HBM4 will remain important directions for AI memory demand, while supply capability depends on capacity, yield, and customer validation.
Thermal control is another challenge. HBM uses a 3D stacked structure, making it more difficult for heat from internal dies to dissipate. The more layers are stacked, the higher the bandwidth, and the higher the power density, the more important thermal management becomes. Future HBM competition will not only be about bandwidth and capacity, but also materials, base die design, packaging structure, cooling solutions, and system-level design.
If you are following HBM supply chain companies, you should look not only at technology leadership, but also at actual trading costs. In public markets, US-listed companies such as Micron, NVIDIA, AMD, Marvell, Seagate, and Western Digital are related to AI memory, chips, or data centers. When tracking related assets through Biya, you should also watch company earnings, customer qualification, capital expenditure, and valuation. Biya charges $0 commission for US stock trading, while platform fees, external institutional fees, and other charges are subject to US stock trading fees and the order display. Public market information does not constitute investment advice. Service availability depends on user location, identity verification results, platform rules, and applicable laws and regulations.
Summary: HBM scarcity comes from the entire supply chain, not from one manufacturing step. It requires advanced DRAM, TSVs, stacked bonding, base dies, interposers, advanced packaging, testing qualification, and thermal management to mature together. Wafer expansion only solves part of the problem. The true determinants of shipment volume are yield, packaging capacity, customer qualification, and system reliability. This is why HBM average selling prices and margins are usually higher than ordinary DRAM. Its high price is not only due to strong demand, but also because it binds memory, packaging, and AI accelerator design together.
HBM is moving from HBM3E toward HBM4, but old and new products will not switch over instantly. A more realistic situation is that HBM3E continues to serve many existing AI accelerators, HBM4 scales with next-generation GPUs and AI ASICs, and HBM4E plus custom HBM enter customer validation. Future competition is not only about who has more capacity, but who can balance bandwidth, capacity, yield, customer qualification, packaging resources, and capital expenditure discipline.
HBM generation upgrades mainly move in four directions: higher bandwidth, larger capacity, better energy efficiency, and stronger customization. Micron’s HBM4 materials show that HBM4 uses a 2048-bit interface and is designed to deliver higher bandwidth and capacity for AI and HPC. When Samsung announced HBM4 commercial shipment, it said its HBM4 achieved stable transfer speeds of 11.7Gbps and could be further enhanced to 13Gbps. In its HBM4E showcase, Samsung also mentioned 16Gbps per pin and 4.0TB/s bandwidth, showing that the next stage of competition will continue to revolve around AI accelerator data bottlenecks.
| HBM Generation | Main Upgrade Direction | Typical Application Stage | Key Observation Point |
|---|---|---|---|
| HBM2/2E | Establishes stacked high-bandwidth architecture | Early AI and HPC | Technology validation and cost |
| HBM3 | Increases capacity and bandwidth | Generative AI training | GPU adoption scale |
| HBM3E | Higher speed and larger stacks | Current mainstream AI platforms | Customer qualification and supply capability |
| HBM4 | 2048-bit interface, custom base die | Next-generation AI accelerators | Yield, energy efficiency, and mass production |
| HBM4E/custom HBM | Higher performance and system coordination | Next-generation GPUs/ASICs | Co-design and cost control |
One important change in HBM4 is that the base die moves closer to system-level customization. In the past, HBM looked more like a standardized memory product. In the future, HBM may increasingly become a system component jointly defined by GPU vendors, ASIC designers, memory makers, and foundries. Customers may demand deeper optimization in interface protocols, power management, package size, signal integrity, thermal paths, and data access methods. This raises the technical barrier and may also bind leading customers more tightly with leading HBM suppliers.
To judge the competitiveness of HBM manufacturers, you can track eight indicators:
For retail investors, HBM is both a technology issue and a cycle issue. On the demand side, watch AI training, inference, cloud provider capex, and custom ASIC deployment. On the supply side, watch the expansion plans, customer qualifications, and yields of SK hynix, Samsung, and Micron. On the valuation side, consider whether the market has already priced in high-growth expectations. To track related US-listed companies, you can use US stock information search to view basic information, then cross-check earnings reports, product launches, and order changes. Users who meet applicable service conditions can also download the App to review order fees and risk disclosures.
Summary: The next stage of HBM competition will move from pure memory specifications toward a system-level battle across memory, logic chips, and advanced packaging. HBM3E will continue to support many existing platforms, while HBM4 serves next-generation AI accelerators with a wider interface, higher bandwidth, and stronger customization. Whether manufacturers can generate long-term returns depends on customer qualification, mass-production yield, packaging resources, product mix, and capital expenditure discipline. High industry growth does not mean profits or stock prices of related companies will necessarily rise in sync. Investors still need to consider the latest earnings, supply-demand cycles, and valuation.
Once you understand HBM, the AI chip supply chain becomes clearer. For NVIDIA and AMD accelerators, you should not only look at compute power, but also HBM capacity and bandwidth. For SK hynix, Samsung, and Micron, competition is not only about memory shipments, but also customer qualification, yield, and HBM revenue mix. Advanced packaging players such as TSMC can also affect final supply pace. For retail investors, tracking the HBM supply chain means putting technology upgrades, capital expenditure, product qualification, memory pricing, and trading costs into the same framework. Public market analysis should support judgment, not replace personal risk assessment. Any trade should be based on your own capital plan, platform rules, and local regulatory requirements.
HBM is a type of DRAM, but it uses 3D stacking, TSVs, an ultra-wide interface, and advanced packaging. Its storage principle is similar to DDR, but its product structure, connection method, and use cases are different. It mainly serves GPUs, AI ASICs, and HPC accelerators.
Usually no. HBM mainly serves GPUs or AI accelerators, while DDR handles CPU system memory, operating systems, data preprocessing, databases, and general-purpose tasks. AI servers need HBM and DDR to work together, rather than replacing all memory layers with one memory type.
Not necessarily. Larger HBM capacity can hold bigger models, KV Cache, and batch workloads, but actual speed is also affected by HBM bandwidth, GPU compute power, model architecture, software optimization, precision choices, and multi-GPU communication. Capacity alone is not enough to judge performance.
Usually no. HBM is highly integrated with the GPU, interposer, and package substrate, so it is difficult to replace separately like a memory module after the server leaves the factory. When more HBM is needed, users usually replace accelerators, add more GPUs, or adjust model deployment strategies.
The main reasons are cost and packaging complexity. Most gaming, office, creator, and lightweight AI workloads can be served by GDDR or DDR without paying for HBM’s advanced packaging cost. HBM is more suitable for high-end AI, HPC, and data center accelerators.
The main risks include slower AI capital expenditure, customer qualification delays, weaker-than-expected yield, advanced packaging capacity shortages, thermal issues, and oversupply after expansion. When evaluating related companies, investors should refer to the latest earnings reports, product disclosures, platform rules, and local regulatory requirements.
*This article is provided for general information purposes and does not constitute legal, tax or other professional advice from BiyaPay or its subsidiaries and its affiliates, and it is not intended as a substitute for obtaining advice from a financial advisor or any other professional.
We make no representations, warranties or warranties, express or implied, as to the accuracy, completeness or timeliness of the contents of this publication.



