Photographs are essential to an architectural portfolio, but they cannot always show how a space feels as someone moves through it. A short walkthrough can reveal the sequence from an entrance to a living area, how daylight changes across a room, or how materials look together at a natural viewing distance.
At Minerva Designs, we want project videos to do more than create a quick social-media impression. They should help clients understand design decisions, respect the privacy of the people who use each space, and remain available to our team after a post has disappeared from view. Here is the workflow we plan to follow.
Start with the story of the space
A walkthrough works best when it has a purpose. Before filming, we would choose two or three details worth explaining: perhaps the transition from a shaded entrance into a bright interior, the relationship between a seating area and an outdoor view, or the way lighting changes the appearance of stone and wood.
Our Stone & Shadow residence is an example of a project where movement could add context to the photographs. Its stone geometry, recessed surfaces, warm accents and lighting are easier to understand when shown as a sequence rather than as isolated details. A video should complement the project page—not replace its photographs, plans and written description.
Film with permission and a simple shot list
Before recording a completed home or commercial space, we would confirm what the client permits us to show and where the video may be published. A social-media post is a different use from an internal progress record. We would also check the frame for people, family photographs, documents, screens, addresses and other details that should stay private.
A short shot list keeps filming focused:
- Open with a view that establishes the space.
- Move through the main route at a steady pace.
- Pause on two or three design details.
- Finish with a wider view that puts those details in context.
We would capture a little more footage than the final edit needs, while avoiding repeated shots that do not teach the viewer anything. Clear framing and steady movement matter more than elaborate effects.
Make the video useful without sound
Many people encounter a video with the sound off. Brief captions can explain what they are seeing—for example, why a wall was recessed or how a lighting detail changes the room after sunset. Those captions should be readable on a phone and should not cover the feature being discussed.
If the video includes speech or music, we would review it before publishing. The audio should be clear, and any music or other third-party material must be used with the appropriate permission. We would also write a post caption that identifies the project and gives viewers a reason to visit its full portfolio page.
Keep the original before posting anywhere
The camera or editing export—not a copy downloaded from a social platform—should be our master file. We plan to save that original in an organised project folder, together with the final edited version, approved captions and the client’s publication permissions.
A filename such as project-name-walkthrough-final-2026.mp4 is more useful than final-video-2-new.mp4. It tells another team member what the file contains without opening it. We would keep a second copy in a separate storage location and make sure the team knows which version is approved for public use.
Social platforms may resize or recompress an upload. A downloaded post can be handy for checking what viewers actually received, but it should never be the only surviving copy of a project video.
Treat social posts as distribution, not storage
Once a walkthrough is approved, it could be shared in formats suited to the platforms our audience uses. A vertical excerpt may introduce the project, while the full project page can hold the photographs and details that need more space. We would link viewers back to that page when it adds useful context.
If we later publish a walkthrough as a public Threads video post, we may want to keep a copy of the published version for our posting records. A Threads video downloader for public MP4 posts can help retrieve a source-available version. We would use it only for our own posts or videos we have permission to save. Available formats and quality depend on what the public post exposes; an HD option is not guaranteed.
That downloaded copy would help us review the published post. Our original approved export would remain the archive copy.
Review the result after publication
Publishing is not the end of the process. We would open the post on a phone and a computer to check that the first frame is clear, captions are legible, the crop does not cut off an important detail, and the linked project page opens correctly. If a client requests a correction or removal, the team should know where the post was shared and who can update it.
A useful walkthrough gives people a better understanding of a space. A useful archive gives the team confidence that the video, its permissions and its final version can still be found later. We want both parts of the process to be as carefully considered as the project presentation itself.
