Rendered vs Photographed 360 Virtual Tours
If the space exists and looks like what you are selling, photograph it. Render when the space is unbuilt, when it is under construction, when it is occupied by a tenant whose fitout will leave, or when you are selling an option that has never been built. The single non-negotiable rule either way is disclosure: a rendered panorama must say it is rendered.
Teams usually ask this as a cost question. It is really a question about what the viewer will conclude and whether that conclusion will hold up.
Both routes produce 360 virtual tours that look similar in a browser, which is exactly why the disclosure matters.
What each one can and cannot do
Photography captures what is there, including the scuffed baseboard, the fire extinguisher and the neighbor's parking lot. It is fast, it is credible, and it cannot show anything that does not exist.
Rendering shows the design intent, the unbuilt unit, the alternate finish package and the view once the trees mature. It costs more, takes longer, and depends entirely on the quality of the model and the finish information it is built from.
Choosing between them
| Situation | Choose photographed when | Choose rendered when |
|---|---|---|
| Finished, vacant space | Always; it is faster, cheaper and more credible | Only to show an alternate finish package |
| Under construction | Never; a shell reads as a worse building than it is | Always, until the space is finished enough to shoot |
| Occupied by an exiting tenant | The shell will convey largely as seen | The fitout is leaving and defines what a viewer sees |
| Pre-leasing before delivery | Not possible; nothing exists yet | Always; this is the core case for rendering |
| Selling options a buyer can choose | You have a built example of each option | The options have never been built together |
| Amenities finishing after the units | Once they open; replace the rendered set then | During lease-up, clearly labeled as design |
| Budget is tight and the space exists | Always; do not render what you can walk into | Never in this case |
The verdict
Photograph by default. Render only when there is nothing to photograph or when what exists actively misrepresents what you are selling.
Many real projects end up mixed: rendered units during lease-up, photographed amenities once they open, and a planned swap from one to the other. Scope that swap at the start rather than treating it as a surprise a year later.
The disclosure rule
Every rendered panorama says it is a depiction of the design. Not in a footer, not in the email that carried the link, but inside the tour where someone looking at that room can see it.
This is not caution for its own sake. A renter or buyer who arrives expecting the depicted finish and finds a different one has a grievance, and your tour is the evidence they will use.
Rendering has an input dependency photography does not
A photographed tour needs access and a date. A rendered tour needs a current model, a settled finish package and someone able to state which selections are committed. When those are not ready, the render waits, and that wait is the schedule surprise we see most often on this kind of project.
Not sure which half of your project is which? Send the delivery schedule and we will split the scope for you.
How to start
Walk your own building. Anything you can stand in and would be happy for a prospect to see gets photographed. Everything else gets rendered and labeled.
Related reading: how to brief a 360 tour project covers the inputs, retail centers covers mixed occupied and vacant space, senior living communities covers phased delivery, and how long a tour takes covers the schedule difference.
Send us your delivery schedule and we will tell you what to shoot and what to render.