Visual walkthrough — Multiplexers (2 - 1, 4 - 1, n - 1)
We use a few symbols. Before any appear, here is the whole cast in plain words:
Step 1 — The physical picture: a knob choosing one pipe
WHAT. Draw four water pipes feeding into one tap. A dial with a pointer selects which pipe's water reaches the single spout.
WHY start here. Every symbol below is a translation of this picture into electricity. If you can see the tap, you never lose the meaning of the algebra. "Multiplex" literally means many into one line — this drawing is that phrase.
PICTURE. The dial position (a number) chooses the pipe. The spout ignores every other pipe completely.

Step 2 — Two pipes only: the 2:1 MUX, in pictures
WHAT. Shrink to the smallest interesting case: two data inputs and , and one select bit . When we want ; when we want .
WHY the smallest case first. Everything bigger is copies of this. If you understand one select bit steering between two inputs, the 4:1 and n:1 are just "more of the same."
PICTURE. Two gates, like two doors. We need each door to open only in its own case.

The question the algebra must answer: "how do I write a switch that is ON only when ?" That is exactly what is for.
Step 3 — Turning "when " into algebra: why we need
WHAT. We want a term that is precisely when , so it can "wave through" then. And a term that is precisely when , to wave through .
WHY and not something fancier. itself is when — that is our gate. But for we need the opposite on-condition. The one operation that flips a bit is NOT, written . It is the smallest tool that answers "am I in the world?" — so we use it, nothing heavier.
PICTURE. Watch the two gates open in opposite halves of the knob.

Now assemble the sentence. "Pass when " is . "Pass when " is . Either one may be the winner, so we join them with OR ():
Term-by-term: is " if we are in the world, else ." is " if we are in the world, else ." The says "output whichever half is active." Because and are never both , only one half is ever nonzero — the promise from Step 1 is kept.
Let us check both cases exhaustively (only two exist):
Step 4 — Two select bits build four "pointers": the minterm idea
WHAT. With two select bits (the high bit, MSB) and (the low bit), the knob has positions: . Each spells a number . We need one algebra-term that is for each position and everywhere else.
WHY. In Step 3 the "on-when-" gate was . Now each of four positions needs its own on-gate. The gate for position "both bits as written" is the AND of each bit in its right flavour (barred if that bit is , plain if ). That special product is a minterm.
PICTURE. A four-slot dial; each slot lights exactly one minterm lamp.

Read the lamps:
| number | minterm (its on-gate) | why barred/plain | ||
|---|---|---|---|---|
| 0 | 0 | 0 | both bits are → bar both | |
| 0 | 1 | 1 | bar it, plain | |
| 1 | 0 | 2 | plain, bar it | |
| 1 | 1 | 3 | both → plain both |
Step 5 — Assemble the 4:1 MUX: gate each pipe with its pointer
WHAT. Give each input its own minterm as an on-gate, then OR everything.
WHY. Same sentence as the 2:1, just four clauses: " if we're in position 0, or if position 1, or …". Each clause is ; only one clause is ever nonzero (Step 4), so exactly one pipe reaches .
PICTURE. Four AND gates fanning into one OR gate — the shape of every MUX.

Term-by-term: each brace is a pointer (a minterm) that is only for its own knob setting; the next to it is the pipe it lets through; the signs OR the four clauses, but since only one pointer fires, only one pipe survives.
Step 6 — The pattern that scales: the general n:1 MUX
WHAT. For select bits there are knob positions and inputs. Every position has its own minterm; gate each input with it and OR them.
WHY. Nothing new — Steps 3–5 already are the pattern. We just write it compactly with a summation sign , which means "add all these clauses."
PICTURE. The universal AND-array → OR shape, drawn for general .

Term-by-term: says "OR together one clause for every address from to ." is the fingerprint that fires only when the knob spells . is the pipe at that address. This block of minterms is exactly what a decoder produces — a MUX is a decoder feeding an OR gate.
And the count of select lines, since bits address inputs, inverts to:
Step 7 — The degenerate and edge cases (never leave a gap)
WHAT. Push the formula to its extremes so no reader hits an unshown scenario.
WHY. A derivation you can trust must survive its own boundaries.
PICTURE. Three tiny corner cases side by side.

The one-picture summary
Every step collapses into a single claim: a MUX is minterms (a decoder) choosing pipes, ORed at one spout. The picture below packs the whole derivation — knob → minterm fingerprints → AND-gate pipes → single OR → .

Recall Feynman retelling — the whole walkthrough in plain words
Imagine a water tap over four pipes with a dial. We wanted to write that tap in the language of s and s. First we did the tiny two-pipe tap: we needed a switch that's ON only when the dial says , so we invented ("not "), and the switch for the dial-says- side is just . Each switch waves its own pipe through, and we say "either one" with a (OR): . Then for four pipes the dial has two bits; for each of the four positions we made a fingerprint — a minterm — that lights up for exactly one position by barring the bits that are and leaving the s plain. We paired every fingerprint with its pipe and ORed them all. Because only one fingerprint ever lights, only one pipe ever comes out — the tap's promise is kept. Writing "add a clause for every address" with a gives the general formula, and it survives all the corners: no selects means a plain wire, all-equal inputs means a constant, and an enable bit can shush the whole thing by multiplying everything by zero.
Connections
- Multiplexers (2 - 1, 4 - 1, n - 1) — the parent topic these pictures derive.
- Decoders — the minterm/fingerprint generator living inside every MUX.
- Demultiplexers — the mirror image: one pipe, many spouts.
- Boolean Algebra Minterms — the fingerprints of Step 4.
- Shannon Expansion — factoring a variable out to shrink onto a smaller MUX.
- Tri-state Buffers — how enable becomes high-Z on a shared bus.
- Combinational Logic Design — the MUX as a universal function block.