The End of the Chain: null
What you'll learn: Where the prototype chain ultimately ends and what marks its final boundary.
The Ultimate Ancestor
You've seen how JavaScript objects link together through prototypes, forming a chain. But every chain must end somewhere. In JavaScript, the prototype chain terminates at Object.prototype, and its prototype is null.
Think of it like a family tree: you trace your ancestors back through parents, grandparents, great-grandparents... but eventually you reach the beginning of recorded history. There's no one "before" that point. In JavaScript's world, null is that absolute endpoint—it represents the deliberate absence of any object.
Why This Matters
When JavaScript looks for a property, it walks up the prototype chain. It checks the object, then its prototype, then that prototype's prototype, and so on. But it can't search forever. When it reaches Object.prototype and still hasn't found the property, it checks one more time: "What's your prototype?" The answer is null, which signals: "Stop searching. There's nothing beyond here."
const obj = {};
console.log(Object.getPrototypeOf(obj));
// [Object: null prototype] {} (Object.prototype)
console.log(Object.getPrototypeOf(Object.prototype));
// null — the chain ends here
This null value is intentional and fundamental. It prevents infinite loops and defines the boundary of inheritance.
Key Takeaway: The prototype chain always ends at Object.prototype, whose prototype is null, marking the absolute end of property lookup and preventing endless searching.