A client pays for the "End Result" (the website, the logo, the app). They do not necessarily pay for the "Tools" (the raw PSDs, the Figma source, or the local dev environment).
If a client wants your source files, they are asking for your Intellectual Property. Here is how to handle that request on your final invoice.
1. Source Files vs. Deliverables
- Deliverable: The compiled
.exe, the live website, the.pnglogo. - Source File: The raw
.layer, the.tsxcode, the.rawphoto.
2. The "Buyout" Fee
If a client wants the raw files so they can edit your work without you later, you should charge an Ownership Transfer Fee (Buyout). This compensates you for the future work you are losing. You can add this as a separate line item in our Invoice Maker.
3. Background IP
Never give away your "Background IP"—the snippets of code or design templates you've built over years that you reuse for all clients. Your contract should state that you retain ownership of your underlying tools and only license them to the client.
Frequently Asked Questions (FAQ)
What if I'm a 'Work for Hire' developer?
In a Work Made for Hire agreement, the client usually owns everything, including the source code. In this case, ensure your milestone payments are high enough to reflect that you are losing all future rights.
Should I charge an 'Archiving Fee'?
If a client comes back 2 years later asking for raw files you’ve been storing on your personal hard drive, it is perfectly professional to charge a "Data Retrieval Fee."
How do I deliver source files securely?
Don't use public links. Use a secure, private handover. Because FreelanceShield is built on privacy, we recommend ensuring your handover process is as secure and local as possible to avoid data leaks[cite: 2].