7 River Mistakes That Break Your Fantasy Map (And How to Fix Them)

Your coastline is gorgeous. The mountains have real weight to them. You spent an hour on the lettering.

Then somebody looks at the map for about four seconds and says: “why does that river fork?”

Rivers are the single most common way a fantasy map gives itself away. Not because mapmakers are careless, but because rivers are the one feature on the page that obeys physics visibly. A coastline can be almost any shape and still look plausible, and mountains can sit wherever the story needs them. Water has exactly one rule, and everybody who has ever watched rain run down a window already knows it.

Here are the seven errors that show up most often, why people notice them even when they can’t explain why, and how to fix each one.

Why rivers give you away

Your brain has been quietly cataloguing how water behaves since you were about two years old. You have watched puddles drain, streams merge, rain find the gutter. You never studied hydrology, but you absorbed it anyway.

So when a river on a map does something water doesn’t do, most readers don’t think “that violates the principle of gravitational flow.” They just get a small itch that something is off, and the world feels a little more like a drawing and a little less like a place. Cartographers have written about this for years. K. M. Alexander’s much-shared essay We Need to Talk About Your Rivers exists precisely because the mistake is so widespread, and Map Effects catalogues the same sins for working artists.

The good news: every one of these is a two-minute fix.

Mistake 1: The splitting river

The classic. A river runs inland, then splits into two branches that go off in different directions, like a road junction.

Water doesn’t do this. Rivers converge as they travel. Small streams feed into bigger ones, which feed into bigger ones still. A river system looks like a tree with the trunk at the sea, not like a delivery route.

The exceptions are real, but they are specific. A delta at the river’s mouth genuinely does fan out into several channels, because the land has flattened and the river drops its sediment and wanders. Braided rivers split and rejoin across wide gravel flats. And there is one famous genuine bifurcation on Earth, the Casiquiare in Venezuela, which links the Orinoco and the Amazon across terrain so flat the water can’t decide.

That’s the point, though. They’re notable because they’re rare. If your map has three of them in the first continent, the reader reads it as a mistake, not as exotic geography.

To fix it, flip the junction. Whatever you drew as a split, redraw as two streams joining into one thicker river. Save the fanning-out for where the river actually meets the sea.

Mistake 2: The river that connects two seas

You’ve drawn a channel running clean across the continent, linking the Western Ocean to the Eastern Sea. It looks fantastic. It gives your merchant fleet somewhere to go.

It also can’t be a river.

Rivers flow downhill. Both oceans sit at sea level, the same level, by definition. There’s no gradient, so there’s no direction for the water to go. A river needs a high end and a low end.

The fix is to decide what you actually want and name it correctly. If you want ships to pass through, you want a strait: a channel of salt water with sea on both ends, tides, and currents that reverse. Draw it as ocean cutting through land rather than as a river line. If you want it to feel engineered, you want a canal, which means locks, an owner, a toll, and a very good story about who paid for it. That’s a plot hook, not a mistake. And if you just want a big river, pick one ocean and let it drain there.

Mistake 3: The river that starts nowhere

A river appears in the middle of a plain and heads for the coast. No mountains behind it, no hills, no lake. It simply begins.

Rivers start where water collects and has somewhere to fall from: mountains, plateaus, high moorland, glaciers, big springs fed by upland rain. Rain lands on high ground, gathers, and runs down. That’s the whole mechanism.

Trace every river backwards from the sea. Each one should end up somewhere higher than where it started on your page, whether that’s a range, a ridge, a highland, or a lake that itself sits above the coast. If a river’s headwaters are in featureless flatland, either put some relief behind it or delete it.

Watch the related version of this error too. A river that crosses a mountain range on its way to the sea is doing the same impossible thing. Water gaps do exist, and the Delaware Water Gap is one, where a river was already there when the mountains rose and cut down as fast as they lifted. But a river casually hopping over a range is the same red flag as one flowing uphill, because that’s what it’s doing.

Mistake 4: Tributaries joining at the wrong angle

This one is subtle and it’s everywhere. The tributary meets the main river at a right angle, or worse, angles backwards, so the junction points downstream.

Real confluences form an arrowhead. The two branches meet at an acute angle and the point of the V faces the way the water is going. Look at any satellite image of a river basin and you’ll see the same shape repeating at every scale. It’s called a dendritic pattern, and it looks like a tree, or a leaf’s veins, or a bare branch in winter.

At every junction, ask which way the water is heading, then make sure both incoming branches lean that way. A tributary should look like it’s being swept into the main channel rather than colliding with it.

Mistake 5: The lake with no outlet

Three rivers flow into your lake. Nothing flows out.

In a wet climate, that lake fills. Then it keeps filling, until it finds the lowest point on its rim and spills over. Within a geological blink there’s a river leaving the lake, and it has carved itself a valley. A lake in a rainy region without an outlet isn’t a lake. It’s a lake that hasn’t finished happening yet.

The exception here is genuinely useful. Endorheic basins, meaning closed drainage, do exist: the Caspian Sea, the Great Salt Lake, the Dead Sea, Lake Eyre. Water comes in and leaves only by evaporation. Two things follow, and both are gifts for worldbuilders. They’re salty, because minerals arrive with the rivers and never leave, so nothing drinks from them and very little lives in them. And they sit in dry places, because evaporation has to keep pace with inflow, which means they shrink and swell dramatically between wet and dry years, leaving salt flats and old shorelines behind.

So either give the lake an outlet river running down to the sea, or commit to a salt lake: put it in an arid region, ring it with white flats, and let the local culture treat it accordingly. A city built on salt trade beats a hydrological error every time.

Mistake 6: The desert river with no source

A river winds confidently through the middle of your great desert. Where does it get the water?

Deserts evaporate more than they receive. A river can’t be born there.

But a river can absolutely cross one, and this is one of the most interesting features you can put on a map. Geographers call them exotic rivers: the Nile, the Colorado, the Tigris and Euphrates. Every one of them rises in wet highlands hundreds of miles away and then spends its whole journey losing water to a landscape that gives nothing back. The Nile picks up almost no tributaries for its last 1,700 miles.

That single fact builds civilisations. If one river is the only water for a week’s travel in any direction, then whoever controls the headwaters controls everyone downstream, every city sits on its banks, and the flood calendar is the calendar.

Don’t delete the desert river. Source it properly instead. Run it back to a mountain range or a monsoon-fed highland well outside the desert, and let it arrive already big. Then thin it as it goes, instead of thickening it.

Mistake 7: The river that never changes width

A line of perfectly even thickness runs from the mountains to the sea.

Real rivers grow. They start as something you could step across, and each tributary makes them wider, slower, and browner. By the time a major river reaches the coast it might be a mile across. That change in weight along its length is part of what makes a drawn map read as a real place.

Draw rivers in at least three weights: hairline for headwaters, medium after the first confluences, heavy for the last stretch to the sea. If you’re working digitally, taper the stroke. It takes a minute and it’s probably the highest-impact change on this list.

When to break the rules on purpose

None of this is a law. It’s a set of expectations your reader already carries, and breaking them deliberately is a legitimate move, as long as the break is loud.

A river that flows uphill because a god commanded it should be famous in-world. Pilgrims should travel to see it. A ring-shaped river around a city should be an engineering marvel that bankrupted a dynasty, with the aqueducts still standing. A lake that drains into nothing should have a name that means the throat.

The difference between a mistake and a feature is whether anyone in the world has noticed. If your characters walk past impossible water without comment, readers file it as an error. If somebody in chapter two says “nobody knows where the Kell goes,” it becomes the best thing on the map.

The 60-second river check

Before you call a map finished, run this pass:

1. Follow every river from the sea inland. Does each one end in high ground?
2. Look at every junction. Do branches merge going downstream, and does each V point the way the water flows?
3. Any river touching two coasts? Turn it into a strait or cut it.
4. Every lake: is there a way out, or is it salty and in a dry place?
5. Any river in a desert: can you trace it back to wet highlands off-screen?
6. Squint at the map. Do rivers get thicker toward the sea?
7. Any impossible water left? Then somebody in this world had better have an opinion about it.

Let the generator do the boring part

Getting drainage right by hand is genuinely fiddly, and it’s the part of mapmaking nobody enjoys.

Our fantasy map generator handles it in the terrain step. It raises the highlands first, then runs water down the actual slope of the generated landscape, so rivers start in the mountains, merge as they descend, thicken on the way, and reach the sea. No forks pointing the wrong way, no channels linking two oceans, no orphan rivers sitting in the middle of a plain.

Generate a continent, check it against the seven points above, and then spend your time on the part that’s actually fun: deciding who lives on which bank, and why they don’t get along.

Want a map sized for a campaign region rather than a whole world? The D&D map generator starts you on a single continent. For something smaller and stranger, try the island map generator.

Once the water behaves, the next two things worth getting right are where your cities sit and how big the whole thing is. Both depend on the rivers, which is why this one comes first.