This page explains how image rights, third-party use, 3D source models and working files are typically handled for architectural visualisation projects. It is intended to give clients clear commercial expectations before a brief is commissioned.
Final images and client project use
When a client pays for final images or renders, they receive usage rights for those final paid deliverables for their own project and company use, unless the accepted quote, contract or written agreement says otherwise. Typical permitted use may include planning submissions, design presentations, brochures, websites, investor decks, sales material, hoardings, social media and internal project communication connected to the commissioned project.
The practical aim is simple: once final images are paid for, the client can use those final images to promote, explain and progress the project they were commissioned for.
Third-party use is separate unless agreed in writing
Usage rights for the commissioning client do not automatically extend to unrelated third parties. If another consultant, developer, estate agent, contractor, supplier, publication, partner company, future owner or other organisation wants to use the images independently, a separate usage or licensing fee may apply unless that use has been agreed in writing.
This protects both sides. It lets the client know what is included, while making sure wider commercial use is discussed openly before images are circulated beyond the original project team and agreed purpose.
Examples of use that may need separate permission
- An estate agent wants to use the renders in a separate advertising campaign for their own brand.
- A contractor or supplier wants to feature the CGI in their portfolio, tender documents or case studies.
- A publication, media partner or awards submission wants to reproduce the images outside the client’s own project material.
- A future owner, purchaser, funder or development partner wants to reuse the images for a new sales, leasing or investment campaign.
- A separate consultant wants to adapt, crop, annotate or republish images as part of their own marketing.
3D source models and working files
Project fees usually cover the labour, process and expertise required to model, compose, texture, light, render and deliver the agreed final outputs. They do not automatically include ownership or transfer of the underlying 3D source models, scene files, working files, textures, setups, cameras, lighting rigs, render settings, scripts, reusable assets, production methods or other source material.
Those working assets are part of the production system used to create the final images. They may contain studio libraries, third-party assets, licensed textures, reusable setups, test geometry or workflow material that cannot automatically be transferred with a final render.
Source-file release or rights buyout
If a client needs transfer, surrender, buyout or release of source model files or broader rights, this must be agreed separately in writing. A model or source-file release fee may apply, and the scope should define exactly what is being released, in which format, for which use, and whether any restrictions remain.
Where source files include third-party assets, licensed material, stock textures, proprietary setups or reusable studio components, some elements may need to be removed, substituted or licensed separately before release.
Portfolio, confidentiality and written project terms
Confidentiality, portfolio display, credit lines, third-party use, exclusivity, image buyouts and source-file transfer should be raised before work begins where they matter to the project. Written project terms, accepted quotes, contracts, NDAs or statements of work prevail over the general information on this page.
Standing usage-rights guidance
These image and model licensing points are standing general usage-rights guidance for Architectural Visualisations London projects. They may not be repeated in full in every offer, quote, contract, email, invoice, handover note or downstream document, so clients and image users should refer to this Licensing / Usage Rights page for the current general position unless their written project agreement expressly states different terms.
This is intended as a clear reference point, not a hidden condition or trap. If a project needs broader use, third-party rights, exclusivity, a source-file release or a different licensing arrangement, it should be confirmed in writing so the scope and fee match the intended use.
Practical FAQ
Can we use final paid renders on our website and in planning documents?
Typically yes, if the use relates to the commissioned project and your company’s own project communication. The quote or project terms should be checked for any specific limits.
Can our estate agent, contractor or supplier use the images too?
Not automatically. Third-party use should be agreed in writing, and a separate usage or licensing fee may apply depending on the audience, duration, channel and commercial purpose.
Do we own the 3D model once the renders are paid for?
Not unless this has been agreed separately. Payment for final renders typically covers the final image deliverables, not the source model, scene file, asset library, lighting setup or render workflow.
Can we buy the source files?
Potentially, but source-file transfer must be scoped separately. A release fee may apply, and some third-party or reusable studio assets may need to be excluded, substituted or licensed separately.
Will these licensing terms appear in every project email or quote?
Not necessarily. This page provides the standing general usage-rights guidance for image licensing, third-party use and source-file release unless a written project agreement expressly differs. Clients and image users should check this page when they need the current general position.
General information, not legal advice
This page provides general commercial information only. It is not legal advice. The agreed quote, contract, statement of work, licence terms or written project agreement will take precedence for any specific project.