How to put a map in your video with the right shape

Last updated 2026-09-10 · 8 min read

What is the short version?

Maps are the one graphic your audience already knows the answer to. A chart can be slightly off and nobody notices; a state or a country with the wrong coastline is noticed by everyone who has ever seen it before.

1. Go to Vizard Agent with the place.
2. Say the outline has to be the real one.
3. Ask where the shape came from.

What do you need before you start?

The place and how much of it needs to be right. Vizard Agent works from public geographic data, and knowing whether you need a recognisable silhouette or an accurate boundary with towns on it changes which source is worth going to.

• The place. Named precisely.
• What has to be accurate. The outline, borders, cities.
• What is marked on it. A pin, a route, a region.
• The style. Flat, textured, animated.
• The format. A vertical map is cropped hard.

What do you type into Vizard Agent?

Tell Vizard Agent that the shape itself is the constraint. Ask simply for "a map of Montana" and you may well get something Montana-shaped; asking for the real outline taken from a public source makes the accuracy a requirement of the job rather than a happy accident.

Prompt

Variants worth knowing:

• "From real geography data." The instruction that matters.
• "Tell me the source." Makes it checkable.
• "Show me the animation." Stills hide the problems.

What does Vizard Agent actually do?

Here is the approach Vizard Agent takes on real films that needed a place shown on screen. The research step at the front is short, and it is the single step that decides whether the finished graphic survives contact with an audience that lives there.

1. Researches an official source for the outline.
2. Builds the shape from that public data.
3. Styles it to match the rest of the film.
4. Adds the markers — pins, routes, labels.
5. Renders the animation.
6. Pulls a contact sheet of the animated map.
7. Reviews it frame by frame rather than as a still.
8. Checks labels are legible at the size they will play.
9. Confirms the shape is still correct after styling.

Step one is short and non-negotiable. Public boundary data exists for almost every place you would put in a video, and using it costs one search — whereas a generated coastline is wrong in a way that cannot be corrected by adjusting the prompt.

Step seven catches what a still cannot. A map that animates — a pin dropping, a route drawing on, a zoom into a region — can be perfect at the start and end and wrong in the middle, with a label sliding off or the outline distorting as it scales.

Step nine is worth doing explicitly. Styling passes, textures and generated fills can subtly reshape an accurate outline, so the shape gets checked again after the look has been applied rather than only when it was built.

What does the result look like?

A map that people from that place recognise straight away. The outline is the real one, the markers sit where they actually belong, and the labels can still be read at the size the video plays at rather than at the size it was designed at.

Vizard Agent also tells you which source the boundary data came from, which is the answer to the question somebody will eventually ask.

When does this not work well?

Data does not settle everything, and Vizard Agent will say when a question is not a technical one. Disputed boundaries, historical borders and deliberately stylised maps are editorial decisions rather than data ones, and a very small map cannot carry detail whatever source it came from.

• Disputed borders. An editorial choice, not a data one.
• Historical maps. Present-day data is the wrong source.
• Very small on screen. Detail disappears regardless.
• Deliberately stylised maps. Accuracy may not be the point.
• Places with no clean public data. Rare, but it happens.

How do you fix a result that came back wrong?

Say what is wrong with it geographically rather than visually. Because Vizard Agent built the shape from named data, a note like "the border is wrong here" is checkable directly against that source, whereas "it looks a bit off" leaves it adjusting the styling instead.

• "That border is wrong." Checked against the source.
• "The pin is in the wrong place." Coordinates, not eyeballing.
• "The label slides off." Caught in the animation review.
• "It distorts as it zooms." The shape is being scaled badly.

How does Vizard Agent compare to doing it yourself?

By hand a map is generated or drawn to look right, because that is quick and it usually passes an internal review — everyone in the room is looking at the design rather than the geography. It fails with the audience instead.

Common questions

Why not just generate a map? Because a generated outline is plausible rather than correct, and viewers know the difference.

Where does the shape come from? Public geographic data. Vizard Agent tells you which source.

Can it mark a route? Yes, and it will place the points by coordinate rather than by eye.

What about a city map? Same approach, though Vizard Agent will warn about detail at small sizes.

Can it animate a zoom? Yes, and it reviews the middle of the move as well as the ends.

Will the labels be readable? Vizard Agent checks them at the size the video will play at.

What about disputed borders? That is your editorial call. Vizard Agent will flag it rather than choose.

Can it match my brand colours? Yes, and it re-checks the outline after the styling is applied.

Does it work for historical maps? Only with a historical source. Vizard Agent will say so.

Can it show a region within a country? Yes. Vizard Agent builds it from the same public data.

Will it fit a vertical video? Vizard Agent will tell you when the shape crops badly in portrait.

How accurate is the data? As accurate as the public source, which Vizard Agent names for you.

Can it add a pin that drops? Yes. Vizard Agent places it at real coordinates rather than as a positioned graphic.

Why do generated maps look wrong? Because they are drawn from an impression of the shape rather than from its real boundary data.