3D ARCHITECTURAL ANIMATION

Real-Time Archviz vs Rendered Video: What Clients Actually Get

7 min read

Real-time archviz vs rendered video sounds like a technology comparison, but for the person paying, it’s really a purchasing question: one of these is a file, and the other is software. A rendered animation arrives as a video — it plays identically on every screen forever, uploads anywhere, and never asks for hardware. A real-time experience arrives as an application that has to run somewhere, every time someone uses it. Almost every disappointment we’ve seen in this corner of the market traces back to buyers not being told that difference up front. So here it is up front — with the logistics, the honest cost picture, and a decision test at the end. (For what walkthrough production itself involves, our 3D architectural walkthrough guide covers both formats from the service side; this article is strictly about which one to buy.)

A contemporary building at blue hour, sharp against foreground pedestrians and traffic streaked into motion blur

What “real-time” actually ships as

An Unreal Engine archviz project — the dominant route, fed by Datasmith imports straight from Revit, Archicad, SketchUp Pro, or Rhino — can reach its audience three ways, and they have very different demands:

  • A packaged Windows application. Installed on a sales-office PC or presentation laptop. No streaming bill and nothing to pay per viewer — but it needs a machine with a serious graphics card, and every design update means redistributing a new build. Epic publishes no universal spec because it depends entirely on the scene; plan on gaming-class hardware, not the receptionist’s desktop.
  • Pixel Streaming. The application runs on a cloud GPU and streams to any browser — per Epic’s own documentation, viewers need no install and no hardware beyond a phone or laptop. The trade is an ongoing bill: published pricing at Vagon Streams runs $0.025 to $0.047 per streaming minute per session — roughly $1.50 to $2.80 an hour, each — plus $0.67 a day per region to keep the application hosted. A hundred remote buyers exploring ten minutes each is real money, monthly, for as long as the campaign runs.
  • A VR build. Headset-based, maximum wow per square meter of sales suite, and the narrowest reach: each headset immerses one viewer at a time, and while multi-headset and shared sessions are entirely buildable, most sales-suite deployments run one guided seat.

One cost that never shows up in these comparisons, and belongs in yours: Unreal itself. Epic’s engine is free while you stay under $1 million in gross revenue over the past twelve months. Above that, the licence follows how the work is distributed: an application that relies on engine code at runtime and is licensed to third-party end users takes Epic’s royalty route instead of seats, where “all lifetime gross revenue above $1M that is directly attributable to the UE product” carries a 5% royalty. Other commercial work — which is where most studio archviz sits — needs seats at “$1,850 per seat per year” on Epic’s US list, before tax. Epic’s own examples of seat-based work name “architectural visualizations” and “interactive architectural walkthroughs” outright. It is not a fee you pay directly; it sits in the studio’s cost base. But it is one reason real-time work prices the way it does, and worth knowing about when a quote looks high next to a rendered animation. Epic has changed these terms more than once, so check unrealengine.com/license for the current position.

One myth to retire: stock Unreal has no first-party web export. Epic moved HTML5 packaging out of the engine at Unreal 4.24 and no longer supports it, so when a vendor promises the Unreal experience “in the browser”, the practical route behind that promise is streaming, with streaming’s costs — a custom WebGL rebuild is a separate engineering project, not an export button. That single fact reframes most sales conversations about interactive archviz.

A photoreal apartment interior with a curving trail of gold light showing the path a camera swept through the space

Real-time archviz vs rendered video on cost

Rendered animation has published, comparable market rates: Visiofy’s February 2026 guide tells buyers to “expect to pay between $100 and $300 per second of footage” for high-end cinematic animation — which is $6,000 to $18,000 a finished minute, a reminder to convert before you compare anything. Its own FAQ puts the average “per minute of animation” at $8,000, and its wider band for animation work at $2,000–$20,000 a minute, with stills and 360 panoramas cheaper still. Note that the same page’s tier table runs wider than its headline — $50 a second entry-level up to “$500+” boutique — so even a single vendor’s guide disagrees with itself, which tells you how much precision these numbers really carry: treat it as one studio’s published guide, not a market benchmark. Interactive real-time work has no equivalent benchmark, which is not the same as having no published prices. Named studios do publish them — Skanda Designs lists a 360° panoramic still at US$1,500–$3,500, a pre-baked VR tour of one apartment at US$8,000–$25,000, and an interactive Unreal sales experience with configurable layouts and materials at US$60,000–$250,000+. The problem is that none of those share a unit: per panorama, per apartment, per project. There is nothing here you can line up against dollars-per-second the way you can with animation, and any single “market rate” for interactive work is false precision. Skanda puts the reason plainly: “real-time work is priced as software engineering, not as imagery — expect a discovery phase, a build phase and ongoing maintenance.” The price moves with the number of units, options, finishes, interactions and deployment requirements, not with runtime minutes. The one qualitative point we found published — a studio commentary, so read it as vendor-adjacent, though it matches what we see — is that the real-time build costs more up front and pays back in reuse — unlimited viewpoints, day-night states, and option combinations from one build, where every video change is a new render bill. Both statements are true, which is exactly why neither format simply “wins.”

The quality ceiling, in the engine vendor’s own words

Real-time imagery in Unreal 5.8 — Lumen global illumination, Nanite geometry — is remarkable, and it’s the fastest-improving thing in this industry. It is still not the top of the quality range, and you don’t have to take a rendering studio’s word for that: Epic’s own documentation positions the offline Path Tracer as the “physically correct and compromise-free” option, for “final shots and ground truth comparisons against the real-time rendered scenes”. The engine vendor itself draws the line between interactive framerates and final-pixel imagery. In practice that means the campaign film, the billboard still, and the hero shot stay rendered; the exploration layer — walk anywhere, toggle finishes, check the view from unit 14B at sunset — is what real-time is actually for.

The decision test

Skip the format debate and answer four buyer questions:

  • Who’s the audience? Broadcast reach — ads, social, portals — is a video’s home turf; a file travels where software can’t. A defined pool of serious prospects who need to explore options favors real-time.
  • How many variants? Run this one as arithmetic, not preference. Video pays per combination: every finish package or unit type you want shown is another render bill, forever. An interactive build prices the variants once, inside the build. A single fixed design keeps video cheapest; a large option matrix flips the math — count yours before choosing.
  • Where does it get used? Staffed sales suite: packaged application. Remote and international buyers: streaming, priced as an ongoing campaign cost, not a one-off.
  • What’s the budget shape? Video is a one-time production cost: pay once, keep the file forever. Streamed real-time adds an ongoing usage-and-hosting component — beautifully flexible, never free to keep running.

And the option our own walkthrough guide already argues for, worth repeating in cost terms here: the formats share a model. The same source model and design data can yield the rendered film first and a real-time archviz build later — sequencing the spend instead of choosing sides. Reuse cuts the second format’s cost; it does not remove it, because a real-time deliverable still needs optimisation, interactions, performance work and deployment on top of the shared assets. If the interactive route is where you’re heading, what a 3D interactive presentation is maps that side in detail, and for the video side, our architectural animation cost guide breaks down the per-minute math.