Understanding Creative Ownership, Source Files and Best Practice
As marketing assets become more sophisticated, clients and agencies are increasingly asking who owns the working files behind a finished piece of creative?
A presentation, campaign image, animation or 3D visual may look relatively simple once it is finished, but behind it can sit a substantial collection of editable files, linked assets, technical settings and production processes. Those underlying files can become valuable in their own right, particularly when content needs to be adapted, animated, localised or reused by another team or agency.
That can create a grey area between clients and creative agencies. If a client has commissioned and paid for a piece of work, does that automatically include the working files and source files used to create it?
There is no single answer that applies to every project. Working files ownership, source files ownership and the wider ownership of creative works depend on what has been commissioned, what the agreed deliverables are, the terms of the contract and, in some cases, the rights attached to third-party assets. The legal position can also vary depending on where the work is commissioned and which law applies, so specific intellectual property questions may require legal advice.
What is much easier to control is the commercial relationship. Clear expectations about deliverables, editable files, production assets and usage rights can prevent misunderstandings before they arise.
What is a working file?
The terminology is not always consistent across agencies or creative disciplines, so it helps to distinguish between a few common terms.
Finished artwork is the completed, approved creative intended for its agreed use. For example, a print-ready brochure, final packaging artwork, approved campaign image or finished video.
Working files are the editable files directly associated with that finished work. An Adobe InDesign document containing an editable layout, for example, or an Illustrator file used to create a set of campaign graphics.
Source files are the original editable files from which other assets or outputs are created. Depending on the project, this could include Illustrator artwork, a layered Photoshop file, a 3D scene, an After Effects project or original photography.
Production assets are the wider collection of elements used during production. These might include images, textures, fonts, templates, models, audio, plug-ins or component artwork. Some may have been created by the agency, some by a specialist supplier and some licensed from third parties.
Exported files are the outputs generated from those working files, such as PDFs, JPEGs, PNGs, MP4s or other formats intended for delivery, publishing or distribution.
There is often overlap between these definitions. That is why, when discussing deliverables vs source files, it is usually more useful to agree exactly what will be supplied than to rely on terminology alone.
What about websites and digital platforms?
Websites bring a slightly different set of considerations. Ownership and handover can extend beyond design files into source code, content management systems, plug-ins, hosting, databases and third-party technology. The same principle still applies – what the client owns or receives should be clear from the outset – but website ownership is a subject in its own right and deserves a separate discussion.
What does a client normally pay for?
In most creative projects, the starting point is the agreed scope and deliverables.
A brand identity project may result in an agreed suite of logos, colour palette and brand guidelines. A print project might result in press-ready artwork and, where agreed, editable artwork files. A video or animation project could result in a finished master plus versions for different channels. A 3D visualisation project may result in a series of high-resolution rendered images.
The same principle applies across packaging, illustration, photography, digital content, motion graphics and other creative disciplines. The client commissions an agreed creative outcome and the agency determines the production process required to achieve it.
Paying for that outcome does not necessarily mean every file, component or production asset created during the process is automatically part of the handover. Exactly what the client is purchasing – and the rights that accompany it – should be made clear in the project’s scope, quotation and creative agency contract or terms.
© Balazs Ketyi, Unsplash
What’s actually inside a working file?
Working files can contain considerably more than the finished creative suggests.
Open a complex Photoshop file and you might find hundreds of layers, masks, smart objects, effects and linked assets. An Illustrator file can contain the underlying construction of an illustration. An After Effects project might include compositions, expressions, effects and animation setups. A Premiere project can contain an entire edit structure, while a Cinema 4D or Blender scene may include models, textures, lighting, cameras and render settings.
Some projects go deeper still. Animation files can contain reusable rigs; 3D visualisations may incorporate custom materials or individual product models; technical illustration may involve workflows built around CAD-derived data; and campaign imagery can rely on extensive retouching and compositing.
These files are not simply alternative formats of the finished deliverable. They may contain reusable methods, templates, components or production systems developed over many projects. In other words, a working file can contain not only the client-facing creative, but elements of an agency’s accumulated production knowledge too.
© Peter Stumpf, Unsplash
Why don’t agencies automatically hand over every file?
It is understandable for a client to assume that paying for creative work means receiving everything used to make it. In practice, design files ownership and access to source files depend on what has been agreed.
One consideration is intellectual property in design. Depending on the contract, a working file may contain reusable agency material, tools or assets that were not created exclusively for that client. Commercial rights vs copyright can also be different questions. A client may have broad rights to use finished work without necessarily receiving every underlying production file.
Third-party asset licensing is another important factor. Fonts, stock photography, music, plug-ins, models and other assets may be subject to licences that do not allow an agency simply to transfer them to another organisation.
There is also the technical reality. A working file is not always a neat, self-contained document ready for somebody else to pick up. It may rely on specialist software, linked files, particular fonts or established production methods. Internal production files are created to get the work made efficiently; preparing them as a clear editable files handover can itself require additional work.
None of this means agencies should never transfer working files. It means transferring source files is worth considering as part of the project scope, rather than assuming every underlying file is automatically included.
© Unsplash
Why clients may need working and source files
There are many perfectly reasonable reasons for clients to request working files.
An internal design team may want to adapt campaign assets without returning to the original agency for every small amendment. Another creative agency may take responsibility for a particular channel. A specialist supplier may need existing assets to create an animation, localisation or derivative piece of work.
Larger organisations may also have procurement, governance or global asset-management requirements. They may want an archive of editable brand materials, greater continuity between suppliers or confidence that important assets remain accessible if agency arrangements change.
Long-term reuse can be particularly relevant for specialist assets. If a business commissions a substantial library of 3D product models, for example, it may know from the outset that those models will need to support multiple campaigns over several years.
Where that future use is foreseeable, discussing working files and usage rights early gives both parties the opportunity to agree what should be supplied, who can use it and whether that changes the project cost.
© Peter Herrman, Unsplash
What is considered fair?
There is no single commercial model that fits every project.
In some cases, supplying editable files can simply be included within the original scope and price. If the client knows at the outset that source files are an important deliverable, the agency can plan for the handover and price the project accordingly.
In other circumstances, working or production files may be available for an additional fee. That fee may reflect the commercial value of reusable assets, the time required to prepare them for transfer, or additional usage rights being granted.
Licensing creative work can provide another option. Rather than transferring every underlying right or asset, the client and agency can agree how particular files may be used, adapted or shared with third parties.
A hybrid approach is often the most practical. Client-specific working files can be supplied, while reusable agency tools, templates, exploratory material or third-party licensed assets are excluded.
None of these approaches is automatically more correct than another. Fairness comes from both sides understanding what is being supplied, what can be done with it and what has been included in the price.
How can this work in practice?
Imagine a campaign comprising a hero image, white paper, presentation and social graphics. A sensible handover might include the packaged InDesign file for the white paper, the editable presentation and the source artwork for the agreed social graphics.
The hero image may be different. If the finished visual was created from a complex Photoshop montage containing extensive retouching, embedded elements and reusable production components, the flattened approved hero image might be part of the standard campaign handover while the deep layered build is treated as a separate production asset unless specifically agreed.
A 3D project provides another useful example. The agreed source file for a completed visualisation might be included in the project handover. But if another agency later asks for individual product models extracted from within that scene so they can create different work, that request goes deeper into the underlying production assets and may need to be scoped separately.
The principle is not about making files difficult to access. It is about defining the level of handover clearly enough that both client and agency know what ‘working files’ actually means for that particular project.
Best practice for agencies
For agencies, transparency is key. Questions about creative ownership and working files are much easier to resolve before a project begins than months or years later.
Quotations and scopes should define the deliverables clearly and state whether editable or source files are included where relevant. For complex work, it can be useful to list the specific production assets being handed over and any exclusions.
Agencies should also flag third-party licensing restrictions early and explain where an editable handover may require additional preparation. If there is a separate fee for source-file preparation, transfer or licensing, that should be made clear before the client commits.
It can also help to agree how files will be archived and transferred at project completion. A simple client-facing handover package is usually more useful than duplicating an agency’s complete internal production folder.
Best practice for clients
Clients can make the process much easier by thinking beyond the immediate deliverable.
If editable files are likely to be important, raise this during the briefing or procurement process. Consider who may need to use the work later, whether internal teams will need to adapt it and whether other agencies or suppliers are likely to become involved.
It also helps to distinguish between wanting to archive a file and wanting the ability to reuse or develop the underlying production assets. Those needs may lead to different handover, licensing or pricing arrangements.
Most importantly, avoid assumptions. If retaining particular source files matters to the organisation, make it an explicit project requirement. That gives prospective agencies the opportunity to scope and price the work on the same basis.
Key takeaway
When it comes to who owns working files, there is rarely a universal answer. Clients can have legitimate reasons for wanting access to the assets behind their creative work, while agencies can have equally legitimate reasons for treating some source files, production assets or third-party content differently.
The best outcomes usually come from defining the handover before the project starts. That means agreeing the final deliverables, which editable files are included, whether deeper production assets are required, who may use them and whether any additional licensing or preparation costs apply.
At Shine, we aim to take a pragmatic approach. Sometimes working files are included as part of the project. In other situations, a more detailed production-asset handover or separate licensing arrangement may be appropriate. We look at the scope, the intended future use and the practical work involved, then explain the approach clearly.
The goal is not to make working files difficult to access. It is to make sure everyone understands what has been commissioned, what is being supplied and how the work can be used in future. Clear expectations protect both sides and create a stronger foundation for a long-term creative partnership.
Not sure what should be included in a creative file handover?
We work with clients to make these arrangements clear from the outset, so everyone knows what’s being supplied, how it can be used and what happens if another agency needs access later.