How to Build a Fantasy World Without Drawing a Map
Nearly every worldbuilding guide opens with the same instruction: draw your map. Plenty of creators can't draw, though. Some simply don't want to, and some can't see a map at all. Here's the good news. A map isn't what makes a world feel real. The heavy lifting happens elsewhere: in how places relate to each other and how long it takes to get between them, plus what each place sounds and feels like once you arrive.
So this guide shows you how to build a coherent fantasy world entirely in words. There's a bonus, too. A world built this way is precisely the kind that thrives in an audio-first game. I'd know, because EchoQuest runs on worlds like that, and honestly I didn't set out with a grand theory. Every design decision just kept nudging me in this direction.
Why Word-First Worldbuilding Works
- Players rarely see your map anyway. In most games they pick up the geography through the story, one road and one rumour at a time.
- Words carry mood. "Three days' ride through the Weeping Fens" tells a player far more than a green smudge on paper ever could.
- It's accessible. Blind and low-vision creators can build whole worlds without a single visual tool.
- An AI Game Master understands descriptions better than images. Text is what it reasons about, so as far as the GM is concerned, your sentences are the world.
There's decent science behind this, by the way. Psychologists have studied for decades how people picture places they've only read about, and a 1992 paper co-written by Stanford's Barbara Tversky explains that readers build mental models of a scene straight from the text. Those models hold on to plain relations like "above", "north of" and "across from". The same paper also cites a study in which readers formed a usable model of an environment from route descriptions (the kind that walk you through it) and from survey descriptions (the kind that lay it out from above). So your readers' heads are already doing the cartography. You only have to hand them good sentences.
That last bullet is a lesson I learned from the inside, too. EchoQuest's world format has no map field at all. Each location is a name, a few sentences of description, a one-line summary, an ambient sound and a list of the places it connects to. No picture. No coordinates. And the GM runs whole campaigns on that.
Step 1: Choose a Spine
Every world needs a simple organising shape, something you can hold in your head without notes:
- A river running from mountains to sea, with cities strung along its banks
- A road linking two rival capitals
- A coastline of islands, like the Stradovine Archipelago in EchoQuest's Saltbound
- A ring of kingdoms circling a forbidden centre
- A vertical world, with sky cities above and caverns below
Your spine lets anyone, an AI included, place things in relation to each other. It's the first decision I'd make, every time. Saltbound shows why. Its geography hangs on an island chain, so when the crew mentions that the navigator vanished at the Bone Reef, "three islands east", you know roughly where that is and that it's a real sail away. Nobody unrolls a chart for that.
Which spine would your world hang on? Rivers are my quiet favourite, because "upstream" and "downstream" do so much storytelling for free.
Step 2: Describe Places by Relationship
Forget coordinates. Use relationships instead:
"Harrowgate sits where the King's Road crosses the River Ashe. Two days upstream is the monastery of Saint Vell. Downstream the river widens into the salt marshes, and then the port of Brine."
That paragraph is a map. It tells you what's connected and what lies upstream or downstream. It even tells you how long the journeys take.
Sailors worked like this for centuries, incidentally. The Periplus of the Erythraean Sea, a Greek guide for merchants written in the first century CE, reads remarkably like the paragraph above. Here's a line from Wilfred Schoff's 1912 translation: "Two days' sail, or three, beyond Malao is the market-town of Mundus, where the ships lie at anchor more safely behind a projecting island close to the shore." You get a sailing time and a reason to drop anchor, and nothing else. The whole document carries on like that, port after port, down the African coast and across to India.
It's also, more or less, how EchoQuest reads a world. When you upload a Game Bible, the parser picks out each location along with the names of the places directly next to it. So if you write your relationships plainly, the connections land where they belong.
Step 3: Measure Distance in Time
Players care about how long a journey takes, far more than how many miles it covers. So build a simple travel table:
| From | To | Route | Time | Danger |
|---|---|---|---|---|
| Harrowgate | Saint Vell | River path | 2 days | Low |
| Harrowgate | Brine | River barge | 1 day | Medium (smugglers) |
| Brine | The Fens | Causeway | Half a day | High (fog, bog lights) |
Travel time creates choices: the safe road or the fast one?
Historians lean on the same trick. Stanford's ORBIS project, a model of travel across the Roman Empire, lets researchers express Roman communication costs "in terms of both time and expense", simulating trips along roads, rivers and sea routes, season by season. If time and expense are good enough for mapping Rome, they're good enough for the Ashe Valley.
Need a yardstick for travel on foot? The D&D Basic Rules put a normal pace at 24 miles a day. A fast pace gets you 30 miles but dulls your perception, whereas a slow one manages 18 and lets you sneak. I love that little trade-off, and you can steal it wholesale: speed costs attention.
Step 4: Give Every Place Three Senses
For each major location, write:
- One sound: gulls and creaking rope in Brine, chanting at Saint Vell
- One smell: tar and fish, incense and wax
- One feeling: crowded and suspicious, calm but watchful
Three sensory details stick far better than a page of architecture. They're also exactly what an audio game needs.
Give smell a little extra love. Harvard neuroscientist Venkatesh Murthy told the Harvard Gazette that "the olfactory signals very quickly get to the limbic system", the part of the brain tied up with emotion and memory. That's why one line about tar and fish can bring Brine flooding back to a player weeks later, when the name on its own wouldn't.
Sound was the sense I underestimated. In May I added forge, storm and underwater ambient tracks to EchoQuest, and every location can carry its own background sound. In Saltbound, for instance, the cove gets surf with wind in the cliffs and the village gets tavern noise. Then I discovered the soundtrack was trampling the sound cues, so it had to learn to duck underneath them. Lesson learned: a place's sound belongs in its description, but it has to leave room for the story. Later, on October 2, I rewrote the GM's voice, and one of the first rules I gave it was to open each scene on a single concrete sensory detail. Your three senses hand it something to open on.
Step 5: Connect Places Through Conflict
A world wakes up when places want things from each other:
- Brine smuggles goods past Harrowgate's river tolls
- Saint Vell shelters refugees from the Fens, and Harrowgate wants them expelled
- The Fens are rising, and every year the causeway floods a little further
Now the geography is a story engine.
Notice that every one of those conflicts runs along a route from the travel table. That's no accident, and it's the bit I'd urge you to copy. Saltbound does it with the Bone Reef: the navigator was last seen there, and the Crown frigate Argent has been spotted in that same water twice in two days. So the place you most need to reach is exactly where the danger sits. One sentence of geography, and the plot practically writes itself.
Step 6: Write a Regional Summary
Pull it all together in a short, structured summary:
The Ashe Valley. A river kingdom running from the Grey Peaks to the Salt Coast. Its capital Harrowgate controls the river tolls. Upstream: monasteries and mountain passes. Downstream: the smuggling port of Brine and the rising Fens. Tension: the Fens are swallowing the southern farms, and refugees are straining every town.
That's under sixty words, and a Game Master, human or AI, can run a whole campaign from it.
Why keep it so lean? Because the GM leans on it every single turn. When EchoQuest turns an uploaded Game Bible into a playable world, it condenses the setting into a GM briefing of roughly 200 to 400 words, which has to cover tone, tensions, rules and the opening situation as well. A tight regional summary leaves room for all of that. A rambling one crowds it out.
Step 7: Put It Into a Game Bible
On EchoQuest, your world lives in a Game Bible, a structured document covering setting, locations, factions, NPCs and rules. Word-first worldbuilding drops straight in. See How to Write a Game Bible, or let the World Builder Wizard walk you through it step by step.
You don't need fancy formatting either. The upload takes PDF, DOCX, TXT, MD and JSON, so a plain text file with your spine, places, travel table and conflicts is plenty. Afterwards you get to look over the summary it pulled out before you play. Building a private world comes with the Storyteller plan, by the way.
Should You Ever Draw a Map?
If you enjoy it, absolutely. Maps are lovely. But let the map illustrate the world rather than define it. The words should hold up on their own.
Tolkien, famously, went the other way. In a 1954 letter to Naomi Mitchison he wrote, "I wisely started with a map, and made the story fit (generally with meticulous care for distances)". I'm not about to argue with the man about Middle-earth. Still, look at what his map was protecting: distances. A travel table guards exactly the same thing, and you can read it aloud to someone who has never seen a single line of ink. So my view is firm. A map is a pleasant extra, but the words are the world.
Build Your World
Start with a spine and a few places, then give them one conflict to fight over. You'll have a playable world in an afternoon, no drawing required. So, where does your river start?