Three approaches produce investor renders from the massing model you already have, without commissioning a studio: AI rendering from the view you have open (Chaos Veras), a renderer computing every camera from one scene (D5, Twinmotion, Enscape), or a 3D scene with attached photographs supplying the surfaces (Intangible). Two other routes sit outside that set. Blender asks the most rendering craft and costs nothing: the project states you are free to use Blender for any purpose, including commercially or for education. A freelance visualizer supplies the craft for you and charges for it. Which of the three fits turns on one question: does anyone on your team light a scene?
The pressure is financing. The Globe and Mail reports that Canadian banks typically require condo developers to presell about 70 per cent of their buildings' units before providing construction financing, a threshold those developers are lobbying to lower. The images exist long before the building does.
The priced benchmark for all of them is the commissioned studio: one firm prices exterior and interior stills at $400 to $1,500 per image for small projects, and $1,200 to $5,000 for large exteriors.
| Approach | How the next camera gets made | What it asks of you | Published price |
|---|---|---|---|
| Per-view AI generation (Chaos Veras) | Re-derived generatively from a view of your model | You drive consistency across the set | Chaos lists Veras from $16.90 a month for Starter, $29 for Pro, billed annually; Veras AI is also included with Enscape Solo and above |
| One-scene renderers (D5, Twinmotion, Enscape, plus its Envision companion) | Computed from one scene, so the images agree | Scene setup in the host app: materials, sun, camera | Chaos lists Enscape Solo at $47.90 a month billed annually; D5 lists Pro at $38 a month or $360 a year, with a free non-commercial Community tier; Epic lists Twinmotion free for companies under $1 million a year in gross revenue, and $445 per seat a year above that |
| One 3D scene, generated surfaces (Intangible) | Read off one scene every camera shares, with surfaces from attached photographs | Judgement on every frame, since its documentation states fidelity to references varies by model | Intangible lists Free at $0, Explorer at $35, Business at $65 a month billed monthly, with an annual option; 3D asset import needs a paid plan |
Chaos states Veras reads your active 3D view directly in its host, with no file transfer, and that a native Revit plugin draws directly from your model data, which it says preserves geometry, camera views and material assignments. It lists Veras across seven native hosts plus a web app, and inside Enscape, V-Ray and Corona. For set consistency it documents reference-image feedback, presets, rotation controls, a render seed on engines V4 to V6 with Reference Images replacing it from V7, and Design Lock, which replicates detailing and trim profiles, among other elements, without altering primary structure.
All the one-scene products batch across cameras: Enscape documents batch rendering across saved Views, Envision render queues across selected camera views, D5 a render queue for multiple jobs at once, and Twinmotion media you can export several at the same time. All sync from the host app: D5 live syncs with eight hosts including Blender, Rhino, Revit, SketchUp and Archicad, Twinmotion's Datasmith Direct Link syncs automatically or in one click, and Envision through Chaos Bridge. Intangible documents giving its visualizer the actual 3D scene and camera, so composition stays where you put it while the model varies the surface.
Before buying, check what you hold. Chaos includes Veras AI in Enscape Solo and higher, with 100 Chaos AI credits monthly on Solo and 1,500 on Collection, and Collection carries Envision, whose still images suit presentations, marketing, and design reviews. If a one-scene renderer is already on an office machine, use it: it wins on control, repeatability and output size. Enscape documents resolution up to 8192 x 8192 pixels, D5 custom sizes up to 16K, and Twinmotion images up to 64K (61440 x 61440), which Epic documents reaching through a tiled export that is not limited by GPU memory. The test: ask whoever last opened one whether they can light a scene to presentation quality. The generated-surface path earns its place when the answer is no.
On price the generated-surface path is not the cheap option, and for this reader it is usually the most expensive. Blender is free. Twinmotion is free for a practice under $1 million a year in gross revenue, which covers most boutique firms, and D5's Community tier is free for non-commercial work with Pro at $38 a month or $360 a year. Veras Starter is $16.90 a month. Intangible's Explorer is $35 a month and its Free tier cannot run this workflow at all. So the case for the third path is not cost. It is time: a renderer pays back over a second project, not a second image, so buying or learning one wins when somebody in the office wants that skill and has time to build it. Where nobody does, the trade is a subscription plus a learning curve against a subscription plus photographs.
Export the massing model to a mesh. All four packages here write one: Autodesk documents Revit exporting FBX from an open 3D view, Trimble documents SketchUp Pro exporting FBX, McNeel lists OBJ and FBX among Rhino's export types, and Graphisoft documents saving Archicad to FBX, plus OBJ, on current versions.
Bring it in. Intangible's answers page says it supports importing your own 3D assets and CAD in FBX, OBJ, DXF, and GLB, binds references so they stay faithful across every angle, and exports to image, video, or glTF. Its help pages disagree on DXF, and the ones addressing behavior put plans in as line geometry, so send FBX, OBJ, or GLB. The same page carries the soft vertex limit, roughly 280,000, above which models can fail to import, and the fact that materials are stripped on import; the CAD-to-render page walks that part end to end.
Build the site around the building. An investor reads the block as much as the building. Photograph the neighbors, the glazing you are specifying, and the paving, then attach them as image references, which Intangible's documentation describes as locking an object's appearance to that photograph at render time. Two documented traps: a reference does not override composition, and object names feed the prompt, so a specific name makes the model render its own idea of that thing over the reference. Name objects generically and let the photograph carry the identity.
Set all six cameras, then generate. Intangible's documentation states a shot stores its own camera position, lens, and aspect ratio and can be duplicated and reordered, with one caveat there: reordering does not update the auto-prompt history, and rendered images keep their original shot numbers in metadata, so if you care about file naming, rename instead of renumbering once renders exist. Its answers page says that because every shot comes from the same 3D scene, composition and references hold across angles instead of each frame being regenerated; for lighting, its help documentation puts consistency across a sequence on reusing one preset. Generate one shot and check silhouette, floor count and setback against the drawings before building the rest.
Six images, each with a job in the room, for the principal or developer who fundraises on projects years from breaking ground. The angles will look familiar. What each has to prove, and where the set stops, is the useful part.
A seventh angle of the same elevation reads as one good image repeated.
These renders are not construction documentation and carry no dimension anyone should build to. Keep the geometry locked to the design, let generation handle light and material, and label them concept renders subject to change.
A studio is still worth commissioning for art direction and asset build: the entourage, the bespoke landscape, the material study nobody in the office has time to model.
Output size is a real limit on the generated-surface path. Intangible lists image renders at 1K and 2K, 2K costing roughly twice the credits of 1K on the same model with the ratio varying by model provider, which covers a slide and falls short of a hoarding. For budgeting, its pricing page sells 1,000 credits for $10, about 170 1MP images, which puts the Free plan's 150 credits at roughly 25 images, and its documentation warns there is no live cost preview at render time. Its pricing page lists watermarked downloads on the free plan and watermark-free downloads on paid plans. Two of its surfaces disagree with that reading: the enterprise architecture page advertises a flat fee with unlimited renders, and the help documentation names the free-plan restriction as Generate 3D Asset while the pricing table marks 3D asset import unavailable on Free. This page follows the pricing table.
Only the studio route publishes a number: that rate card lists stills at 2 to 7 days for small projects, rising to weeks on large ones. The one-scene renderers sync live from the host app, per their own sync documentation above, so a first look is immediate once a scene exists. The other two paths have vendor marketing and no benchmarked figure: Intangible's architecture page advertises minutes per variation and CAD to a walkthrough in an afternoon, which is the vendor's own claim. The labour is front-loaded into building the scene once, so the sixth image takes far less of your time than the first, though metered credits still charge per render.
A plan alone will not render as a building, since linework carries no mass. Extrude it to a massing model in whichever package drew it, then export a mesh.
Accurate on what an investor checks: massing, floor count, setbacks, the parcel line, and the relationship to neighbors. Facade detail and fitout can come from image references.
Re-import; the documentation shows no way to edit in place. Intangible's import documentation describes Smart Import bringing a model in as a new asset, scale and orientation set on the way in, and documents no path for revising an imported mesh. Its Swap Model dialog opens scoped to the asset's category, though the same page says its search bar reaches across all categories; either way it is a different job. One thing survives: that page states swapping a model does not clear its image reference.
