Naming Islands on Fantasy Maps: A Consistency Guide

A single striking island name is easy. A whole map of them that feels like one world is much harder, and it is where most homebrew settings quietly fall apart. The problem is rarely that any one name is bad; it is that "Cliffhaven," "Tzun'Marai," and "Old Otter Rock" are sitting next to each other on the same chart with nothing explaining why. This guide is about the discipline behind a chain of islands that reads as charted geography rather than a list of separate word-generator runs, and it pairs well with our 150+ island name ideas if you want ready-made names to test the patterns on.

Start from who named the place, not what sounds cool

Every real-world place name was assigned by somebody: a fisherman, a surveyor, a conquering navy, a monastery. That somebody spoke one language, cared about a narrow set of things, and named accordingly. Before generating a single island, decide who is doing the naming for this stretch of water. A fishing culture names for hazards and landmarks a boat can see from the water: shoals, rocks, the shape of a headland. A colonizing navy names for its own kings, saints, and home ports. A single ancient culture that settled the whole archipelago at once names everything from one root language and one set of gods or ancestors. Pick the namer first, and the vocabulary follows almost by itself.

One naming language per culture, not per island

The single most common mistake on a homemade map is variety for its own sake: every island gets a name from a different invented language because the mapmaker got bored of the last one. Readers notice this even when they cannot name what is wrong. The fix is to treat each culture that has ever controlled a stretch of water as one naming language with a small, consistent toolkit: a handful of stems, a handful of suffixes, and rules for how they combine. Our own generator's Nordic style is a working example: it fuses stems like Ravn- (raven) or Ulv- (wolf) to suffixes like -holm, -ey, and -vik, and nothing else. If a second culture later settles or conquers part of the chain, that is when a second naming language should appear, and it should appear as a visible seam on the map, not as random noise spread evenly across it.

This also means resisting the urge to make every name maximally unique. Real charts repeat themselves constantly: multiple "Sandy Cay"s, multiple "Isle of Saint Anne"s in different countries, three "Ravnholm"s within one language's range because ravens are common and the naming pattern is simple. A little repetition, especially of generic descriptive terms, is a signal of authenticity, not a failure of imagination.

Geographic descriptors should describe something real

Every naming language on a real map has a small set of geographic terms, and each one is load-bearing: it tells the reader, or the sailor, what kind of place this is. Atoll means a ring of coral around a lagoon. Cay and key mean a low sandy islet sitting on a reef. Skerry means a small bare rock, often barely above the waves. Holm is Old Norse for a small island, distinct from the larger -ey or -oy islands nearby. When you invent a fantasy descriptor of your own, give it the same discipline: decide exactly what physical feature it marks, and use it only for that feature, every time. A map where "shard" always means a narrow volcanic spire and "mere" always means a low island with standing fresh water will feel surveyed. A map where the same words are decorative and interchangeable will not.

Directional and size prefixes do similar work with almost no invention required. North, South, Upper, Lower, Great, and Little are how real charts split a cluster of related islands that share a base name: North Pelham Key and South Pelham Key are obviously part of one family, and a reader absorbs that relationship instantly without a caption. Reuse this pattern freely; it costs nothing and buys a lot of implied geography.

Chains want a shape, not just a list

An archipelago is not a bag of unrelated dots; it usually has a structure the naming can reflect. A volcanic chain is often ordered from oldest and most eroded to youngest and most active, and a naming scheme that gets progressively more ominous toward one end (Ashfall Isle, then Emberreach, then The Weeping Vent) quietly tells that story without a paragraph of exposition. A reef chain built around one large lagoon often has a "mother" island with a proper name and a scatter of minor cays named for what a passing sailor would notice about each one: Sunmirror Cay, Palmwater Isle, Tidebloom Cay. A haunted or cursed chain benefits from a shared grammar of dread, the "Isle of (abstract noun)" pattern our own cursed-style list leans on, so that even an island named for the first time in play feels native to the set.

Deciding the chain's shape before naming individual islands also solves a practical problem: it tells you how many "big, important" names you actually need versus how many can be minor, descriptive, and forgettable on purpose. Not every island on a hundred-island chain needs a name a player will remember. Most need exactly enough of a name to exist on a map without drawing attention away from the three or four that matter.

Writing the legend: what actually belongs in a map key

A map legend for islands should do less than most worldbuilders think. It does not need to explain the naming language in-world; that belongs in lore notes, not the corner of a map. What it needs is a small, readable key to the geographic terms you invented, exactly the way a real nautical chart glosses "shoal" or "bank" for readers who might not know: one line per term, in plain language, so a player glancing at the map understands why "Grimwrack Shoals" is dangerous water and "Grimwrack Isle" would not have been. If your world uses two naming languages in the same region, a legend can also mark which culture's names are which, either with a simple color code or a footnote, so the seam between them reads as intentional history instead of an inconsistency.

Keep the legend's own language plain and consistent with everything else on the page. A map that uses "atoll" precisely in its legend and then calls a random skerry an atoll in the flavor text has undermined its own key. Consistency is the entire point of this exercise, and it has to hold at every layer, from the individual name to the descriptor behind it to the sentence describing it in your notes.

A short worked example

Say your setting has one archipelago settled by a single seafaring culture that reveres storms and iron. Decide their naming toolkit first: stems drawn from weather and metal (Storm-, Iron-, Frost-, Thunder-), fused to two or three geographic suffixes that mean specific things (-reach for an open channel, -hold for a settled, sheltered island, -spire for a sharp volcanic peak). Now the chain names itself with almost no further invention: Stormreach for the main shipping channel, Ironhold for the main settlement, Frostspire for the dangerous volcanic outlier at the chain's edge. Every name shares the same two or three roots and the same small set of endings, every ending still means exactly one thing, and a reader who sees a fourth island called "Thunderhold" already knows, correctly, that it is another settled, sheltered place belonging to the same people. That is the whole method: pick the namer, pick their toolkit, and apply it with more discipline than feels necessary. The discipline is what a reader experiences as a real, lived-in world.