Launch Video Versions: Design Before You Crop

Imagine that a product-launch film is already locked. It looks strong on the venue screen and the 16:9 replay works. The brand team then asks for a 9:16 cut and a silent-viewing version. The editor simply crops the landscape master: half the product disappears, subtitles cover the interface, and the emotional build collapses once the music is removed.

This is a hypothetical scenario, not an ONCE client case. It illustrates a structural risk in launch-screen and social-version delivery. The problem is not poor cropping. It is treating the master as one fixed-size movie file.

A more resilient approach separates the master into four manageable layers: story, picture, text, and sound. The venue screen, landscape, vertical, and silent-viewing versions can share the same product facts and major beats without being forced to share the same composition, subtitle density, or audio logic.

A master is an approved content system, not one export

Before approving a 1920 x 1080 file, the brand team should approve four layers:

• Story: when the product appears, how claims are sequenced, and which shot reveals or proves each point.
• Picture: where the product, hands, interface, graphics, and background sit, and which elements can move or be rearranged.
• Text: whether titles, claims, captions, and disclaimers remain separate enough to be rebroken, resized, and repositioned.
• Sound: whether music, narration, sync sound, and effects remain available as stems, and what takes over when viewers watch silently.

Once these layers are flattened into an indivisible timeline, multi-version delivery becomes a crop-and-scale exercise. If they remain adjustable through scripts, storyboards, and post-production, every output can preserve the same point without preserving the same layout.

That is why a version tree should come before the delivery folder: the team needs to know which changes propagate across every version and which belong to one destination only.

Ask the screen for resolution and the channel for aspect ratio

A launch-event screen should not be assumed to be 16:9. Ultra-wide canvases, split screens, irregular LED surfaces, and presenter zones can all require different pixel maps. The production team should obtain the real canvas dimensions, refresh rate, playback device, codec requirements, and a test file from the event or playback team before laying out the screen version.

The exported file is only one part of the result. Resolume's official guidance on 10-bit color output shows that the GPU, connector, cable, processor, and display all affect the signal chain. A pre-rehearsal playback-path test answers whether a file will play correctly at the venue. This article addresses a different question: whether the content still works when the frame changes.

Social outputs should follow the actual destination. YouTube's official guidance describes 16:9 as the standard computer ratio while adapting its player to vertical and square uploads. LinkedIn's current video-ad specifications include 16:9, 1:1, 4:5, and 9:16 options. Platform support for several ratios does not mean one landscape composition can be cropped mechanically into all of them.

A practical output matrix pairs dimensions with an editorial job:

• Venue screen: use the actual pixel canvas and align the reveal with stage action.
• 16:9 landscape: preserve the full spatial relationship for websites, replays, or media distribution.
• 9:16 vertical: rearrange the subject, product claim, and interface so the central action does not cross the crop boundary.
• Silent-viewing version: replace information carried only by sound rather than merely deleting the audio track.

Use three content zones instead of one universal safe box

One safe-area rectangle rarely serves an ultra-wide screen, 16:9, and 9:16 equally well. A more useful system divides each key shot into three zones.

Core information zone

The product, essential action, and most important claim sit where every planned version can retain them. This is the content that should survive every reframe.

Repositionable zone

Specifications, supporting titles, enlarged UI, and graphic accents can move, but they must remain separate assets. They may sit beside the product in landscape and stack above or below it in vertical.

Extension zone

Environment, lighting, particles, and non-critical background detail fill the outer frame. This zone may be cropped, but it cannot carry the only instance of an essential product fact.

Production needs to protect these options. Placing a presenter too close to the product, stretching a hand movement across the whole frame, or burning UI into the original footage turns vertical adaptation into repair work. Important launches may share performance and lighting continuity across ratios without sharing exactly the same camera position.

Captions and audio must each be able to carry the message

The venue version may use music, sound design, and the stage system to create a reveal. Social viewing may happen without useful audio. A silent-viewing version should let the audience understand what the product is, what is being demonstrated, and what happens next. That does not require turning every spoken word into wall-to-wall captions.

Separate three text jobs:

• Information text: product names, feature names, and necessary specifications.
• Narrative captions: the key causal points from narration, edited for reading rather than copied word for word.
• Compliance text: conditions, limitations, or disclaimers that cannot disappear just because the vertical frame is tight.

Audio should also remain layered. Keep the full mix, music, narration or dialogue, and principal effects separately available. If multilingual delivery is in scope, agree in advance on music-and-effects masters, subtitle files, and editable text layers. Silent cuts, localized versions, and later cutdowns should not have to reverse-engineer a flattened master.

Approve in an order that contains rework

Instead of reviewing a folder of many near-identical files at once, approve the system in sequence:

1. Approve the narrative master: lock the claim order, shot selection, and key rhythm before deriving ratios.
2. Approve critical landscape and vertical frames: review the product reveal, proof shots, and final call to action first.
3. Approve the text layer: check line breaks, size, on-screen duration, and compliance text; do not shrink landscape captions into the vertical frame.
4. Approve audio and the export matrix: confirm the venue mix, social mix, silent version, subtitle files, resolutions, and naming rules.

Four quick tests catch many failures: is any part of the product cut off vertically; can a viewer restate the main claim without sound; are captions readable at phone size; and has the venue version been tested against the real canvas and playback conditions?

When one master should not become every edit

A shared narrative master can unify product facts, but some projects should not force every destination to use the same cut:

• An ultra-wide stage animation depends on movement across the full screen, while a vertical viewer sees only a narrow slice.
• A venue reveal must wait for a presenter, lighting cue, or mechanical action, while the social version needs to reach the product sooner.
• Product UI, hand interaction, or small details require tighter coverage for vertical viewing.
• The landscape film primarily builds brand atmosphere, while the vertical cut explains one feature; their jobs are different.

In these cases, deliver more than new dimensions. Preserve shared product facts, visual language, and source assets, then create a distinct edit for each viewing task. ONCE's brand-film production approach can define ratios, captions, sound, and acceptance rules at script and storyboard stage.

If you are planning a launch film, venue-screen content, and post-event social cutdowns, contact ONCE VISUAL for a product-launch video plan that makes version requirements a production condition before the shoot, not a repair list after picture lock.