Foundations — The Jacobian matrix
Why this page exists
The parent note throws a lot of notation at you very fast: , , , , , . If any one of those symbols is a fog to you, the whole topic collapses. So below we take every symbol the parent uses and give it three things: a plain-words meaning, a picture, and the reason the topic needs it. Read top to bottom — each block is a rung you stand on to reach the next.
1. A number line, and what means
The picture: a horizontal line stretching left and right forever, with in the middle. A single real number is one dot sitting on that line.
Why the topic needs it: every input and every output in the Jacobian story is built out of real numbers. Before we can stack numbers into vectors we must name the pool they come from.
2. Vectors and the spaces
- : one number, one dot on a line.
- : two numbers , a point (or arrow) on a flat sheet.
- : three numbers, a point in the room you are sitting in.
We write such a list as a vector and put it in bold: . Its individual numbers are the components — same letter, subscript for the slot.

The picture (figure above): a vector is an arrow from the origin to a point. In the arrow points 3 right and 2 up. The word "vector" and the word "point" describe the same list of numbers — one emphasises the arrow, one emphasises the tip.
Why the topic needs it: the Jacobian describes machines that take a vector in and give a vector out. Without the idea of there is nothing to be multi-dimensional about.
3. A function between vector spaces:
The output is itself a list, so is really ordinary scalar functions bundled together:
Each is one output component — a single dial-reading of the output — and it is allowed to depend on all the inputs.

The picture (figure above): a box with input dials on the left and output bulbs on the right. Every dial may wire to every bulb. That web of wires is exactly what the Jacobian will measure.
Why the topic needs it: this is the object the Jacobian is about. The whole note answers "how does this box respond when I nudge the dials?"
4. Slope of one variable: the ordinary derivative
The picture: zoom into the curve until it looks like a straight line. Its steepness is . A big means a steep climb; a negative means going downhill; means flat.
Why we use a slope at all (WHY this tool): the derivative answers the question "if I nudge by a tiny amount , how much does change?" The answer is . This single fact — change slope nudge — is the seed the entire Jacobian grows from. We pick the derivative and not, say, the average value, because we care about local response to a small push, which is precisely what a slope encodes.
5. Many inputs, one output: partial derivatives
Now let one output depend on several inputs. If I want its slope, I face a puzzle: slope in which direction? Wiggling is a different push than wiggling .

The picture (figure above): the graph of is a landscape — a hilly surface over the flat floor. is the slope you feel walking due east (only changes). is the slope walking due north. Same spot, two different steepnesses, because a hill can be flat one way and steep another.
Why the topic needs it: every single entry of the Jacobian is one partial derivative — output , nudged by input . Partials are the atoms the table is built from.
6. Bundling the partials of one output: the gradient
For output there are partials — one per input. Collect them into a single list.
The picture: back on the hill of §5, the gradient is an arrow drawn on the flat floor pointing in the steepest-uphill direction, and its length is how steep that is. It packs "east-slope" and "north-slope" into one arrow.
Why the topic needs it: the parent says "row of the Jacobian is ." So one gradient, tipped on its side, becomes one row of the table. Stack of them and you have the whole Jacobian. See the deeper note Gradient and directional derivative for the "steepest ascent" story.
7. Weighted sums as a dot product
When we nudge all inputs at once by a small step , the change in is the sum of each partial times its own nudge:
So the messy sum above is exactly the tidy dot product — the row-gradient of output dotted with the nudge.
Why the topic needs it: this is the single algebra move (Step 2 of the parent's derivation) that turns "a weighted sum of nudges" into "a row times a vector." Recognising it is what lets separate sums collapse into one clean matrix equation.
8. Stacking rows into a matrix, and multiplying by a vector
The picture: the inner numbers and touch and cancel; the outer numbers and survive as the shape of the answer. If the inner numbers don't match, the multiplication is illegal.
Why the topic needs it: the master formula is a matrix–vector product. It also powers the composition rule that becomes Backpropagation and Jacobian–vector products.
9. Two square-matrix extras: and
The picture: the unit square gets pushed into a parallelogram; is that parallelogram's area. If , the square collapses to a line — the map squashes a dimension flat.
Why the topic needs it: the parent's polar example uses as the area-scaling factor — the whole reason shows up in integration.
10. The prerequisite map
Read it as: number line feeds vectors, vectors plus derivatives feed partials, partials bundle into gradients, gradients-as-rows dot the nudge, and matrix multiplication ties it all into the Jacobian.
11. Where each piece reappears later
- Gradients and their "steepest direction" meaning → Gradient and directional derivative.
- Multiplying Jacobians in the right order → The chain rule (multivariable) and Backpropagation.
- The linear-map view → Linear approximation and Taylor series.
- Second-order slopes (a matrix of partials of a gradient) → Hessian matrix.
- as an area factor → Change of variables in integration.
- Cheap " times a direction" without forming → Jacobian-vector products (forward-mode autodiff).
Equipment checklist
Test yourself — cover the right side and see if you can answer each before revealing.