Who Owns Architectural Renders From Freelancers?

Mia runs a small architecture studio in Wellington. Her team wins a promising residential design brief, then hires an external renderer to create polished images for the client presentation.

The renders look great. The client then asks for the editable 3D files, texture libraries and all source files so their marketing agency can reuse them. Mia assumes the studio can hand them over because it paid the renderer. The renderer disagrees, saying the fee only covered final JPEGs and that the reusable assets are part of their own library.

This kind of gap is very common in architecture and design workflows. You may be clear on the design direction, deadlines and price, but less clear on who owns the final renders, the working files and the assets sitting behind them.

The good news is that this can usually be fixed with the right contract wording before the project starts. The key is to be specific, because IP ownership is rarely as simple as whoever paid owns everything.

Who Owns Copyright In Architectural Renders In New Zealand?

It depends on what was created, who created it, and what your contract says.

In New Zealand, copyright is mainly dealt with under the Copyright Act 1994. Copyright can protect original artistic works such as drawings, plans, diagrams, models and images. It can also protect some computer-generated works and related files, depending on what they are.

Copyright doesn't protect every idea. It protects the particular expression of an idea. So your broad design concept, mood or style isn't treated the same way as a specific render, drawing, model or file.

There's no copyright registration system through IPONZ. Copyright usually exists automatically once the work is created, as long as it meets the requirements under the Copyright Act 1994.

The ownership position can change depending on the relationship:

• Employee work: if your employee creates renders as part of their job, your business will usually own the copyright, unless there's an agreement saying something else.
• Independent contractor work: if an external freelancer creates the work, the answer depends on the type of work, the commissioning arrangement and any written agreement.
• Commissioned works: for some commissioned works, such as drawings, plans, models, films and computer programs, the person who commissions and pays for the work may be the first copyright owner, unless the contract says otherwise.
• Pre-existing materials: if the freelancer uses their own templates, texture libraries, scripts, lighting rigs or model assets, those may stay with the freelancer unless they're clearly assigned to you.

That last point is where architecture firms often get caught. Even if your business owns a final commissioned render, that doesn't automatically mean you own every underlying asset or reusable file that helped create it.

If you're thinking about architect and freelancer IP ownership in NZ, the safest approach is to put the ownership position in writing, rather than relying on default copyright rules.

Are Renders, Source Files And 3D Models Treated The Same?

No, not always. Final renders, editable source files and reusable design assets can be treated differently.

For example, your project might involve:

• final still images, such as JPEGs or PNGs
• animations or fly-through videos
• Photoshop files with editable layers
• Revit, SketchUp, Rhino, Blender, 3ds Max, Lumion, Enscape or Twinmotion files
• CAD drawings, plans, diagrams and models
• textures, materials, people, plants, furniture and lighting assets
• custom scripts, plug-ins, presets or workflows
• reference images, mood boards and presentation layouts

A renderer may be happy to give you final image files, but not their editable working files. From their perspective, those source files may reveal their methods or include assets they use across many clients.

From your perspective, you may need source files so your internal team can make future changes without starting again. You may also need to pass certain files to the client, a marketing agency, a builder or another consultant.

Both positions can be reasonable. The issue is that your fee and project scope need to match the rights you want.

Final Outputs

Final outputs are the deliverables the freelancer is being paid to create for your specific project. These might be still renders, an animation, a set of boards or image files for a planning application or client pitch.

Your contract should say whether your business owns these final outputs or receives a copyright licence to use them. If your client expects ownership, your renderer contract needs to support that.

Source Files

Source files are the editable working files used to produce the final output. They can be much more valuable than a finished image because they allow future edits, reuse and adaptation.

If you want source files, say so clearly. Spell out the file types, when they must be delivered, whether they must be editable, and whether third-party assets are included or excluded.

Reusable Assets

Reusable assets are the pieces the freelancer may use again across different jobs. These can include texture packs, 3D furniture, lighting setups, templates, material libraries and workflow tools.

It's common for freelancers to keep ownership of these assets but give your business a licence to use them as embedded in the project deliverables. If you need broader rights, you should negotiate that upfront.

What Rights Does Your Architecture Client Get?

Your client only gets the rights you can legally give them.

This is the common gap. Your client may assume that because they paid your architecture studio, they own every render, file and visual asset connected to the project. But if your external renderer kept some rights, you may not be able to pass full ownership on to the client.

Say your studio hires a freelance designer to create marketing renders for an apartment development. Your client later wants to use the images for brochures, online ads, signage, investor packs and social media. That might be fine if your agreement allows it.

But if your renderer agreement only allows internal presentation use, or says the renders can't be used for paid advertising without extra fees, you may have a problem with the client.

Your client contract and renderer contract should line up on:

• whether the client owns the final renders or only gets a licence
• whether the client can use renders for marketing, planning, sales or investor materials
• whether the client can edit, crop, adapt or combine the renders with other material
• whether the client can give files to builders, consultants, agencies or future designers
• whether the client receives source files or only final outputs
• whether the client can use the images after your engagement ends

If the client has paid for a limited design stage, you may not want them to have open-ended rights to repurpose incomplete concepts. On the other hand, if full client ownership is part of your commercial offer, you need the renderer's contract to reflect that.

What Should An IP Clause In An Architecture Contract Say?

An IP clause should clearly separate new project work, pre-existing materials, source files and permitted uses.

A strong IP clause in an architecture contract usually covers more than one sentence saying all IP belongs to the client. That kind of wording can create confusion if the freelancer uses existing materials or third-party asset libraries.

Your renderer agreement should deal with:

• New project IP: who owns the final renders and other new material created specifically for the project.
• Pre-existing IP: what the freelancer owned before the project started, and whether your business can use it as part of the deliverables.
• Third-party assets: whether any stock images, 3D models, textures or plug-ins are used, and what licence terms apply.
• Source files: whether editable files are included, which formats are required and when they must be handed over.
• Client use: whether your client can use, reproduce, publish, adapt and share the renders.
• Portfolio use: whether the freelancer can show the work on their website, social media or award submissions.
• Moral rights: how attribution, credit and treatment of the work will be handled.
• Confidentiality: what project information, designs, client details and files must be kept confidential.

New Zealand copyright law also recognises moral rights, including certain rights to be identified as author and to object to derogatory treatment of a work. These rights are different from copyright ownership. They may need to be managed through acknowledgements, consents or waivers where appropriate.

The right wording depends on how your studio works. A renderer who creates one-off bespoke images for confidential concept work needs different terms from a regular contractor who produces marketing renders using a large asset library.

Templates often miss these workflow details. Documents work best when they reflect how your business actually briefs, reviews, stores, shares and reuses design files.

Can A Freelancer Reuse Parts Of Your Project?

Yes, they may be able to reuse parts of the work if your agreement allows it, but they shouldn't reuse your confidential or client-specific material without permission.

Freelancers often want to reuse non-confidential elements such as textures, lighting settings, generic furniture layouts, trees, people or workflow templates. That can be commercially sensible, especially where those assets came from their own library.

But there's a big difference between reusing a generic texture and reusing a distinctive design for a named client project.

Your agreement should say what is off limits. For example, you may want to restrict the freelancer from:

• using your unreleased design concepts for other clients
• sharing confidential floor plans, site information or client details
• publishing renders before your client has approved public release
• presenting your project as their own design work
• reusing bespoke models, facade studies or interiors created for your client

You should also think about the Fair Trading Act 1986. If a freelancer or another party makes misleading claims about who designed the project, who owns the work or what role they played, that can create commercial and reputational issues.

If the project includes personal information, such as names, contact details or identifiable images of people, the Privacy Act 2020 may also be relevant. That's less common for architectural renders than for some other creative work, but it can come up in client presentations, sales materials and internal project platforms.

What Happens If You Do Not Have A Written Agreement?

You may still have some rights, but you're more likely to face uncertainty over ownership, file access and reuse.

Without a written agreement, you may need to piece together the position from emails, quotes, invoices, briefs and conduct. That can be slow and frustrating when a client is waiting for deliverables.

Common problems include:

• the freelancer says the fee only covered final images, not source files
• your client expects ownership of all project IP, but your freelancer kept key rights
• you can't update the renders without going back to the same freelancer
• third-party assets were used but no one checked the licence terms
• the freelancer publishes confidential images before the project is public
• the client wants to use renders for advertising, but that use was never discussed

This doesn't mean every freelancer agreement for a renderer needs to be complicated. For small jobs, you may only need a simple contractor agreement and a clear project statement of work. For higher-value projects, confidential developments or projects with heavy client marketing use, it's worth being more detailed.

If you use external renderers regularly, build the IP rules into your standard onboarding process. That way, you don't have to renegotiate ownership every time a deadline is close.

How Should You Set Up Your Renderer Workflow?

You should set up your workflow so the IP position is clear before the renderer starts work.

A practical setup could look like this:

Before You Brief The Renderer

• Decide whether your studio needs ownership or a licence.
• Check what your client contract promises the client.
• List the deliverables, including exact file types and formats.
• Decide whether source files are included in the fee.
• Ask whether the renderer will use third-party assets or their own asset library.
• Set confidentiality rules, especially for unannounced projects.

When You Engage The Renderer

• Use a contractor agreement that covers IP, confidentiality and deliverables.
• Add a statement of work for the specific project.
• Confirm revision rounds, deadlines and approval points.
• State who can approve use of the work in portfolios or social media.
• Make sure the payment terms match the level of rights being granted.

At Handover

• Check that all agreed files have been delivered.
• Confirm any third-party asset terms that affect future use.
• Store files in a way your team can access later.
• Record any limits on client use, editing or publication.
• Keep a copy of the signed agreement and scope documents.

If the person doing the work may be closer to an employee than a genuine contractor, get advice on that structure too. The Employment Relations Act 2000, including the Employment Relations Amendment Act 2026 contractor gateway test changes, can affect how contractor status is assessed. Classification matters for employment obligations, and it can also affect how IP ownership is analysed.

Your legal setup doesn't need to slow your creative process down. Done well, it gives everyone confidence about what is being made, who can use it and what happens when the project grows.

Key Takeaways

• Don't assume your architecture studio owns every render, source file and reusable asset just because you paid a freelancer.
• The Copyright Act 1994 has default rules, but architecture rendering projects often involve mixed materials, third-party assets and pre-existing freelancer IP.
• Your client only gets the rights your business can pass on, so your client contract and renderer contract should line up.
• Be clear about final outputs, editable source files, 3D models, asset libraries, portfolio use and confidentiality.
• A tailored contractor agreement and statement of work can prevent awkward conversations when the client asks for more than you expected.

If you'd like help with your renderer contractor agreements, IP clauses, client contract wording and confidentiality documents, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.