A camera control menu is not the same as a locked camera move

The shot

As of 16 September 2026, three current video-generation products document explicit camera controls rather than leaving framing and movement entirely to a text description. Runway's Camera Terms, Prompts, and Examples guide lists shot sizes, angles, and named movements such as pan, tilt, dolly, push in, pull back, and truck, each paired with a Gen-4.5 example clip. Luma Labs' Camera Motion guide for Dream Machine lists a shorter menu of preset moves: pan, orbit, crane, four directional moves, and push in or pull out. Google DeepMind's Veo 3.1 product page advertises camera controls including move back, zoom in, move up, and move right, alongside a separate feature for transitioning between a first and last frame. All three are living documents describing an interface as it exists today, not a fixed specification.

What the documents show

Each page states a named control as a menu option or prompt term, which is the vendor's own account of the interface, not an independently verified measurement of how reliably the control reproduces a specific angle or speed. Runway's own FAQ on the Camera Terms page is the most candid limitation on record: it states that video models are "designed to create immersive, high-fidelity motion, which can make achieving static shots challenging for certain camera angles or scenes, most notably establishing or wide landscape shots," and recommends reinforcing the instruction in prose or stabilizing the output afterward in an editor. This is Runway describing its own model's weak point, not a third party's test. Luma's and Veo's pages list what their controls do without a comparable caveat, which is worth noting: an absence of a stated limitation is not evidence the limitation does not exist.

The workflow

An operator selects a shot size or angle from a vendor's own terminology, such as Runway's macro, close-up, medium, wide, and establishing categories, or Luma's named presets, adds the term to the prompt or menu, and generates a clip within the product's supported duration. Runway pairs its terms with example outputs so a prompt can be checked against a documented reference first. None of the three vendors documents a numeric tolerance for a requested angle or move.

What the tool does not change

None of the three documents claims the control replaces a cinematographer's judgment about coverage, or guarantees that a repeated request produces the same result twice. Choosing which shot size serves a scene, matching a move to the beat of a cut, and deciding when a close-enough generation is unacceptable remain outside anything the cited pages describe the software as doing.

• Does the vendor's own documentation state a limitation for the exact shot type being requested?
• Has the control been tested across more than one generation to see whether the result is repeatable?
• Is the shot one the source material already flags as unreliable, such as a static wide or establishing frame?

Reading three vendors' camera-control pages side by side shows a shared vocabulary borrowed from set terminology, applied to an interface where static and establishing shots are, by Runway's own account, still the hardest instructions to satisfy.