Biblical atlases are a staple of serious Bible study. They're also, almost universally, annoying to use.
I built Anselm Atlas as a free, interactive map of the biblical world — roughly 190 sites across the Mediterranean, the Levant, Egypt, Mesopotamia, Persia, and Asia Minor. Cities, mountains, rivers, regions, provinces. From the Garden of Eden to the seven churches of Revelation, with a solid layer of Second Temple and intertestamental sites — Masada, Qumran, Machaerus, the Decapolis cities, Hasmonean battle sites, Diaspora communities. No account required. No paywall. Free, permanently.
The Problem with Biblical Geography
Biblical atlases are always neat and rarely useful. You flip to the back of your study Bible, find a map of Paul's missionary journeys, and get a static image that tells you approximately where things were but gives you no feel for what they meant. Distance is doing a lot of theological work in Scripture that most readers never feel. When Luke writes that Paul "set sail from Troas" or Genesis says Abram "went down to Egypt," the miles matter. Three days on foot through hostile territory is not the same kind of journey as a Sunday drive to the next county over, and reading it that way produces a flattened understanding of the text.
The Atlas exists to put that geography under your hand and let you feel the scale.
How It Works
You select sites from a categorized, alphabetized, searchable list. The order you select them becomes a route — markers are numbered in sequence, dashed gold lines connect them, and real distances are calculated along each leg with totals at the bottom. If you want to map Paul's first missionary journey, you click Antioch, then Seleucia, then Salamis, then Paphos, and so on. You end up with the actual arc of the journey, in miles or kilometers, with each segment labeled.
This is a deliberate design choice. Most digital atlases let you pin places. Few of them let you build a route. But the Bible is a profoundly itinerant text — the Pentateuch is largely a travel narrative, the Gospels move between regions on purpose, Acts is structured around journeys. Abram's call from Ur to Haran to Shechem is a 1,200-mile arc of obedience. You can click that out in thirty seconds and see it. You can click out the Babylonian exile route, the flight to Egypt, the eunuch's road from Jerusalem to Gaza. The route tool turns the Atlas from a reference into a reading companion.
Why a Wire Map
I used a minimal basemap — terrain and water, no modern labels by default. That's on purpose. A satellite view is a beautiful object, but it's a 21st-century object. Modern political borders, modern coastlines, modern city lights — all of them tell a story that isn't the Bible's story. The wire map strips back to what matters: where things were, in relation to each other. The geography of the ancient Near East hasn't changed much. The politics layered on top of it have changed constantly, and I don't want those layered on top of a biblical map.
Honesty About Uncertainty
Some biblical sites are archaeologically established beyond reasonable dispute. Others we know only by region. The Atlas distinguishes between them. Sites with established archaeological identity get a solid gold marker. Places whose location is genuinely contested — Eden, Ophir, Tarshish, Sheba — get a dashed circle with a question mark, and the popup says plainly that the position is approximate.
Christian discourse has often been embarrassed by geographic uncertainty, and that embarrassment has produced a lot of false confidence. A tradition names a hill in the Sinai Peninsula and asserts it as the mountain of the Law, when the honest answer is that the location is contested. I'd rather say "somewhere in Mesopotamia" about Eden than pin it with false precision and imply that certainty exists where it doesn't. The question mark is a feature, not an admission of weakness.
What's Coming
The data structure is built for additions — new sites need a slug, coordinates, a category, a testament tag, an uncertainty flag if appropriate, and a one-sentence description. Future expansions will likely include battle sites and campaign routes, and additional patriarch-era and exodus stations. Longer-term, I want to integrate the Atlas with Anselm's reports — so when you generate a study on Paul in Ephesus or the fall of Jerusalem, the relevant geography is one click away.
A Tool That Answers the Right Questions
Biblical atlases have always existed. The problem is that they rarely answer the questions people actually have. How far is Jerusalem from Thessalonica? What's the scope of Paul's journey from Antioch to Rome? What's actually between here and there? The Atlas is built around those questions — click two points and you have a real distance. The scale of the biblical world becomes something you can measure rather than vaguely imagine.
Most of Anselm's study tools are AI-generated and designed to be. The Atlas is different in kind, not in care. It's a reference tool, and reference tools live or die on the accuracy of their data.
The Atlas is free, no account required. Take a look.
God bless, everyone.
Scripture References
Key Terms
A minimal basemap showing terrain and water without modern political borders or city labels, designed to foreground ancient geography rather than contemporary overlays.
The era of Jewish history from the rebuilding of the Temple (~516 BC) to its destruction in AD 70, including sites like Masada, Qumran, and the Decapolis.
A text structured around movement and journey; used here to describe how much of Scripture — the Pentateuch, Gospels, Acts — unfolds as travel narrative.
