About

Making place the start of the story

Creating a professional map video used to mean hours of manual keyframing. Now you write the story and the map follows it, whether you build the scenes yourself or let your own AI agent do it.

The vision

We believe location is the most powerful context in storytelling. Whether you are selling real estate, recapping a trip or explaining a geopolitical event, a map gives viewers a sense of place and scale that a talking head or stock footage cannot.

The technology

Mapflyover combines real satellite imagery, live geographic boundary data and a scene engine that turns a script and its caption timings into a fully timed camera sequence. Editing and rendering run in your browser, with no cloud render queue to wait in.

Why rendering runs in your browser

Keeping rendering on your own device was a deliberate choice. Your video is composed there, and you decide when it is saved or shared. Projects, narration and exports are stored in your private account so you can come back to them, and we do not sell your production data. For creators working with unreleased scripts or client-confidential listings, that is a design choice, not only a policy promise.

What we care about

Four things we will not trade away

Accuracy over approximation

Real administrative and geographic boundaries, not generic shapes standing in for a place.

Sync that actually holds

Camera timing locked to your narration, and captions timed to the word, not eyeballed.

Private by default

Your projects are visible only to you. Rendering happens on your device, and the keys you add are stored encrypted and never shown again.

No editing degree required

A script and a few minutes should be enough to get a finished video.

Who it is for

People with somewhere to take you

Creators
Countdown, travel and geography content for TikTok, Shorts and YouTube.
Real estate
Genuine spatial context on a listing or a region.
Educators
Geography, history and current events with real scale and real place.
Journalists and explainers
Setting the scene for a story before the reporting starts.

Where we are headed

Early, and still growing

We build in the open, shaped by what creators tell us they need next. This page will keep changing as the product does.

Who we are

One founder, one product

Mapflyover is an independent product, designed, built and operated by its founder, Ali Hassan, from Darwin, Australia. There is no parent company behind it, no team of departments and no investors to answer to: the person who writes the guides is the person who builds the studio, reads the support inbox and decides what gets fixed next.

That smallness is deliberate, and it cuts both ways, so here is the honest version of it. You will not find a sales team, a press office or a roadmap written by a marketing department. What you get instead is a product that is used by its own maker every week, support answers that come from the person who can actually change the code, and guides that are written from doing the work, not from a brief.

What we do

A studio that turns scripts into map videos

Mapflyover makes one kind of video, and makes it properly: a cinematic 3D flyover over real maps and satellite imagery, driven by a script. You write the story, or describe the video to the built-in Create with AI, or connect your own AI agent (Claude, ChatGPT or another MCP client) and let it build. The studio finds the real outline of every place, frames and flies the camera, adds narration in your choice of voice, times captions to every spoken word, and exports a finished MP4 in your browser, vertical 9:16 or landscape 16:9.

Around that core it does the jobs a map video actually needs: stat and focus cards, a location chip with the country flag, place fills, routes and lines, moving props and stickers, animated titles, data maps and racing bar charts from a CSV, six ready-made templates, a soundtrack built from your own audio, and, on Pro and Studio, scheduling the finished video to your channels through Buffer. It serves creators making countdowns, travel and geography videos, educators and journalists who need to show where something happened, and property and local businesses showing where they are. The full, current list is on the features page, and the limits of each plan are stated plainly on the pricing page.

Our story

Built because the founder needed it

Mapflyover exists because making a decent map video by hand is slow. The usual route is a desktop editor, a satellite image traced or keyframed shot by shot, captions typed and timed one by one: hours of work for a minute of video. Ali makes map videos himself, for his own channels, and kept hitting the same wall: the story was the easy part, and the map work was the bottleneck.

So the tool he needed was built instead: write the script, and let the software find the places, fly the camera and time the captions. The Shorts on the home page of this site were made with Mapflyover itself, on the founder's own channel, which is still the first test every change has to pass: if a feature does not make those videos better, it does not ship. The guides on this site come from the same place. They are the notes from building and using the product, written up so you do not have to learn the same lessons the slow way.

The author

Ali Hassan, founder

Every guide and use-case page on this site is written by Ali Hassan, the founder of Mapflyover. He writes them from building the product and from making his own map videos with it, and each one shows when it was last updated. There is no content team and no outside writers: if a guide is wrong, it is his mistake, and the support inbox is the fastest way to get it fixed.

You can find him on LinkedIn, or reach the product through the contact page.

Editorial guidelines

How these guides are written and kept honest

Our guides follow a short set of rules, and they are rules you can hold us to:

  • ›Written from the product, not about it. Every instruction is checked against what the current version of Mapflyover actually does before it is published. If a button, limit or step cannot be found in the product, it does not go in the guide.
  • ›Limits are stated, not hidden. Plan limits, export formats and things the product cannot do yet (it does not draw historical borders, and it has no stock music library, for example) are written in the guides themselves, next to the features they limit.
  • ›Updated when the product changes. When a feature, price or limit that a guide mentions changes, the guide is revised and its last-updated date changes with it. The date at the top of each guide is real.
  • ›Nothing invented. We do not publish reviews, ratings, testimonials or user numbers we cannot stand behind, and no company pays to be mentioned in a guide. Where a guide uses an example, it is labelled as an example.
  • ›Corrections are welcome and fast. If you find an error, tell us through the support inbox and it will be fixed in the guide and the date updated.

What you can check for yourself

Trust should not need our word for it. The pricing page states every plan limit in plain numbers, including what the Free plan cannot do. The demo on this site runs with no account, so you can watch the studio work before signing up. Your exports render in your own browser, and your projects stay in your private account. Every guide names its author and shows when it was last updated, and if anything on this site turns out to be wrong, the support inbox is answered by the founder, the same person who can fix it.

Where will you take us?

Build the whole film for free. Export when you are ready.