Creative Source File Ownership: Ask What Leaves With You Before You Build Anything
Quick answer
Creative source file ownership is the question of who holds the editable originals of your brand's work and what you can take with you when a vendor or platform relationship ends. Work built inside somebody else's tool without an export path is work you rent, and the rent comes due at migration.
What does losing creative source file ownership actually cost you?
A full rebuild of work you already paid for. The brand director at a multi brand home services operator described two of these losses in the same breath, one to an agency and one to a platform.
We're going through that right now with our fleet graphics, for example. We've had an agency, they do production for it, and we don't have access to the source files any longer because they've done some production work. Similarly with our old email program, we had our email team who were not designers, they were making changes within the platform. And then when we changed to a different platform, we lost all of it. That was all done in the platform. And so we have to rebuild everything from scratch.
Senior director of brand, creative and content at a multi brand home services operator
Two different mechanisms, one result. The agency held the production files. The email platform held the design work as platform objects that meant nothing outside it. Neither loss involved anybody behaving badly. Both were decided years earlier, by what nobody asked for in writing.
Why does creative work built inside a platform vanish when you migrate?
Because the work only exists as configuration inside that vendor's database. A template edited in an email tool is a set of rows rendered by the vendor's code. Export gives you flattened markup that no designer wants to inherit, or it gives you nothing. When the contract ends, the configuration ends with it.
Letting non designers work inside the platform speeds this up. Every edit that happens in the tool and nowhere else widens the gap between what the platform holds and what your team could rebuild. That operator's email team were not designers and they were the ones making changes, which is exactly how a program ends up with no recoverable design layer.
The same exposure shows up in physical assets. Look at what a fleet graphics rebuild costs at their scale: 30 brands across 77 branches, vans in market carrying wraps that now have to be redrawn from photographs and flattened PDFs, because the editable art sits at a vendor.
What should you ask a video platform vendor about source files?
Ask these before the pilot, and get the answers into the contract instead of the sales call. Include us in that list.
| Question to ask | What a good answer sounds like | Risk if the answer is vague |
|---|---|---|
| Who owns the source files we bring in? | You do, and we work from your files rather than replacing them | Your own assets quietly become the vendor's work product |
| What do we get if we cancel? | A named list of file types, delivered within a stated number of days | An export button that returns something unusable |
| Is the design work editable outside your product? | Yes, in a named application your designers already run | A rebuild from scratch on the day you leave |
| Do you hold the master or a copy? | A copy. You keep the master. | One vendor holding the only version of your brand's motion work |
| What happens to renders we already made? | They are yours, downloadable at full quality, hosted or not | A media library you cannot take with you |
| Who can rebuild this if you go away? | Any competent designer working in the source application | A dependency with no substitute |
How does Capsule handle source file ownership?
We build from your After Effects files. A designer on your team or at your agency delivers the composition, Capsule turns it into a locked template, and the fields you choose get exposed in a browser for everybody else. The After Effects project stays yours and stays editable in After Effects, which is why we start there instead of asking you to rebuild your brand inside a proprietary editor.
Here is the honest boundary. The template system itself, meaning the locking, the exposed fields, the rendering and the permissions, is our product, and access to it stops when you stop paying us. What stays with you is your After Effects source, your brand kit assets and every video you rendered while you were a customer. Ask us to put that in writing. Ask every other vendor on your shortlist the same question and compare the answers.
Details on how the file handover works once you build on a template system are in our piece on why After Effects templates do not scale. The product demo and explainer use case shows what teams build once their templates exist.
FAQ
Who owns creative source files, the agency or the client?
Whichever party the contract names. When nothing is written down, teams find out the answer on the day they need the files back, which is what happened with the fleet graphics above.
What should a source file handover clause cover?
Named file formats, the application they open in, a delivery deadline after termination, fonts and licensed elements, and who holds the master versus a copy.
How do you avoid losing design work in a platform migration?
Keep the editable original outside the platform and treat the platform as a place work gets published from. If the only version of an asset lives in a vendor's database, the migration is a rebuild.
Does Capsule keep my After Effects files?
You keep them. Capsule works from a copy of your composition to build the template, and your project file stays yours and stays editable in After Effects.