Back to the animated explainer guide

How to animate a flow diagram with a moving marker

To animate a flow diagram, keep its nodes and connectors fixed and move one marker along the route. Change the caption when the marker reaches each station, then hold at the endpoint. Start with verified station names and connections; review the animation without sound before exporting.

Copy the production brief or watch the reference below.

Showing two possible outcomes instead? Plan a three-shot decision fork animation.

Watch the fixed-route example

Loretry Infrastructure Flow Diagram 1.0.0: a 24-second reference, 960 × 540 at 30 fps.

The full diagram stays in view while one marker follows Source → Treatment → Distribution → Tap and stops at Tap. This is an illustrative water-system sequence. The treatment stage is generic; it does not document a particular utility, treatment method or travel time.

View the flow diagram example and Skill details. The visible preview is a reference, not proof that a new project has been generated or exported.

1. Supply the route and station captions

Bring a diagram you have permission to use or redraw, an ordered station list, the directed connections and one short caption per station. Name what the marker represents and where it should stop. For a real system, verify these inputs with its documentation before animating it.

For this schematic exercise, use Source → Treatment → Distribution → Tap. The marker indicates sequence only. Use the station names as captions; do not add unverified process details. If your route branches or loops, choose one path and state what it leaves out.

2. Lock the layout before adding motion

Approve a still with the entire route visible. Keep station positions, labels and connector bends unchanged throughout the animation. Reserve a separate caption area so text cannot cover the route. The moving marker should be easy to distinguish from the stationary nodes.

3. Tie captions to station arrivals

Use one editable arrival cue for each station to control both the marker and its caption. Hold the marker at a station while its caption is read, then move along the connecting line. Stop at Tap and hold the full route for the ending. Choose readable pacing for your own captions; the reference does not establish exact segment durations.

Try a 24-second practice timeline

These timings are for your own exercise. They are not measurements from the reference video or estimates of water travel time.

  • 0 s — Source
  • 6 s — Treatment
  • 12 s — Distribution
  • 18 s — Tap; hold through 24 s.

At each cue, check that the marker reaches the named station as its caption appears. At the first three stations, hold for three seconds, then use the next three seconds to move to the next station. Keep the full route visible through the final hold.

Open a still from the reference or open the reference MP4 directly.

Copy the production brief

Paste this into your animation agent after confirming its project format and rendering requirements. The requested files below are delivery requirements, not a verified export from this tutorial. Model, API and rendering costs are separate.

Create an illustrative flow diagram animation. Inputs: route Source → Treatment → Distribution → Tap; directed connections Source to Treatment, Treatment to Distribution, Distribution to Tap; station captions “Source”, “Treatment”, “Distribution”, “Tap”. One moving marker represents sequence only. This is a schematic exercise, not a verified real water system.

Keep the whole diagram visible and the layout fixed. Keep node positions, labels and connector bends unchanged. Move one distinct marker along the connectors in route order. Use shared, editable arrival cues for the marker and captions. Display each station caption when the marker reaches that station and hold long enough to read it. Keep captions clear of the route. End with the marker stopped at Tap and hold the full diagram.

Request a 24-second, 960 × 540, 30 fps preview to match the reference format. Propose readable arrival and hold timings for approval before rendering; do not infer exact segment timings or real travel times from the reference. Deliver an editable scene or project with separate node labels, route geometry, marker motion, captions and arrival cues, plus an MP4 preview and render instructions listing required dependencies. Review without sound.

4. Review without sound, then test one edit

  • Play the preview muted. Can you follow the marker from Source to Tap without losing the full route?
  • Pause at each station. Does the caption name that station when the marker arrives? If it appears early or late, adjust the shared arrival cue.
  • Check that labels and captions remain readable at your intended viewing size and never cover the route. Extend holds or shorten captions when needed.
  • Inspect the last frame. The marker must stay at Tap, with the complete diagram still visible.
  • In the editable project, change the Distribution caption to “Distribution network” and render again. Confirm that the new text appears at the same station without moving nodes or connectors. Keep both previews and the project to check the revision.

If the muted sequence is unclear, fix the layout, marker visibility or arrival cues before adding narration. For your own subject, replace the schematic inputs with a verified route and repeat the same checks.

How to animate a decision fork with two outcomes

When you need to explain both outcomes of a decision, draw both branches in one fixed layout. Start at the shared source, emphasize one branch and its endpoint, then switch emphasis to the alternative. Keep the unselected branch visible but lighter. Label each branch with its condition and each endpoint with its result.

Watch the 12-second Decision Fork 1.0.0 preview (960 × 540, 30 fps), or view the Decision Fork Skill reference. In the preview, “Start with one question” holds the marker at Source. “First outcome” emphasizes the upper Route A and its endpoint while the other route stays light. “Alternative outcome” emphasizes the lower Route B and its endpoint while the upper route stays light. Both branches keep the same positions.

Plan three shots in the same layout

The following is a generic teaching example, not the scenario shown in the preview: ask “Is the input complete?” Use “Yes: complete” for the upper branch leading to “Continue”, and “No: incomplete” for the lower branch leading to “Request missing input”.

  1. Show the question. Display the shared source, both connectors and both endpoints. Hold attention at the source while the viewer reads the question.
  2. Show the first outcome. Emphasize the upper connector, “Yes: complete” condition and “Continue” endpoint. Keep the lower branch lighter, with its labels still readable. Hold for the result caption.
  3. Show the alternative. Return attention to the same question, then emphasize “No: incomplete” and “Request missing input”. Fade the upper branch to the lighter state without moving or removing it. Present this as an alternative case, not a next step after “Continue”.

Copy the decision-branch brief

Create an illustrative two-outcome decision animation. Question at the shared source: “Is the input complete?” Upper branch condition: “Yes: complete”; result: “Continue”. Lower branch condition: “No: incomplete”; result: “Request missing input”. Keep both branches, labels and endpoints in one fixed layout. Show the question, emphasize the upper branch and result, then switch to the lower branch and result. Keep the unselected branch lighter but readable. Synchronize each result caption with its branch emphasis. Do not imply that the two outcomes occur in sequence. Propose readable holds for approval; do not infer exact transition times from the reference. Request an editable scene and an MP4 preview; these are requested deliverables, not a verified export.

Review muted: can you read the question, identify the condition for each result and see which branch is active without relying on color alone? Check that neither endpoint moves and the lighter labels remain readable. In your project, revise one condition and render again; confirm that its caption and emphasis still match. For a real decision, verify the conditions and results against the source material first.