Static infographics

Any chart type can be rendered as a static infographic rather than an animated video. The choice is made when the project is created.

A static project renders one still frame: a single data point per entity, no date animation, no particles, and no brand intro or outro. You still pick a normal chart type — the flag changes how it renders, not what it is.

Rendering is much faster than a video, and the output is an image you can drop into a slide deck, a document, or a social post.

Treemaps are the standout — an area-proportional composition reads perfectly as a still, and needs no motion to make its point.

Comparisons are already static by design, so rendering one as an image is a natural fit.

Maps work well when a single moment is the story — one year's distribution rather than a decade of change.

Races are the weakest fit. A bar race reduced to one frame is just a bar chart; if that is what you want, it works, but the type's whole purpose is the motion.

The deciding question is where the output is going. A video feed rewards motion; a slide deck, a report, or a printed page cannot use it at all.

Teams routinely build a video and then screenshot it for a deck. Rendering a static project directly is faster, sharper, and avoids the awkward frame you happened to pause on.