This is not a gotcha about a typo. It is a small, checkable example of something that will cost you money the next time a renewal quote lands: the public record of what shipped in which version of an AI rendering tool is unreliable, and almost nobody checks it before deciding whether an upgrade is worth paying for.
Here is what today's sweep turned up, all four captured 21 July 2026.
Three sources, three numbers
The Chaos blog post comparing six AI rendering tools states that Veras 4.0 introduced Image-to-Video, which transforms still renders into motion. That is the vendor writing about its own product.
Archinect's news piece, headlined around an image-to-video tool for architecture being unveiled by Chaos, says the Veras 3.0 update allows users to transform static renderings into animations using text prompts. That is a serious trade outlet reporting a launch, which is normally the most reliable kind of source you can get, because launch coverage is written at the moment the thing actually appears.
Architools, a reseller, runs the headline "Chaos Veras 4: AI rendering for architecture gets a major update" and describes gains in output quality and prompt adherence. Meanwhile the current product page describes Veras as turning 3D models, 2D drawings and sketches into visuals and animations, with no version number attached at all, and a video review circulating this month asks whether Veras 4.5 is worth upgrading to.
So: 3.0, 4.0, 4, and an unnumbered product page, for one capability, in a product now on 4.5.
Announced, shipped, and quietly rebuilt
The interesting part is that both of the specific claims can be honest at the same time.
A feature in this category has at least four dates. The date it was announced, often at a launch event with a demo reel. The date it appeared in a build you could install. The date it stopped being flaky enough to use in front of a client. And the date, usually unmarked, when the model underneath was replaced with a better one and the feature kept its old name while becoming a different thing.
A version number is a marketing artifact at least as much as an engineering one.
Archinect was almost certainly writing about the announcement. Chaos, a year or more later, is describing the version where the feature became worth putting in a comparison table. Neither sentence is a lie. But a roundup writer skimming for a bullet point picks whichever page they landed on, states it flatly, and the next roundup copies that. Two hops later it is just a fact with no date on it, which is the same problem we ran into with roundups whose URL slug gives away the year they were really written.
Compounding it, this product is sold through at least three different vendor pages, and a reseller updates its marketing on its own schedule, not the developer's.
Why this costs you money
Four ways, in rough order of how often we see them.
You skip an upgrade you needed. Someone in the office reads that motion arrived in 3.0, checks that the office is on 4.0, and concludes the capability is already sitting there. It might be, in a form that was rough at the time. The 4.5 question never gets asked properly.
You buy something you already own. The mirror image, and the expensive one. A separate motion tool gets added to the stack, or a competitor gets a seat, to do a job the existing licence covers. Nobody audits this, because it does not throw an error, it just quietly appears on the card statement next to everything else in the subscription pile.
You cannot make the case at renewal. Whoever signs the invoice asks what changed since last year. "Better output quality" is not an answer that survives a finance conversation. A dated list of what arrived in which release is.
You plan a project around a capability that is not in your build. This is the one that actually hurts, because it surfaces on a deadline. It is the same failure as stale compatibility listings, arriving from the opposite direction: there, the page says a host version is supported when it is not; here, the page says a feature exists when your installed build does not have it.
How to establish what you actually have
Ten minutes, once, before any upgrade decision. In this order.
| Step | What you do | What it settles |
|---|---|---|
| 1 | Open the tool. Read the version in Help or About. | What is installed, as opposed to what was purchased or what the website is currently advertising. |
| 2 | Find the vendor's own changelog or release notes page, not a blog post and not a comparison table. | The only source with an incentive to be precise about version numbers. |
| 3 | Press the button. Try the capability on a real model. | Whether it exists in your build, and whether the version you have is the good one. |
| 4 | Write down the answer with the date you checked it. | Next year's renewal conversation, and the colleague who asks in October. |
Step three is the one people skip, and it is the only one that cannot be wrong. Everything else is reading. If the question is whether your seat can turn a still into a clip, the fastest route to certainty is to spend a few credits turning a still into a clip. If it produces something, you have it. If the menu item is not there, you do not. We have written the checklist for judging the output separately, and separately again on where this particular feature earns its keep and where it hands the job back to your render engine.
When sources conflict and you cannot test, prefer the one that is dated and specific over the one that is confident and vague. Launch coverage beats a comparison table for when something appeared. A vendor's current page beats launch coverage for what it does now. Neither beats the About box.
The wider record
Worth saying plainly, because it is not really about Veras. The history of this software category is being written mostly by pages with a commercial interest in the answer and no visible publish date, and the tools change fast enough that a claim goes stale in months. Version history is the part of that record you would expect to be solid, because it is the most factual thing there is: a number, attached to a build, on a date. If that is drifting, treat everything softer with the suspicion it deserves.
The 4.5 release itself is a decent case for reading changelogs directly. It is an unglamorous update, mostly selection behaviour and sharing, and the roundups have largely not caught up with it at all. The gap between what shipped and what the internet says shipped is currently about one release wide.
Our take
Nobody needs to settle the 3.0 versus 4.0 argument. The useful conclusion is smaller and more annoying: you cannot outsource knowing what your own software does.
The office that gets upgrade decisions right is not the one that reads more comparison posts. It is the one that keeps a plain text file listing each tool, the version installed, the date it was last verified, and one line on what changed. That file takes twenty minutes a quarter and it is the difference between arguing for a renewal with evidence and arguing with adjectives.
Check the About box. It is the only page in this whole category that has no reason to lie to you.
Written from the 21 July 2026 intel sweep. Version attributions quoted are as published on the Chaos blog, Archinect, Architools and the Chaos product page as captured on 21 July 2026, and may be corrected or reworded by their publishers without notice. This piece deliberately does not adjudicate which release first shipped image-to-video; the point is that four current sources disagree, and that your installed build is the only authority that matters for a purchasing decision.