Should architects use the Veras gallery as a project archive?
No. Use the cloud gallery as a working space for generation, comparison and sharing, then export every accepted result into the project record with its source revision, prompt, engine, date and approval status. A visible thumbnail proves an image exists today. It does not establish retention, ownership of context or future retrieval.
A render is approved in a Monday call. By Friday it is still easy to find, sitting in a handsome grid between twelve near-misses. Six months later, someone asks which Revit option produced it. The thumbnail remembers the picture. The project folder remembers nothing.
That is not a cloud failure. It is an archive decision nobody noticed making.
What did Veras change about local saving?
Chaos's Veras 4.2 release note says the default local auto-save for images was changed to disabled, with renders saved to the cloud and available through the gallery. The current Veras Image Tab documentation describes Download as the action that saves a render result to the local machine.
Those two statements create a clear operational fact. A local file is now a deliberate action unless an office changes the default. Chaos does not say in those pages that the gallery is a permanent project archive, and ArchiGen should not invent a retention promise on the company's behalf.
The gallery has real strengths. Later Veras updates add storage-use indicators, share links, persistent source images and workflow history. Veras 5.3 says NODES workflows save to the cloud as users work, keep versions and remember which workflow produced a rendering. Useful memory is accumulating inside the product. It is still product memory.
A gallery and an archive answer different questions
| Question | Cloud gallery | Project archive |
|---|---|---|
| What can I compare now? | Fast thumbnail browsing | Selected milestones |
| Who controls access? | Account and vendor controls | Practice records policy |
| What is kept? | Product-defined items and metadata | Decision-defined package |
| How is it named? | Gallery title or generated order | Project, view, revision and status |
| What survives a tool change? | Unestablished by the cited pages | Files in the practice system |
A working gallery optimizes discovery. It wants the newest output nearby, a quick filter and an easy share button. An archive optimizes later proof. It wants a stable name, a source relationship, approval context and a retention rule.
The same image can belong in both places. The mistake is assuming the first performs the second job because it has thumbnails and dates.
When should a Veras image leave the gallery?
Do not download every experiment. That turns a clean project directory into a second, worse gallery. Export when the image crosses a status boundary: selected for development, issued for review, shown to a client, approved as a direction, used to instruct scene changes or placed in a formal deliverable.
Status is more useful than beauty. An awkward image that changed the facade may deserve a project record. A gorgeous discarded sunset may not. Our design-decision log follows the effect of an image rather than the volume of generation.
Export the source frame too when the generated image proposes a change. If the Veras result came from V-Ray, our VFB History method ties it to a named parent render. If it came from a BIM viewport, record the model revision and camera. The AI output alone cannot tell a future reviewer what it retained, moved or invented.
What belongs in the accepted-image package?
Keep the downloaded output at its original delivered dimensions and format. Add a small text or structured record containing project code, view, source file or revision, Veras version, image engine, prompt, reference-image identifiers, date, author or operator, approval status and the decision the image supported.
Where a seed is exposed, record it without promising perfect regeneration. Hosted models and wrappers change. The goal is to reconstruct the decision and its conditions, not swear that a cloud service will return identical pixels in 2028.
Name the pair before filing it. A pattern such as project_view_sourceRevision_verasEngine_status_date is not elegant, but neither is a coordination meeting devoted to six files called download(4).png.
Record the gallery item or share reference when one exists, yet treat it as a pointer rather than the record itself. Share links are built for access. They can be revoked, and recipients may clone shared items into their own gallery according to Chaos's Veras 4.4 and 4.5 update page. That is useful collaboration, not custody.
Should an office turn local auto-save back on?
Possibly, but automatic saving solves only file presence. It does not identify which image mattered, connect it to a source or record why someone approved it. A folder full of every attempt is a cache with ambition.
Auto-save makes sense where network access is uncertain, where a contractual requirement demands local capture, or where office policy forbids relying on one hosted copy during active production. Confirm storage paths, permissions and cleanup before deploying it widely.
Deliberate export is better for a decision-led archive because the action marks a status change. Pair it with a short approval step. The reviewer names the image, chooses its status, attaches the source and states what may be carried back into the model.
The right answer can be both: automatic local capture for recovery, deliberate promotion into the project archive for evidence. Do not call the recovery folder the archive either.
How does cloud storage change the studio policy?
The policy should name an account owner, define access when staff leave, state what project imagery may be uploaded and set a recurring export or closeout check. Our cloud upload gate covers what may enter. This archive step covers what must come back out.
Storage meters deserve attention as well. Chaos documents a live cloud-storage indicator and signals that teams may need to make space. A capacity warning is a poor moment to discover that the gallery contains the only copy of an approved option.
At project closeout, reconcile the gallery against the decision log. Download missing accepted images and their sources. Confirm that shared review links no longer expose work that should be private. Do not delete cloud items merely because a local copy exists unless office policy and project obligations authorize deletion.
ArchiGen's take: convenience needs an exit door
Cloud galleries are better than mystery folders on one workstation. They make comparison, continuity and sharing easier, and Veras is adding useful connections between sources, workflows and outputs.
The cleaner the gallery becomes, the easier it is to mistake access for custody. Architects know the difference in every other project system. The issue set is not the drawing archive. The live model is not the record copy. The pin-up wall is certainly not the records room.
Enjoy the wall. File the decision.
Evidence note: product behavior was checked on 27 October 2026 against Chaos's Veras 4.2 release note, current Image Tab documentation, Veras 4.4 and 4.5 update page, and Veras 5.3 release note. Cloud retention is deliberately described as unestablished by those cited pages. This is an editorial records method, not a report of ArchiGen hands-on testing.