Google's Humufish TPU will use Intel EMIB T instead of TSMC CoWoS, driven by CoWoS capacity constraints and the need to scale beyond 9.7x reticle size for its 10x reticle die — but Intel must jump from 90% to 98%+ yie... EMIB T uses tiny silicon bridges embedded in organic substrate only where dies connect, dramatic...

Create a landscape editorial hero image for this Studio Global article: Search & fact-check with cited sources for What is the significance of Google's decision to use Intel's EMIB-T packaging instead of TSMC's C. Article summary: Google's EMIB-T bet is a vote of confidence in Intel's packaging at a moment when CoWoS capacity is strangled, and for very large die sizes (~10x reticle) EMIB-T offers genuine cost and scaling advantages. But Intel face. Topic tags: general, general web, user generated. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fa
Google's decision to use Intel's EMIB-T advanced packaging instead of TSMC's incumbent CoWoS for its next-generation TPU (codenamed Humufish, formerly TPUv8e) is one of the most consequential shifts in AI chip supply chains today. It signals both a vote of confidence in Intel's packaging technology and a high-stakes bet that could reshape the semiconductor packaging market — if Intel can overcome a steep yield climb and a nagging irony involving its own flagship processor.
The primary driver for Google's switch is simple: there is not enough CoWoS capacity to go around. Surging AI demand has tightly constrained TSMC's CoWoS output, and Intel's EMIB is currently the only credible alternative at scale for AI accelerators . EMIB-T is described as offering "greater versatility and more scalable, lower-cost designs compared to CoWoS 2.5D approaches"
.
For Humufish specifically, Google's compute die will be manufactured in-house, while MediaTek handles the back-end design. The chip is expected in the second half of 2027 . Aletheia Capital estimates the Humufish die area at 9–10x reticle size with a substrate of roughly 13,700 mm² (16x reticle), making it too large and expensive for CoWoS — EMIB-T is the default packaging, with CoPoS as a backup
.
In short, Google needed a packaging solution that could scale to mega-packages that CoWoS would struggle with economically. EMIB-T is the answer.
The architectural difference between EMIB-T and CoWoS is fundamental. CoWoS mounts every die on a large silicon interposer that spans the entire package — a costly slab that wastes silicon at the edges as package sizes grow . EMIB, by contrast, embeds small silicon bridges into the organic substrate only where dies connect, leaving the rest of the substrate as cheap organic material
.
The difference is often described as a city-wide highway network (CoWoS) vs. a bridge at a river crossing (EMIB) . For Humufish's ~10x reticle die, that cost and scaling advantage is decisive.
Google has placed an order for Intel to build more than 3 million TPUs in 2028, confirmed by The Information citing four sources . Industry analysis suggests this is primarily an advanced packaging engagement, as Intel's own process nodes are not competitive with TSMC for leading-edge logic
.
But the volume target runs headlong into a manufacturing reality: Intel's EMIB-T has achieved roughly 90% technology-validation yield for the Humufish project . Analyst Ming-Chi Kuo says this is a positive signal given Intel's EMIB production history, but the benchmark is FCBGA assembly yield, which the industry runs at 98%+
. Kuo explicitly warns that climbing from 90% to 98% may be "more difficult than getting from 0% to 90%"
.
TSMC, for reference, targets 98% production yield for its 5.5-reticle CoWoS in 2026 — a significantly higher baseline . This yield gap means Intel must solve an extremely hard manufacturing-ramp problem to make the 3-million-unit volume economically viable. Every percentage point of yield loss on a high-value AI accelerator costing hundreds or thousands of dollars translates directly into tens of millions in lost revenue.
Intel is ramping its Project Pelican advanced packaging complex in Malaysia, slated to become operational in 2026 . Even so, hitting multi-million-unit output at high yield for a single customer in a new technology variant (EMIB-T) would be unprecedented for Intel's foundry packaging business.
Perhaps the most awkward element of Google's EMIB-T bet is this: Intel's own upcoming Diamond Rapids Xeon processor will not use EMIB. According to SemiAnalysis (via LinkedIn), "Intel Abandons EMIB for UCIe in Diamond Rapids… Diamond Rapids will likely use UCIe over substrate for a long-reach die-to-die interconnect instead" . Intel showed a UCIe-based die-to-die link at ISSCC
.
This creates a sharp irony: Intel is selling EMIB-T to Google as its marquee external packaging customer while abandoning it internally for its own flagship server CPU. The rationale is that for monolithic-ish CPU chiplets, UCIe over standard substrate offers sufficient bandwidth with lower cost and complexity — but the optics are awkward.
Intel is effectively asking the market to trust EMIB for Google's 3-million-unit TPU volume, yet its own premier product team chose a different interconnect standard. As SemiAnalysis put it, "Intel's 'best' packaging tech — for everyone but Intel" .
Note: The Diamond Rapids design details are drawn from industry analyst reports and LinkedIn posts from SemiAnalysis, which are credible but not official Intel confirmations .
Google's EMIB-T bet is a vote of confidence in Intel's packaging at a moment when CoWoS capacity is strangled, and for very large die sizes (~10x reticle) EMIB-T offers genuine cost and scaling advantages. But Intel faces a steep yield climb (90% → 98%+) and a multi-million-unit volume ramp with a technology it has never run at that scale. The contradiction that Diamond Rapids drops EMIB underscores how Intel promotes the technology for external customers while migrating its own highest-volume product to a different standard.
Studio Global AI
Use this topic as a starting point for a fresh source-backed answer, then compare citations before you share it.
Google's Humufish TPU will use Intel EMIB T instead of TSMC CoWoS, driven by CoWoS capacity constraints and the need to scale beyond 9.7x reticle size for its 10x reticle die — but Intel must jump from 90% to 98%+ yie...
Google's Humufish TPU will use Intel EMIB T instead of TSMC CoWoS, driven by CoWoS capacity constraints and the need to scale beyond 9.7x reticle size for its 10x reticle die — but Intel must jump from 90% to 98%+ yie... EMIB T uses tiny silicon bridges embedded in organic substrate only where dies connect, dramatically reducing cost and enabling larger packages than CoWoS; however, analyst Ming Chi Kuo warns the 90%→98% yield gap may...
Intel is selling EMIB T to Google as its marquee external packaging customer while reportedly abandoning EMIB for its own Diamond Rapids Xeon — switching to UCIe over organic substrate — creating an ironic contradicti...