Free tool: runs in your browser
AI visualization handoff checkerbefore you send a generated or assisted view
TimeBinder adds a layer of protection against AI and human fraud and disputes. Label the view, keep the source model, and check what a client or planner might assume.
Nothing you tick is sent anywhere. This page does not scan the image and it is not a tool for identifying generated media.
Check a visualization before you send it
Tick what is true of the view you are about to share. You get a shareable result and clear next steps. The image itself is not sent to TimeBinder, because this page does not ask for the file.
Your choices stay on this page. Nothing you tick is sent anywhere or tied to your name.
Tick everything that is true of the visualization you are about to send
This looks at how the view is labelled, what source files you still hold, and what a client or planner might assume. It does not scan the image, and it is not a tool for identifying generated media.
What to do now
How should I send an AI-assisted architectural visualization? The short answer
Label it as a concept, a study or a generated view. Keep the source model or the earlier drawing, and check dimensions against that model, not against the render alone.
This checklist scores those points. It is not a tool for identifying generated media. A TimeBind of the exact file you send can show that file existed no later than a recorded time and still matches. It does not show who designed the work.
Why this came up in October 2026
In October 2026 Google showed Gemini 4 Argon, starting from a single Nano Banana image, driving Blender to build a finished 3D Gothic cathedral, iterating on geometry, textures and lighting. Google's own product blog, published on 13 October 2026 when the model was released more widely, describes that workflow. On 12 November 2026 the X API reported more than two thousand likes on Google DeepMind's post of the demo, and more than three hundred thousand impressions on Google's own post of the scene.
A photoreal visualization can be a useful study. It is not a photograph of a built work, and it is not a construction or planning document unless it has been checked and issued as one. This page does not embed the demo. The checks are written so they work for the next view you send to a client, a jury or a planner.
Sources: Google DeepMind's 23 October post, Google's 22 October post, and the Gemini 4 Argon product blog, 13 October 2026.
What this checker does and does not do
The honest job of this page is to slow down a handoff, not to label a file as fake or real.
| Part | What it does | What it does not do |
|---|---|---|
| A clear label (concept, study, generated view) | Reduces the chance a recipient treats the file as a photograph or as an approved design. | Change how a third party later describes the image. |
| The source model or earlier drawing | Gives you something to check dimensions and materials against. | Verify the visualization by itself. |
| An unofficial detector score, or a missing watermark | Reminds you that those signals are weak on their own. | Identify generated media, or clear a view as accurate. |
| A TimeBind of the file you send | Records that an exact file existed no later than a recorded time and still matches. | Show who designed the work, or turn a visualization into a construction document. |
If the visualization is yours to send
Before it leaves your studio:
- Label the view, and keep the source model, the prompt record or the earlier drawing.
- Make a TimeBind of the exact file you send. The fingerprint is made in your browser and the file stays on your device.
- Store the file, the source, and the Proof of Time Certificate together.
A TimeBind shows the exact file existed no later than the recorded time and still matches. It does not show who designed it, who holds the commission, or whether a copy circulating later is yours.
First Pooled TimeBind free, no card, then from US$5. An ASAP TimeBind is US$15.
What a TimeBind shows, and what it does not. It shows that an exact file existed no later than a recorded time and that a copy shown later still matches its fingerprint. It does not show who made the file, who owns it, that its contents are true, or whether AI was used to make or edit it. This is general information, not legal advice.
To keep track of which drawings went to whom and when, see also the free Drawing issue register builder. It does not read drawing files.
If clients ask how your studio uses AI tools, see also the free Design studio AI use statement builder. It drafts a short, plain statement and is not a contract clause.
Before the job starts, the free Visualisation AI scope brief builder drafts a plain paragraph for your quote saying where AI tools may be used and how results will be labelled. It is not a contract clause.
Before you hand off, the free AI model dimension spot check log compares key dimensions in an AI-generated model with your source numbers against a tolerance. A pass is not a code or design check.
AI visualization handoff checker: FAQ
Can this tool tell me if a render is AI?
No. It does not scan the image and it is not a tool for identifying generated media. It scores whether the view is labelled, whether you still hold the source, and what a client or planner might assume.
Why not just run an AI detector on the image?
Unofficial detector scores are often wrong about photographs and about generated files. A missing or present watermark is also not decisive. This page asks you to label the view and check it against the design model instead.
What was the Gothic cathedral demo?
In October 2026, Google showed Gemini 4 Argon building a 3D Gothic cathedral in Blender from a single generated reference image, inside its Antigravity environment. That is a software demo, not a construction document. This page does not embed the film, and the same checks apply to any visualization you are about to send.
If I am sending a real design visualization, what should I keep?
Keep the source model or the earlier drawing, the exact file you send, and a short note of what was generated and what was modelled by hand. A TimeBind of that exact file records its SHA-256 fingerprint and the time. Later you can show the file existed no later than that time and still matches. It does not show who designed the work, and it does not turn a visualization into a planning or construction document.
Is anything I tick sent to TimeBinder?
No. The checklist runs in your browser. Your ticks stay on the page.
Does a high result mean I should scrap the visualization?
No. It means the file should be labelled and checked before you send it, and that you should still hold the source it came from.
Related guides and tools
- Architecture timestampingThe TimeBinder hub for architects
- Design-file timestampingFor product and graphic design files
- Before sending a product design to a manufacturerWhat to date before a file leaves the studio
- Protect a design concept in a tender or competitionRecords to keep before a jury sees the work
- When a terminated design is reusedWhat to have kept from the original appointment
- Before You SubmitA pre-submission checklist
- Handover ReceiptA record of what you handed over
- All free toolsPrivate, in-browser tools
Date the file you send, and keep the source
Add a layer of protection against AI and human fraud and disputes: a dated, checkable record of the exact visualization, kept with the model it came from.
- Open the app and sign in with email or Google.
- Add your files. They stay on your computer.
- Seal them and download your Proof of Time certificates.
First Pooled TimeBind free, no card, then from US$5. See pricing.