Real-Estate 3D Video Formats and Where to Use Them

A 3D real-estate video should not be delivered as a single file that every team then crops in a hurry. To serve a scheme page, a campaign, a sales appointment and a sales-office screen, it needs to be planned as a system: a master film, reusable sequences, channel-specific versions, subtitles, preview images and consistent calls to action.

This guide is written for developers, architects and communication agencies who are briefing a 3D film or organising its distribution. It covers how to connect goals, formats, framing, sound, accessibility, sign-off and measurement, without promising an automatic commercial result. The starting point stays the same: decide what each version needs to convey, and what action it should lead to.

Give Each Real-Estate Video a Precise Job

Before choosing a length or an aspect ratio, write down the video's role in the buyer's journey. A version meant to build understanding may work before any plans are opened or contact is made. A loop meant for a sales-office screen can work with no sound and no interaction at all.

The brief should connect every video to an audience, a context and a next action. Avoid vague goals such as “create emotion” when they do not say what the viewer should actually take away. Replace them with observable priorities: place the scheme, show access to the central courtyard, explain the relationship between buildings, present an interior mood, or drive a request for availability.

Write One Mission Sentence per Version

For each deliverable, complete this sentence: “This video helps [audience] understand [information] in [context], then directs them to [action].” For example, a vertical version might show three features of the scheme and lead to its dedicated page, while a longer version might be used by a sales adviser during a presentation. Agree this sentence before final production.

Rank the Visual Evidence

Sort what the film needs to show into three tiers: essential, useful and optional. Essential elements can include the scheme's setting, its access points, a main façade and the spaces that carry its positioning. Useful elements reinforce understanding. Optional elements add mood, if time and approved material allow.

This ranking stops the film becoming overloaded, and protects the core message once a version is shortened. It also helps you choose which shots must stay in every cut-down version.

Build a Distribution Matrix Before Editing

A distribution matrix describes where the video will be shown, and under what conditions. Build it before the master film is signed off, not after — a late crop can cut off a building, a title, or an important piece of information.

Create one row per use: scheme page, campaign page or social post, sales-office screen, and any other planned placement. Note the expected action and who is responsible for publishing it.

Distinguish the Channel From the Real Viewing Context

The same channel can cover several viewing contexts. On a website, the video may start on a preview image and be launched deliberately. In a paid campaign, the first few seconds have to work with no prior explanation. On a sales-office screen, a loop may be watched from a distance and can start at any point.

Describe these conditions in the brief. State whether sound will be available, whether the viewer controls playback, whether the text will be legible on mobile, and whether someone will be present alongside the video. Editing, title density and pacing can then be adapted consistently.

Link Each Version to a Destination

A video rarely generates a request on its own. It should lead somewhere useful: a scheme page, a unit selection, a brochure, a form, a booking, or a conversation with an adviser — check that the link actually works. A given version can carry a different call to action, but that choice should be made explicitly, not added at the last minute.

Prepare a Master Built to Be Adapted

The master film should keep the best quality useful for archiving and for exports. It is not enough, though, to produce one large horizontal file and mechanically crop every version from it. The important areas need to stay usable across all the framings you plan to deliver.

Ask the studio to define, at storyboard stage, which shots will be cropped, shortened or reordered. A very wide composition can lose its subject once cropped to vertical. A fast camera move can become hard to read on a small screen. A title placed near the edge of the frame can disappear behind a platform's own interface.

Plan for Ratios Without Multiplying Films

16:9, square, 4:5 and 9:16 are common examples of distribution ratios, but the real usage conditions and specifications need to be confirmed at export time. Use safe zones for the building, the titles, the logo and any regulatory information. For a shot that is hard to crop, plan a dedicated camera angle or composition — and make that decision before the high-quality render, not during the final export.

Separate the Image, the Titles and the Interface

When titles are permanently baked into the image, every correction or translation forces a new export. Ask whether text, subtitles and graphic elements can be kept as separate layers in the edit project. That structure simplifies textless versions, additional languages and last-minute changes.

The logo should follow brand guidelines, but it does not always need to be on screen permanently. Decide whether it appears at the start, at the end, or over certain sequences, and check its contrast across the different moods used in the film.

Turn the Storyboard Into a Sequence Library

The storyboard organises the film's story. For multi-channel distribution, add a second layer to it: whether each shot can work as a standalone module. Name sequences by subject rather than by shot number alone — address, aerial view, façade, entrance hall, living room, terrace, garden, amenities, call to action.

This library lets you build shorter versions without distorting the film. It can also feed a presentation, an animated banner, or a later publication, subject to the rights and scope agreed with the studio.

Plan Clean Entry and Exit Points

A reusable sequence needs a usable start and end. If every shot is joined by complex transitions, pulling out a single module becomes difficult. Ask for clearly identifiable cut points and, where useful, a few extra frames before and after the main action.

Camera moves need to stay coherent when re-sequenced differently — a run of pans in opposite directions can tire the eye. Any edited version needs to be signed off, even if it reuses shots that were already approved.

Document What Can Be Reused

The sequence library should record the applicable licences and a change log. When a detail of the scheme changes, identify every affected version before exporting again.

A change to the logo, a status label or a call to action can affect several files at once. The log should state where the request came from, who approved it, and which outputs need updating.

Being technically able to reuse a sequence does not automatically mean you are authorised to. Rights, licences and usage periods need to be checked by the relevant people before a new campaign, or before distribution in a different territory.

Treat Sound and Subtitles as Deliverables in Their Own Right

Sound can set a mood, support pacing and clarify a message, but part of your audience will watch with it off. The video needs to stay understandable through the image, useful titles, and subtitles wherever speech carries information.

Accessibility guidance for audio and video content distinguishes subtitles, transcripts and audio description — these are not interchangeable. The brief should specify which of them are needed for the intended uses, and who is responsible for approving their content.

Write for the Ear

A voice-over should not repeat every title word for word. It can add context while the image shows the project. Keep sentences short, easy to pronounce, and synchronised with the relevant shots. Proper nouns, figures, addresses and technical terms all need careful checking.

Prepare a version of the script with timecodes and pronunciation notes. If several languages are planned, confirm the space available and the real recording length for each before locking the edit.

Provide Separate Subtitles and a Burned-In Version

Subtitles are best understood as a synchronised transcription of speech and any necessary sound information. A separate subtitle file lets the viewer switch them on and makes corrections easier. A burned-in version can help where a channel does not reliably display subtitle tracks.

Ask for both only where the context genuinely calls for it. Check legibility, contrast, synchronisation, and that nothing overlaps with titles or interface elements. An unreviewed automatic subtitle file can introduce errors into the scheme's name or its sales information.

Organise Exports and Delivery Files

A clear delivery separates the master, the distribution versions, subtitles, preview images and archives, in line with the contract. Every file should be identifiable without having to open it.

Agree a naming convention that covers, at minimum, the scheme, the channel or ratio, the language, the duration or role, the version, and the date. Avoid names such as film_final_v2_definitive. The publishable status should be obvious, and only one active version should sit in the distribution folder.

Describe Each Export in a Technical Spec Sheet

For every file, record its dimensions, ratio, frame rate, codec or container, whether it has sound, whether it has subtitles, its target file size, and its destination. Exact settings should be confirmed with the relevant platforms or integrators at the point of delivery.

Add a deliberately chosen preview image rather than a random frame. It should represent the scheme, stay legible at the sizes it will be shown at, and respect the framing of its channel. Also check the title, description and alt text used around the video on the site.

Keep a Master and a Version Log

The master should never be replaced by a compressed version pulled back from a platform. Archive it together with the script, the list of approved shots, the relevant licences, and the change log. When a detail of the scheme changes, identify every affected version before exporting again.

Embed the Video Without Blocking the User Journey

On a scheme page, the video needs to sit within the content hierarchy. It can complement the rendering, the site plan, the sales plans and the contact form, but it should never block access to essential information.

Plan an optimised preview image, a clear play control, accessible controls, and a fallback for when the video fails to load. The video should not consume bandwidth before the visitor shows an intention to watch, unless that is a deliberate, tested technical decision.

Check Playback on Mobile and on a Constrained Connection

Test the page at several widths, with and without sound, after rotating the screen, and on a slow connection. Check how quickly the preview image appears, the size of the controls, and how full-screen mode closes and returns to the page.

If a lightweight or adaptive version is planned, verify that the server actually delivers the expected file. A well-compressed video is useless if a script or player still blocks access to the form or the plans.

Keep a Useful Text Alternative

Add a written summary of the main information and, where spoken content matters, a proper transcript. This alternative helps people who cannot watch the video, as well as anyone who simply wants to find a piece of information quickly.

The text should never invent a feature that is absent from the approved documents. It needs to stay consistent with the film, the page and the sales materials around it.

Measure Distribution Without Confusing a View With a Conversion

Define the events worth tracking before the video goes live: the player being displayed, a deliberate launch, progress through the video, completion, a click on the call to action, the traffic source, viewing of supporting content, a form being opened, and a confirmed submission. Only compare versions when the audiences, time periods and destinations allow for a fair reading.

Build a Readable Tracking Plan

Name events and parameters consistently. Add the version identifier, the channel, the language and the position on the page where that data is useful and permitted. Document what triggers each event, so a simple display is never counted as a play.

Keep the dashboard split between consumption indicators and commercial indicators. Watch time, completion rate and version choice describe usage. Qualified contact requests and confirmed appointments describe a different, later stage.

Test the Video and Every Version Before Release

Testing does not stop once the master film is approved. Every export can introduce an incorrect crop, a mistimed subtitle, the wrong destination link, or excessive compression. Check the files that are actually going to be published.

Build one test scenario per channel: open the page or the ad, spot the preview image, launch the video, turn on subtitles, check the information shown, reach the call to action, and confirm the destination. On screens with no sound, check that the main message is still understandable.

Pre-Launch Checklist

• The mission, audience and next action are defined for every version.
• Ratios and safe zones were planned before the final render.
• Essential shots stay legible in every crop.
• The script, proper nouns and scheme information are all approved.
• Rights for music, voices, fonts and brand elements are checked.
• Subtitles are reviewed, synchronised and tested in context.
• Exports, preview images and subtitle files follow a clear naming convention.
• The web version is tested on mobile and on a slow connection.
• Links and calls to action lead to the right destination.
• Measurement events distinguish playback, engagement and contact.
• The master and the version log are archived.

To brief production, see Vizion Studio's 3D animation film service. If your distribution matrix and reference documents are ready, send them to Vizion Studio to define the master film, the versions needed, and the sign-offs expected at each stage.

FAQ

Do I need a different video for every channel? Not necessarily. A master film and a sequence library can feed several versions. That said, every variant still needs to be edited and checked for its own ratio, viewing context, message and call to action — automatic cropping is not always enough on its own.

Which ratios should I ask the 3D studio for? Only the ones matching your confirmed channels. 16:9, square, 4:5 and 9:16 are common examples, but the exact requirements need to be verified at export time. The storyboard should anticipate safe zones and any shots that are hard to crop.

Does the video need to work without sound? Yes, for any context where sound may be off or unavailable. The image, useful titles and subtitles need to carry the main message. A version built for an accompanied presentation can rely more on spoken narration.

Should subtitles be burned into the image? It depends on the channel. A separate file allows the viewer to switch them on and makes corrections easier, while a burned-in version guarantees they appear even where the player does not manage subtitle tracks. A brief can plan for both, with legibility and synchronisation checked for each.

What should be archived after delivery? Keep the master, the publishable exports, the subtitles, the preview images, the script, the version log, and any necessary rights information. The contract should state whether project files or 3D source scenes are part of the delivery.

How do I know whether the video is generating requests? Set up a measurement chain linking the traffic source, playback, subsequent interactions, and a confirmed form submission. A view or a completion shows that the content was consumed, not that it converted on its own — analyse qualified requests together with their context and distribution version.