Before You Start Drawing Branches
The way most people approach Greek divine genealogy is completely wrong. They treat it like a biology worksheet. It isn't. The sources contradict each other constantly, and a lot of what looks like a clean family tree is actually later scholars trying to impose order on material that was never organized that way in antiquity. If you want a working map, you need to understand what you're actually looking at before you commit anything to paper. I spent years compiling these relationships for a reference project and learned the hard way that no single source is authoritative across all pantheons. Hesiod gives you one version. Homer gives you another. Local cults had their own additions. The result is a mess if you don't know how to navigate it.
The Genealogical Tree Of Greek Gods Mapping The Divine Family Drama Of Olympus
Let me get the foundations out of the way first, because everything builds from here. The traditional starting point is Chaos — not emptiness in the modern sense, but a gaping void from which the first entities emerge. From Chaos come Erebus and Nyx (Darkness and Night). Nyx then produces Aither and Hemera, which is already a slight problem because some versions reverse the parentage. You'll see both on the internet. Take your pick and note it. From Chaos also comes Gaia (Earth), who then gives birth to Ouranos (Sky) without any partner. She also produces Pontos (Sea) and the Ourea (Mountain spirits). Gaia and Ouranos then combine to produce the Titans, the Cyclopes, and the Hecatoncheires. The Titans number twelve: Oceanus, Coeus, Crius, Hyperion, Iapetus, Theia, Rhea, Themis, Mnemosyne, Phoebe, Tethys, and Cronus. Cronus overthrows Ouranos and marries Rhea. Their children are the original Olympians: Hestia, Demeter, Hera, Hades, Poseidon, and Zeus. Zeus then overthrows Cronus. After that, things get complicated fast. Zeus has children with multiple partners — Metis produced Athena, Leto produced Apollo and Artemis, Demeter produced Persephone, Maia produced Hermes, and so on. Hera produces Hephaestus solo in most versions, though some say Prometheus made him. This is where your map needs branching notation because we're dealing with half-divine offspring, second-generation deities, and minor figures that don't fit neat categories.
How I Actually Map These Relationships
When I build these trees, I use a layered approach. The first pass is chronological by generation — Chaos, Protogenoi, Titans, Olympians, then the hybrid generation. The second pass is by domain and function. The third pass notes which source each relationship comes from. That third pass is the one people skip and regret later. Here's a practical example. If you're mapping the lineage of Dionysus, you'll find two competing versions. In one, he's the son of Zeus and Semele. In another, he's the son of Zeus and Persephone, making him a chthonic deity rather than an Olympian one. Both are cited in ancient texts. A simple tree collapses this into a single branch and loses important theological information. I use split nodes with source tags to handle this without cluttering the main structure. For the minor deities, I usually create a separate appendix layer. Characters like the Graces, Horae, Charites, Muses, and the many nymphs and river gods generate pages of names that have no place in a readable overview tree. Put them on a secondary chart and link them, or you'll end up with something unreadable.
Get the Full Details
The Edge Case That Broke My First Draft
The first time I tried to fully map this, I ran into a problem with Persephone's parentage that took me three days to resolve. Most standard charts list Zeus and Demeter as her parents. But in some Orphic traditions, she's born from Cronus's union with Nyx, or sometimes from Zeus and Hemera. More confusingly, she's occasionally identified with Persephone-Aidoia, a chthonic figure who gets conflated with Hecate and Demeter in certain cult contexts. My workaround was to create three distinct tiers on the same chart. The primary tier shows the standard Hesiodic-Olympian lineage. The secondary tier, in a different color, shows the Orphic and regional variations. The tertiary tier uses bracket notation for figures whose parentage is genuinely disputed even among ancient authors. This took about forty-five minutes to set up in my diagramming tool but saved me from publishing an inaccurate map that would've needed rewriting later. If you're working digitally, I recommend using a tool that supports nested annotations rather than just lines and boxes. The relationships here are too messy for a flat diagram.
Common Pitfalls That Will Mess Up Your Map
The biggest mistake beginners make is assuming that sibling relationships imply full biological siblings. Many of the "children" of Zeus and Hera are symbolic unions rather than literal ones. Aphrodite, for instance, is born from Ouranos's severed genitals in Hesiod but from Zeus and Dione in the Iliad. These aren't errors in the sources — they're competing theological frameworks. Your map should reflect that, not pick one and pretend the other doesn't exist. Another trap is the assumption that the Titans are a monolithic group. They're not. Some are benevolent (Oceanus, who didn't fight Zeus; Mnemosyne, who became the mother of the Muses). Some are hostile. Some are ambiguous. Grouping them all as "the bad guys who got overthrown" is a later Roman-influenced simplification that obscures more than it clarifies. You'll also run into issues with identification. The Greeks frequently syncretized deities from other cultures. Is Isis the same as Demeter in a given context? Sometimes yes, sometimes no. Egyptian gods in Greek sources get pulled into these trees whether they belong there or not. Mark your imports separately or you'll confuse your readers.
What This Approach Can't Do
A genealogical tree has real limits when applied to Greek mythology. First, it flattens temporal inconsistencies. Many gods appear simultaneously across different myth cycles with no clear chronological ordering. Second, it implies biological certainty where ancient authors were deliberately ambiguous. Third, it privileges the Olympian lineage over local and mystery-cult traditions that don't fit the family model at all. Initiates of the Eleusinian Mysteries, for example, weren't interested in whether Demeter and Persephone were mother and daughter in a genealogical sense — they were focused on the cyclical nature of life and death, which a tree diagram cannot represent. If you need to show religious or theological relationships rather than genealogical ones, a different visualization is better. A network graph or a domain-based hierarchy will serve you more accurately than a family tree. I've switched to using network diagrams for projects that emphasize cult practice over lineage.
Working With the Material Long-Term
The most useful reference I've found for cross-checking relationships is the Oxford Classical Dictionary combined with the Loeb editions of Hesiod and the Homeric Hymns. Online databases are convenient but often inherit each other's errors without citing sources. When I found a discrepancy in an online tree about the parentage of the Erinyes, I traced it back through three different websites and found they all copied a single secondary source that had misread a passage from Aeschylus. For building your own map, I'd suggest starting with a small subset — maybe the direct Olympian generation and their immediate children — before expanding outward. The tree grows exponentially and it's easy to get lost in the minor figures. The major relationships are well-attested. The rest gets fuzzy fast. There's also a difference between mapping the gods for academic purposes and mapping them for creative work. If you're writing fiction or designing a game, you can simplify aggressively and note where you've diverged from the sources. If you're building a reference, accuracy matters more than readability. Know which one you're doing before you start.
