Four steps, and three of them are typing
MightyMaps is a map builder you talk to. You never open a layer panel, paste a coordinate or pick a marker icon from a grid — you describe what the map is for, and the map becomes that.
Plan a five-day Nova Scotia road trip out of Halifax
Built 8 stops, a 720 km driving route and a five-day itinerary
Start with one sentence
Open a new map and type what it is for. There is no wizard, no template picker and no blank canvas staring at you — the first message is the whole setup step.
The assistant asks a question back if something genuinely matters and you left it out. Otherwise it just builds.
Pins, routes, areas and a list
It places real coordinates for real places, numbers the stops if the order matters, routes lines along the actual road or footpath network, and writes the sidebar list with a summary line per entry.
It is not writing a web page freehand. It fills in a strict map structure that is checked before anything is saved, which is why a map never comes back half-broken.
Every change is a sentence
"Add a night in Lunenburg and shift the rest back." "Group these by neighbourhood." "Put the parking notes on each venue." "Make it warm terracotta." The whole map is rewritten consistently — the route, the dates and the list all move together.
Each edit saves the moment it lands, with the conversation kept beside the map. Nothing to press, nothing to lose.
Public on a switch
Maps are private until you decide otherwise. Flip the switch and the map gets its own address on map.mightymaps.app — a plain web page that opens on any phone with no app, no account and no login wall.
Keep editing afterwards. The link never changes, so everyone who already has it sees the current version.
Why the maps come out consistent
The assistant is not writing a web page. It fills in one strict structure — places, shapes, groups, entries, colours — which is validated before anything is saved and then rendered by a single renderer.
Checked before it is saved
Coordinates in range, references that resolve, real dates, colours that are actually colours. An edit that fails the check is retried, not shipped.
Contrast is enforced, not hoped for
Any colour you do not choose is derived from the ones you do, and text is measured against the surface it sits on. Ask for a dark map and it stays readable.
Real networks, not straight lines
Driving, walking and cycling routes are calculated on the real network. Flights and ferries are drawn as direct lines, because that is what they are.
Text on a map stays text
Anything you or the assistant writes is treated as text, never as code, so a map you share cannot be turned into something it should not be.
The conversation is part of the map
Every message and every edit is stored with the map. Reopen it in six months and the history of how it got there is still beside it.
Private until you publish
Nothing is visible to anyone else until you switch it on, and switching it off takes the page down again.
Getting started
You get a blank map and a chat box. Describe what you want and the first version appears — usually in under a minute for a full itinerary. From there it is a conversation.
Yes. Paste a list of places, an email itinerary, a set of addresses or a track of coordinates into the chat and ask for a map of it. Pasted addresses and coordinates are used exactly as given.
Tell it. "That is the wrong Springfield." "Move the hotel to the other side of the river." "Drop that stop entirely." Corrections are the normal way of working, not an error path.
No. Everything is saved as it happens, including the chat, so you can come back a week later and carry on from where you stopped.
Building a map is more comfortable on a laptop, because you want the chat and the map side by side. Using a finished map is designed for a phone.
Your next trip, mapped in a minute
Start with a sentence. Keep going until the map is right. Share the link with whoever needs it.
25 free credits when you sign up · No credit card · No subscription