Off-Plan Rendering: What Reaches the Buyer
Image co-authored with help of AI for illustrative purposes
Key Takeaways
- Off-plan rendering creates spatial information - unit data, floor plans, availability - that image-file delivery discards at the first handoff.
- A folder of render files means three separate vendors rebuilding what the 3D model already knew.
- Pre-rendered payload scales per view, not per unit. A 528-unit development carries roughly the same weight per screen as a six-house estate.
A 3D model of an off-plan development knows which unit is on which floor, what the kitchen looks like in oak versus walnut, whether apartment 4B is sold. When a studio delivers image files, all of that stays on the artist's workstation. What reaches the buyer is a website rebuilt from JPEGs, a kiosk that disagrees with it, and a sales team in the middle.
Four pairs of hands touch the render before a buyer sees anything. At most handoffs the deliverable is a file, and the spatial information stays behind.
What the architect's drawings leave out
What arrives at the studio: layouts, elevations, site plans, material specs. No photography. No real lighting to measure. No site to visit.
Everything in the 3D model has to be authored from flat drawings. This is what makes off-plan diffrent from rendering an existing building. The artist has no physical reference. The render is the first time anyone sees the building in three dimensions, including the developer who commissioned it.
What the studio ships: image files or the model
The artist builds the model in Unreal Engine, Maya, Cinema 4D, or Blender. Exteriors, interiors, floor plans, walkthroughs. Full scope, because off-plan needs all of it. Productized packages ship in 2-4 weeks. Bespoke projects take 2-3 months.
Then the chain forks.
Most studios export image files. Maybe an animation. The model stays. Everything it knows - which unit is where, what floor plan belongs to which apartment, what finishes are available, whether a unit is reserved - never leaves the studio.
The other path: ship the 3D project itself as a connected platform. The model drives the website, unit selector, kiosk, CRM. Data survives the handoff.
A folder of images becomes three systems
The marketing team recieves a folder of images and a video file. No unit data. No connection to the model.
They do competent work. Build a website around the images. A second vendor builds a CRM. A third builds kiosk app for the sales office. Three systems, maintained separately, none talking to each other.
The marketing team did nothing wrong. They got files, so they built around files. Fragmentation is a format problem, not a competence problem.
Three systems disagree in front of a buyer
The sales team inherits three systems that disagree. Website says a unit is available, it was reserved yesterday. Kiosk shows finishes from last month. An overseas buyer asks about a unit and gets stale information.
Someone generates a PDF brochure by hand. It is out of date by the time the buyer opens it.
The developer calls. Why is a sold unit showing as available? Sales team gets blamed. But the defect was introduced two owners earlier, at the studio door, when the deliverable was images instead of a connected system.
Ship the project, not a folder of renders
The fix is at the studio door, not at the sales team.
When the studio ships the project as a connected system instead of a folder, every owner downstream works from the same live source. Nobody re-enters what the model already knows. A unit that gets reserved updates once, everywhere.
Safa Al Fursan in Riyadh: 528 units, same 3D model from masterplan to apartment tours, on any device. River Residence in Bulgaria: buyer configures interior finishes from the same project. Only works because the data survived the studio door. Kownatki: 20 houses, three build stages, live availability per stage from one source.
Pre-rendering runs the heavy compute once, caches the result as video. We measured Malinowskiego at 1.81s, about 3.2 MB total. A quarter above a median mobile web page (Web Almanac 2025: 2.56 MB). Pre-rendered payload is per view, not per unit - each screen loads a cached clip regardless of how many apartments the development has. Safa Al Fursan's 528 units carry roughly the same weight per screen as Malinowskiego's six houses.
The trade: the artist chooses the viewpoints. Every angle is designed. For off-plan, where the developer controls how a building that does not exist yet is presented, that is usually the right call.
When plans change mid-construction, an interactive platform updates without re-commissioning. And the same 3D project produces every marketing output (what you own).
~103,000 sessions blended across 13 developments we host, July 2024 to July 2026. About 2 minutes on mobile, closer to 5 on desktop.
Source: Vinode measurement - as of
If you need a dozen hero shots for a brochure and you do not have units to manage, image delivery works fine. Connected platform pays off when the development has enough moving parts (units, stages, pricing, availability) that keeping them consistent across website, CRM, and sales office becomes its own job.
If you are commissioning a rendering project, the images will be good. That is not where this decision lives. It lives in what format you receive and how many systems your team builds around it before a buyer can browse a unit on their phone.
Ask what leaves the studio. A connected platform keeps one source, one update, one link from a buyer's phone to the sales-office kiosk.
See what leaves the studio
Open a live Vinode project on your phone. Unit selector, floor plans, interior tours - one link, any device.
Who keeps your property page current after launch, and how to be sure they can
Your development site launched perfect and went stale within weeks. The reflex is to blame the tool, but most stale-site failures are an unowned edit wearing a tooling costume. How to assign the owner, make the edit safe by construction, and run a cadence that tracks sales velocity instead of the calendar.
Real Estate 3D Model Ownership: Five Files, Five Different Answers
A real estate 3D model is a chain of assets, not one portable file. Name the working files, rights and dependencies before production starts.
Multi-language, multi-currency launches without price drift
Three weeks before an international launch, the same apartment shows three prices across the English, Spanish, and Arabic pages, because each is a hand-built copy and the number changed in only one. Multi-currency is a governance call before it is a feature: decide the one authoritative price, localize the language around it, and name exchange-rate risk instead of hiding it behind a live switcher.