Visual walkthrough — 2.5D packaging and interposers
This is the companion visual derivation for 2.5D packaging and interposers. Every symbol is earned before it is used. A smart 12-year-old should be able to follow from line one.
Step 1 — What even is a wire, electrically?
WHY start here? Because before we can ask "how much energy?" or "how fast?", we must agree what physical thing the energy is fighting against. That thing is capacitance.
PICTURE. Look at the figure. The blue metal line is the wire; the little grey plates hanging below it are the capacitance to the ground plane underneath. A longer wire = more of these little plates in parallel = a bigger bucket.

Step 2 — Capacitance grows with length
WHY this step? This is the single fact that links geometry (how long the wire is) to physics (how much charge it eats). Everything downstream rests on it.
PICTURE. The figure shows a short wire and a long wire side by side. Count the buckets: the long wire (orange) has more. The straight red line in the small graph shows rising in a straight line as grows — that straightness is the word "proportional".

Step 3 — What does it cost to send one bit?
WHY the tool ""? We need the energy stored when a capacitor is charged, because energy-per-bit is the currency of chip power budgets. The physics result for charging a capacitor from empty to voltage is exactly — no other formula answers "how much energy did filling the bucket take?".
The punchline: with and fixed, is directly proportional to . Short wire → cheap bit.
PICTURE. The figure fills the bucket to level ; the shaded area is the stored energy. Notice the shaded triangle — its average height is , which is where the comes from.

Step 4 — Interposer vs PCB: put in real lengths
WHY compare a ratio? Because absolute joules depend on messy constants we don't want to memorise. A ratio cancels the shared stuff and shows the lever cleanly.
PICTURE. Two routes drawn to scale: the long looping PCB trace (grey) and the short direct interposer trace (blue), with their energy bars beside them.

Step 5 — The other axis: bandwidth from parallel wires
WHY multiply, not add? Every wire is an independent lane. Total throughput is lanes × per-lane rate — the same reason a 4-lane road carries 4× the cars of a 1-lane road at the same speed.
PICTURE. The figure stacks several wires; each ticks bits at rate ; the summed arrow on the right is the total .

Step 6 — Why "pitch" decides
WHY pitch is the whole game. PCB pitch is ~; interposer pitch (chip-grade lithography, near the lithography frontier) is ~. Same edge, more wires.
PICTURE. Same fixed edge width at top; below it the fat-pitch PCB fits 4 wires, the fine-pitch interposer fits many. Count them.

This is exactly why HBM needs an interposer: its ~1024-bit bus wants thousands of fine wires no PCB can route.
Step 7 — The cost twin: yield vs die area
WHY the exponential ? Defects land randomly on the wafer. If the average number of defects on a die of area is , the chance of getting zero defects follows the Poisson rule "probability of 0 events ". No other simple law captures "one bad spot kills the whole die". See Wafer Yield and Defect Density.
PICTURE. The curve plotted; a red dot sits at (deep in the collapse), four green dots at (up on the healthy shoulder).

Step 8 — Edge & degenerate cases (never leave a gap)
- (chips touching): . Zero-length wire costs zero charging energy — the ideal 2.5D limit. Real chiplets can't touch (need microbumps), but the interposer gets close.
- (tiny die): . A dust-speck die is essentially always good — but you'd need thousands and the wiring between them explodes. The trade-off is real, not a free lunch.
- (giant die): . Yield vanishes, and you hit the reticle limit first — the monolithic path literally dead-ends. See Reticle Limit and Lithography.
- (perfect fab): for any area — if there were no defects, big dies would be fine and the yield argument disappears. So 2.5D's cost case depends on defects existing. It's the bandwidth/energy case (Steps 1–6) that stands on its own.
- (huge pitch): — no wires fit, no bandwidth. This is the PCB failure mode for HBM, exaggerated.
PICTURE. A small panel of four mini-plots showing each limit: energy→0, yield→1, yield→0, wires→0.

The one-picture summary
Everything on this page is two levers pulling in the same direction, both improved by shrinking geometry:
- Length lever → short wires → low .
- Pitch lever → fine wires → high → high .
- Area lever → small dies → high .
The interposer pulls the length and pitch levers; chiplets pull the area lever. Together they beat the monolithic die on speed, energy, and cost.

Recall Feynman retelling — say it back in plain words
A wire is a bucket you must fill with charge before the other end notices; a longer wire is a bigger bucket, so it costs more energy per bit — that's , and length is the villain. An interposer makes the wire short and thin, so it wins on energy. It also makes wires close together (fine pitch), so hundreds fit along the same edge, and bandwidth is just "wires times speed per wire," — more wires, more bandwidth, which is why HBM's 1024-bit bus can only live on an interposer. Separately, big single chips die easily because defects land at random and one is enough to ruin the whole chip: crashes as area grows, so we cut the chip into small chiplets that each survive far more often. Push every knob to its extreme and the story holds: zero length costs zero energy, zero area is always good, infinite area never works. Interposer + chiplets = faster, cheaper, and actually manufacturable.
Recall Quick self-check
Which symbol in does the interposer shrink? ::: (wire length) — and it also lowers . In , how does fine pitch help? ::: It raises , since and small fits more wires along the same edge . Why does favour chiplets? ::: Smaller per die means each exponent is small, so stays near 1 instead of collapsing. What does do to energy per bit? ::: Drives — the ideal short-wire limit.