Hexagons and How They Work
How Many Sides Has A Hexagon Have
A hexagon has six sides. That's the answer most people want, and it's correct. But getting here involves a bit more than just counting, especially if you're actually working with hexagonal shapes in a technical context like CAD, tiling, or geometry problems. The prefix "hex-" comes from Greek and means six. " gon" means angle or side. So hexagon = six-sided polygon. Pretty direct. In a regular hexagon, all six sides are equal length and all six interior angles measure 120 degrees. The sum of interior angles is always 720 degrees for any hexagon, regular or not, because the formula is (n-2) × 180, where n is the number of sides. That gives (6-2) × 180 = 720. Here's something most beginner geometry resources don't emphasize enough: an irregular hexagon can have wildly different side lengths and angles and still technically be a hexagon. I ran into this when a client sent me floor plans for a custom hexagonal room where the walls were all different lengths due to property line constraints. The shape still closed properly at six vertices with six edges. It wasn't equilateral, it wasn't equiangular, but it was absolutely a hexagon. Counting the sides confirmed it — six, no debate.
Another thing people miss is that you can determine the number of sides purely from the angle sum. If someone tells you the interior angles add up to 720 degrees, you can reverse-engineer that it's a hexagon without ever seeing the shape. Set (n-2) × 180 = 720, solve for n, and you get n = 6. This works for any polygon, not just hexagons, and it's faster than drawing anything out. The real gotcha with hexagons isn't counting sides. It's when people confuse hexagons with other six-vertex shapes that aren't planar or aren't closed. A star-shaped hexagram has six points but twelve sides if you count every edge. A self-intersecting hexagon still has six sides by the standard definition but behaves completely differently in calculations. If you're writing code to detect hexagons from a point cloud, you need to verify the polygon is simple (no self-intersections) and closed before you trust any area or angle computations. I learned that the hard way when my script reported a twelve-sided figure from what looked like a hexagon in a 3D scan — turns out two edges were crossing due to a coordinate ordering error. For practical purposes, whether you're doing manual drafting, programming geometric validation, or just answering a trivia question, the answer stays the same: six sides. The complexity only shows up when you need to verify one exists in the wild.
