Visual walkthrough — SRAM read - write operations
What this page does: the parent note stated two sizing rules — one for reading, one for writing. Here we build both from scratch, one picture per step, without assuming any symbol in advance, until you can see why the access transistor is squeezed between two opposite demands. Start from a single transistor acting like a resistor; end with the full read/write stability window. (Every shorthand — , , , , , — is defined the moment we first need it, below.)
This is the visual companion to SRAM read - write operations. If you have never met a CMOS inverter or MOSFET sizing (W/L), everything you need is built below.
Step 1 — A transistor is just a controllable resistor
WHY this first. Every "who wins the tug-of-war" argument on this page is really "which resistor is smaller?" So we must first agree that an on-transistor behaves like a resistor whose value depends on its size.
PICTURE.

The wider (bigger ) the transistor, the more current it passes, so the smaller its resistance. Read that sentence twice — it is the hinge of the whole page.
- ::: channel width — how wide the conducting path is (wider = stronger).
- ::: channel length — how far current must travel (longer = weaker).
- ::: on-resistance shrinks as the transistor gets wider.
Step 2 — Two resistors in series make a voltage divider
WHY this tool. During both read and write, one internal node () is pulled up by one on-transistor and down by another at the same time. That is literally a divider. The voltage divider formula is the one tool that answers "where does the middle node settle?" — so we earn it now.
PICTURE.

Read the fraction physically: if the bottom resistor is tiny, the fraction is near → node sits low. If the bottom is huge, fraction near → node sits high. The bigger resistor wins the node toward its side. Hold that.
Step 3 — The trip point: when does an inverter change its mind?
WHY we need it. The whole danger of reading is that node rises. "Rises to what, and is that dangerous?" only has meaning against a threshold. is that finish line.
PICTURE.

- Node held below ::: safe, the inverter still reads the intended bit.
- Node pushed above ::: the fed inverter flips → data changes.
Step 4 — READ: the node that must NOT rise too far
WHY. This is Step 2 applied to real transistors. M5 is (pulling toward ), M1 is (pulling to ground).
PICTURE.

To stay safe we need (Step 3). Look at the fraction: to make it small, we want small (strong pull-down) compared to . In size language — since a smaller resistance means a bigger (Step 1's mapping) — that is
- :: cell ratio — how much stronger (bigger ) the pull-down M1 is than the access M5.
- :: pull-down dominates → stays low → no read upset.
Step 5 — READ, the numbers (does the picture hold?)
WHY. A formula you can't put numbers into is a slogan. Let us verify.
PICTURE.

Take V, trip V, , :
The node meant to be "0" rises only to V — comfortably under the V finish line, so the latch never flips.
Why the cell ratio here is and not . By definition . Using Step 1's mapping "bigger ⇔ smaller ", each becomes , so the ratio inverts when rewritten in resistances:
So the pull-down is three times stronger — that is why landed so low, and why the green safety band in the figure is wide.
Step 6 — WRITE: the SAME node must now be forced DOWN
WHY. Same tool (Step 2), opposite goal. Reading feared rising; writing demands falls below .
PICTURE.

To make the fraction small (so drops), we need small vs — i.e. access stronger than pull-up:
- :: pull-up ratio — how strong the pull-up M2 is relative to the access M5; we need it below .
Where does the "–" number come from? only says "access must win by some margin." But real transistors are not perfect resistors, the trip point is not exactly , and process/temperature vary. If access were only barely stronger, would settle just below and the tiniest wobble would abort the write. To keep safely under the trip point across all corners, designers demand a comfort factor: the access transistor must be roughly – times stronger than the pull-up,
That factor is simply the safety cushion that turns the strict inequality into a reliable one. Notice the reversal: read wanted access weak (small ); write wants access strong (big ). Same transistor, opposite demands.
Step 7 — WRITE failure, the numbers (the degenerate case)
WHY. Every rule needs its failure shown, or you won't recognise it in an exam. This is the write's dark twin of Step 5.
PICTURE.

Same V, V, but a monster PMOS , access , writing :
We needed V; the strong pull-up pinned it at V. Fix: shrink the PMOS (raise ) or widen access (lower ) until the fraction drops. The red band in the figure is the forbidden zone — landed inside it.
Step 8 — The squeeze: both rules at once
WHY. This single window is the entire exam and the entire art of SRAM sizing. Everything above collapses to it.
PICTURE.

The one-picture summary

One node, , watched twice. In read it is a divider between access M5 (top) and pull-down M1 (bottom) and must stay below → pull-down wins → . In write it is a divider between access M5 (bottom) and pull-up M2 (top) and must drop below → access wins → access – pull-up. Same divider, mirrored demands, one squeezed access transistor.
Recall Feynman retelling of the whole walkthrough
Every on-transistor is just a resistor whose size sets how small the resistance is — bigger means smaller (Step 1). Whenever one resistor pulls a node up and another pulls it down, the node lands at a spot decided by their ratio — the bigger resistor drags the node toward its own side (Step 2). An inverter has a tipping voltage : cross it and it flips (Step 3). Reading: the "0" node gets tugged upward by the bit-line through access transistor M5; the pull-down M1 must be the beefier resistor so the node stays under the tipping voltage — V in our numbers, safe, and that "3-times-stronger" is the cell ratio (Steps 4–5). Make access too big and you tip it — read upset. Writing: now we want to tip it, so M5 must out-muscle the PMOS pull-up M2 and drag the node below the tip; with a monster PMOS it only fell to V and the write flopped (Steps 6–7). We insist access be – stronger than the pull-up just to keep a safety cushion. So read wants access weak, write wants access strong — the access transistor lives in a narrow window between the two, and that window is the whole story (Step 8).
Recall
- In the read divider, which resistor sits on top pulling up? ::: The access transistor M5 (bit-line side).
- In the write divider, which resistor is on top? ::: The PMOS pull-up M2.
- Why must ? ::: So the pull-down M1 (small ) dominates and keeps below during read.
- Read example with ? ::: V — safe.
- Write-fail with ? ::: V — above trip, write fails.
- Where does the – write factor come from? ::: A safety cushion turning into a reliable margin against process/temperature/trip-point variation.