Intuition What this page is for
The parent note taught the recipe A ^ = A /∣ A ∣ . But a recipe only sticks when you have seen it survive every kind of input you could be handed: negative components, a vector living in 3D, a vector already of length 1, a vector of length zero (the trap!), a vector so long its magnitude is ugly, a word problem dressed in physics, and an exam twist that hides the vector inside a subtraction. This page marches through all of them.
Before we start, one reminder of the two symbols you must never confuse:
A (arrow on top) = the whole vector — it has a size and a direction.
∣ A ∣ (vertical bars) = the magnitude — a single positive number, the vector's length.
A ^ (hat) = the unit vector — same direction as A , but length locked to 1 .
The recipe glues them: A ^ = ∣ A ∣ A , and its reverse A = ∣ A ∣ A ^ .
Every problem this topic can throw is one (or a blend) of these case classes:
#
Case class
What is tricky about it
Hit by
C1
All-positive 2D
The friendly baseline
Ex 1
C2
Mixed signs (a quadrant other than the first)
Signs must survive into A ^
Ex 2
C3
3D with a negative component
Pythagoras twice; sign kept
Ex 3
C4
Already a unit vector
Dividing by 1 changes nothing
Ex 4
C5
Zero vector (degenerate)
A ^ is undefined — no direction
Ex 5
C6
Ugly / irrational magnitude
Answer must stay exact, not rounded away
Ex 6
C7
Real-world word problem (units!)
Strip units to get direction, restore later
Ex 7
C8
Exam twist: vector hidden in a difference
Build the vector first , then normalise
Ex 8
C9
Limiting behaviour: one component huge
A ^ leans toward that axis
Ex 9
Each example below is tagged with the cell it fills.
Worked example Example 1 — C1: all-positive 2D
Find the unit vector of A = 6 i ^ + 8 j ^ .
Forecast: Both components are positive, so A ^ should point up-and-to-the-right, into the first quadrant. Guess: something like 0.6 i ^ + 0.8 j ^ ?
Step 1. ∣ A ∣ = 6 2 + 8 2 = 36 + 64 = 100 = 10 .
Why this step? You cannot divide out a length you have not measured. Squares-then-root because the two components are perpendicular sides of a right triangle (see figure) and only Pythagoras combines perpendicular lengths.
Step 2. A ^ = 10 6 i ^ + 8 j ^ = 0.6 i ^ + 0.8 j ^ .
Why this step? Dividing by the positive number 10 shrinks length to 1 but never rotates, so the direction is untouched.
Verify: 0. 6 2 + 0. 8 2 = 0.36 + 0.64 = 1 = 1. ✓ Both components stayed positive — still first quadrant. Forecast confirmed.
Worked example Example 2 — C2: mixed signs (third quadrant)
Find the unit vector of A = − 3 i ^ − 4 j ^ .
Forecast: Both components negative ⇒ this arrow points down-and-to-the-left (third quadrant). The magnitude cannot know that — it only cares about size. So I expect the signs to survive into A ^ .
Step 1. ∣ A ∣ = ( − 3 ) 2 + ( − 4 ) 2 = 9 + 16 = 25 = 5 .
Why this step? Squaring kills the minus signs — magnitude is always positive. This is exactly why magnitude alone can never tell you the quadrant.
Step 2. A ^ = 5 − 3 i ^ − 4 j ^ = − 0.6 i ^ − 0.8 j ^ .
Why this step? We divide the whole vector, minus signs included. Dividing by a positive number preserves the sign of each component, so the pointer still aims into the third quadrant.
Verify: ( − 0.6 ) 2 + ( − 0.8 ) 2 = 0.36 + 0.64 = 1. ✓ Compare with Ex 1: same length-1 pointer, but flipped to the opposite direction — the signs did their job.
Worked example Example 3 — C3: 3D with a negative component
Find B ^ for B = 2 i ^ − 3 j ^ + 6 k ^ .
Forecast: Three components, one negative. Magnitude uses all three squares, so I expect a whole number if I'm lucky (2 , 3 , 6 smell like a Pythagorean triple). B ^ should keep the minus on j ^ .
Step 1. ∣ B ∣ = 2 2 + ( − 3 ) 2 + 6 2 = 4 + 9 + 36 = 49 = 7 .
Why this step? In 3D we apply Pythagoras twice — first across the base (x , y ), then up to z — which collapses to one square root of the sum of all three squares. Signs vanish under squaring, so − 3 contributes + 9 .
Step 2. B ^ = 7 2 i ^ − 3 j ^ + 6 k ^ = 7 2 i ^ − 7 3 j ^ + 7 6 k ^ .
Why this step? Same recipe as 2D; the third axis changes nothing about how we normalise.
Verify: ( 7 2 ) 2 + ( 7 3 ) 2 + ( 7 6 ) 2 = 49 4 + 9 + 36 = 49 49 = 1. ✓ The minus survived on j ^ — direction intact.
Worked example Example 4 — C4: already a unit vector
Normalise C = 2 1 i ^ + 2 1 j ^ .
Forecast: These components look suspiciously clean. If C is already length 1 , then dividing by its magnitude (= 1 ) should hand it straight back — a "do-nothing" operation.
Step 1. ∣ C ∣ = ( 2 1 ) 2 + ( 2 1 ) 2 = 2 1 + 2 1 = 1 = 1 .
Why this step? Always measure first. Here the measurement reveals we were already at unit length.
Step 2. C ^ = 1 C = 2 1 i ^ + 2 1 j ^ (unchanged).
Why this step? Dividing by 1 is the identity operation — no shrink, no stretch, no rotation.
Verify: Same vector out as in, and its length is 1. ✓ Lesson: normalising a unit vector is a no-op, which is a good sanity check that your recipe is self-consistent.
Worked example Example 5 — C5: the zero vector (degenerate case)
Try to find the unit vector of 0 = 0 i ^ + 0 j ^ + 0 k ^ .
Forecast: A vector of length 0 has no direction — it's a single point, an arrow with no shaft. There is nothing to "point" at. So I predict the recipe breaks.
Step 1. ∣ 0 ∣ = 0 2 + 0 2 + 0 2 = 0 .
Why this step? Measure the length as always — and it comes out zero.
Step 2. 0 ^ = 0 0 = 0 0 i ^ + 0 j ^ + 0 k ^ ⇒ undefined .
Why this step? Division by zero is undefined. Geometrically: to build a pointer you must shrink a real arrow, but a zero-length arrow has no way to say which way . There is no unit vector of the zero vector.
Verify: No arithmetic to plug back — the check is conceptual: any candidate 0 ^ would need magnitude 1 , but 0 ^ = 0 /0 produces 0/0 , which is meaningless. ✓ (This is the one case you must guard against in code and on exams.)
Common mistake "Set the zero vector's unit vector to
i ^ or to 0 ."
Why it feels right: You want some answer, so you default to an axis or to zero.
The fix: Both are wrong. i ^ has magnitude 1 but invents a direction the zero vector never had; 0 has magnitude 0 = 1 so it isn't a unit vector at all. The honest answer is undefined .
Worked example Example 6 — C6: ugly / irrational magnitude
Find the unit vector of D = 2 i ^ + 3 j ^ .
Forecast: 4 + 9 = 13 is not a whole number, so the answer will carry a 13 in the denominator. Do not round — keep it exact.
Step 1. ∣ D ∣ = 2 2 + 3 2 = 4 + 9 = 13 .
Why this step? Not every problem gives a clean triple. 13 ≈ 3.606 , but we keep the exact surd so no precision is lost.
Step 2. D ^ = 13 2 i ^ + 3 j ^ = 13 2 i ^ + 13 3 j ^ .
Why this step? Same division; the denominator just happens to be irrational. You may rationalise to 13 2 13 i ^ + 13 3 13 j ^ — same value.
Verify: ( 13 2 ) 2 + ( 13 3 ) 2 = 13 4 + 13 9 = 13 13 = 1. ✓ Exact form paid off — the 13 s cancel perfectly.
Worked example Example 7 — C7: real-world word problem (units matter)
A velocity is v = 30 i ^ + 40 j ^ measured in m/s . A drone is told to fly at 100 m/s in the same direction . Find the drone's velocity vector.
Forecast: "Same direction" screams unit vector — strip v 's length to get the pure pointer, then re-stretch by 100 . Since 30 , 40 scales to 3 , 4 , 5 , expect a tidy answer.
Step 1. ∣ v ∣ = 3 0 2 + 4 0 2 = 900 + 1600 = 2500 = 50 m/s .
Why this step? We only care about v 's direction , so we must first know its size in order to divide it out. Units (m/s ) ride along on the magnitude.
Step 2. v ^ = 50 30 i ^ + 40 j ^ = 0.6 i ^ + 0.8 j ^ (dimensionless).
Why this step? Dividing m/s by m/s cancels the units — a unit vector is dimensionless , pure direction. This matches the parent note's "a unit vector has no units" point.
Step 3. v drone = ( 100 m/s ) v ^ = 60 i ^ + 80 j ^ m/s .
Why this step? Vector = magnitude × direction. The 100 m/s supplies the new size and re-attaches the units.
Verify: ∣ v drone ∣ = 6 0 2 + 8 0 2 = 3600 + 6400 = 10000 = 100 m/s . ✓ Right speed, and v ^ unchanged ⇒ right direction.
Worked example Example 8 — C8: exam twist — vector hidden in a difference
Points P = ( 1 , 2 , 2 ) and Q = ( 4 , 6 , 2 ) . Find the unit vector pointing from P to Q .
Forecast: The vector isn't handed to me — I must build it as Q − P first (this is the displacement). Only then do I normalise. If I forget the subtraction I'll normalise the wrong thing.
Step 1. P Q = Q − P = ( 4 − 1 ) i ^ + ( 6 − 2 ) j ^ + ( 2 − 2 ) k ^ = 3 i ^ + 4 j ^ + 0 k ^ .
Why this step? A direction "from P to Q " is the displacement Q − P — head minus tail. See Position vector and displacement . Note the k ^ -component is 0 : the two points share the same height, so the displacement lies flat in a plane.
Step 2. ∣ P Q ∣ = 3 2 + 4 2 + 0 2 = 9 + 16 + 0 = 25 = 5 .
Why this step? A zero component contributes nothing to the length — but you still include it so the recipe stays uniform.
Step 3. P Q = 5 3 i ^ + 4 j ^ + 0 k ^ = 0.6 i ^ + 0.8 j ^ .
Why this step? Same normalisation. The 0 k ^ simply drops out.
Verify: 0. 6 2 + 0. 8 2 + 0 2 = 1 = 1. ✓ Sanity check the direction : Q is to the right and above P , and indeed both non-zero components are positive.
Worked example Example 9 — C9: limiting behaviour — one component dominates
Compare the unit vectors of E 1 = 10 i ^ + 1 j ^ and E 2 = 1000 i ^ + 1 j ^ . What happens as the x -component grows without bound?
Forecast: As x dwarfs y , the arrow lies almost flat along + x , so E ^ should approach i ^ itself. I expect the i ^ -coefficient → 1 and the j ^ -coefficient → 0 .
Step 1. For E 1 : ∣ E 1 ∣ = 1 0 2 + 1 2 = 101 ≈ 10.0499 , so
E ^ 1 = 101 10 i ^ + 1 j ^ ≈ 0.9950 i ^ + 0.0995 j ^ .
Why this step? Just the recipe; keep enough decimals to see the trend.
Step 2. For E 2 : ∣ E 2 ∣ = 100 0 2 + 1 2 = 1000001 ≈ 1000.0005 , so
E ^ 2 ≈ 0.9999995 i ^ + 0.0009999995 j ^ .
Why this step? The bigger x gets, the more the i ^ -coefficient hugs 1 and the j ^ -coefficient shrinks toward 0 .
Step 3 (the limit). As the x -component → ∞ with y fixed, x 2 + 1 x → 1 and x 2 + 1 1 → 0 , hence E ^ → i ^ .
Why this step? This shows i ^ is the limiting pointer of any vector that leans ever more toward the x -axis — the standard basis vectors are the extreme cases of normalisation.
Verify: 0.995 0 2 + 0.099 5 2 = 0.99005 + 0.00990 ≈ 1.000 (rounding), and exactly 101 1 0 2 + 1 2 = 101 101 = 1. ✓
Recall Quick self-test across the matrix
Cover the answers and name the trap in each.
Which case gives an undefined unit vector, and why? ::: The zero vector (C5) — magnitude 0 forces division by zero, and a zero-length arrow has no direction.
Normalising an already-unit vector gives what? ::: The same vector back (C4) — dividing by 1 is a no-op.
When you're asked for the direction "from P to Q ", what must you build first? ::: The displacement P Q = Q − P (C8), then normalise.
As one component grows without bound, the unit vector approaches what? ::: The basis vector of that axis (C9), e.g. i ^ .
Do negative components survive into A ^ ? ::: Yes — dividing by the positive magnitude keeps every sign (C2/C3).
Mnemonic The one-line strategy for any scenario
"Build it, measure it, divide it — unless the length is zero."
Build the vector (C8), measure its length via Pythagoras (all cases), divide to normalise — and if the length is 0 , stop: there is no answer (C5).