A binary tree limits each node to at most two children, usually named left and right. A general tree lets a node have any number of children, with no fixed slots.
That cap sounds small but changes how you store and walk the structure. Each node needs just two child pointers, and left versus right becomes meaningful, not just a set of children. This ordering is what later lets binary search trees and heaps assign meaning to sides.
An empty spot matters too: a node can have a left child but no right, and that gap is part of the shape. General trees suit data with variable fan-out, like a folder holding any number of files. Binary trees suit ordered decisions, where each step picks one of two directions. Most fast lookup and priority structures build on the binary form for that reason.
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The interactive diagram is below the answer - jump to diagram ↓ · Below it, the related concept . Jump to it ↓
The diagram below the answer is the concept . Jump to it ↓