A five-second establishing shot needs a yellow hot-air balloon to rise from behind a riverside bridge and move toward the upper-right sky without changing the bridge or balloon markings. This is a motion-direction problem, not merely a request for a prettier picture. Runway lists Motion Sketch as a dedicated App that uses annotations to drive video motion. The reliable approach is to draw the intended route, supply a tightly scoped scene instruction, and judge the exported frames against the original design. The balloon-and-bridge art in this guide is an independent teaching illustration, not an actual Runway export.
Define the motion before entering the editor
Draw the scene on a single reference sheet. Place the bridge across the lower third, a low balloon slightly to the left of center, and clear sky above the far-right span. Add a start dot and an end dot connected by a curved arrow; label the arrow “rise, then drift right.” Include two negative requirements: the stone bridge should remain still, and the balloon must not turn into a different shape. This paper storyboard gives you a concrete basis for judging output. Without it, a visually polished clip could still move in the wrong direction and leave the shot unusable in the finished edit.
Open Motion Sketch rather than inventing a hidden parameter
Runway’s Apps documentation explicitly identifies Motion Sketch as the workflow for using annotations to drive motion. Start from the App available in your account and use its displayed upload, annotation, prompt, and generation controls. We do not prescribe undocumented brush colors, numerical strength values, guaranteed interpolation behavior, or a fixed credit cost, because the public Apps overview does not promise those settings. Check the live interface before following a tutorial from another model or an older Runway product. Record the product name and version or date in your project notes.
Make the annotation describe one path
Use the clearest directional mark that the current App accepts. Avoid overlapping arrows for the sky, balloon, camera, and clouds if the goal is simply an object traveling across a stationary composition. Keep the path continuous: first an upward leg, then a gentle rightward curve. Set a destination that leaves margins around the balloon envelope and basket; an object that exits the frame early cannot serve as the planned ending. If the App accepts supplemental text, explain which object follows the drawn route and which objects remain fixed. The route drawing is an instruction, not evidence that every frame will follow it.
Separate subject movement from camera movement
A rising balloon can be depicted with a locked-off camera, a camera tilt, or a tracking move; those alternatives produce very different backgrounds. For this assignment, request a stable bridge and a stationary viewpoint so the only intended travel comes from the balloon. If the background shifts while the balloon remains centered, the model may be simulating a camera move rather than object motion. Mark that as a different concept, not a successful result. Make a second brief only when camera movement is truly desired. Do not compare a locked-camera prompt with a camera-following prompt as though they were the same test.
Review start, middle and end as distinct moments
Export a short preview and inspect at least three still frames: initial placement behind the parapet, the midpoint above the central arch, and the ending high in the right-hand sky. Overlay your drawn start and end coordinates onto those stills, but do not treat the overlay as ground-truth motion tracking. Watch for basket deformation, a changing number of ropes, duplicated clouds, shifting bridge stones, and frames where the balloon teleports rather than moves. An occasional glitch may be less visible at playback speed; single-frame checks reveal the difference. Save the failed frames alongside the prompt so the next revision targets a specific defect.
Keep the storyboard and video rights separate
A drawn reference can contain original artwork, licensed photos, or commercially restricted imagery. Record whose balloon illustration and bridge scene you are authorized to modify. The existence of a drawing or an uploaded image does not itself grant permission to use another creator’s design in a paid campaign. If an identifiable person appears near the bridge, do not imply the output documents a real flight or event. Put a “concept illustration” note in the internal review deck and have the final publisher decide whether the synthetic imagery needs visible disclosure.
Plan the fallback if the route does not hold
When a generated version misses the path, avoid repeatedly widening the instruction to “make everything cinematic.” Reduce the task to the one movement that failed, simplify the background, or adjust the reference starting position before trying again. Alternatively, create key visual beats with a conventional editor or animation tool; that may give a more dependable result for a fixed educational sequence. Keep a record of generation attempts and costs, especially when a team is using a limited credit allocation. A beautiful failed route should be archived as a rejected concept, not published under the successful storyboard label.
Deliver a verifiable motion-review sheet
Export the selected clip, the original reference sheet, the annotation drawing, and a three-frame contact strip in one review folder. Write a one-line verdict for path accuracy, background stability, recognizable balloon details, framing margins, and source rights. Ask a second reviewer to watch the clip without seeing your verdict and flag any motion that contradicts the intended story. Do not present the examples in this article as empirical Runway benchmarks; only a reader’s own output can answer whether the current version performs reliably on that material.
How We Research
This Runway Motion Sketch workflow was prepared as independent editorial guidance grounded in these primary sources: Runway Apps: available video workflows; Runway Gen-4.5 generation guidance. The example is an original illustrated yellow hot-air balloon moving above a riverside bridge, with an arrow-based storyboard and an unaltered reference illustration. All accompanying graphics are original conceptual teaching illustrations; they are not vendor screenshots, actual outputs, measured benchmarks, or evidence that a live software project was run. We compared documented capabilities and limitations, defined a scenario with observable pass-or-fail checks, and identified practical areas requiring human verification including source rights, factual content, consent, accessibility, and continuity. We did not purchase an account, upload private footage, or measure performance. Readers should verify current account access and controls, preserve originals, and test their own exported media before release.
Frequently Asked Questions
Runway describes Motion Sketch as an App that uses visual annotations to direct motion; exact controls can vary with the interface.
No. Treat them as directional instructions and inspect the generated beginning, middle, and ending frames.
Not in this locked-camera example; background movement would conflict with the intended shot and needs review.
Yes. Use an original or properly licensed reference and assess rights and any disclosure obligations before publishing.
Save the source artwork, drawn motion path, instructions, key frames, rights notes, and the final approved export.