A client stops responding halfway through a project, then a few months later you find your unfinished designs live on their site. Or a client insists your logo work belongs to them the moment you deliver a first draft, before a single rupee changes hands. Both situations trace back to the same gap: nobody was clear about intellectual property before the work started.
Most Indian freelancers assume IP ownership works itself out naturally. It does not. Here is what the law actually says, and the exact clause you need in every contract to avoid finding out the hard way.
Who owns the work by default, without a contract
Under the Copyright Act, 1957, the creator of an original work owns the copyright by default, even if a client commissioned and paid for it. This surprises most freelancers and most clients. Paying for work does not automatically transfer ownership of it in India, unless a contract says otherwise.
The one major exception is a genuine "employer and employee" relationship under Section 17, which does not apply to freelancers working as independent contractors. As a freelancer, you retain copyright over what you create by default until you explicitly assign it, in writing, to the client.
This means silence protects you as the creator, not the client. A client who never got an IP clause in writing has a weaker legal position than they probably assume, which is exactly why getting a clear IP clause into every contract benefits both sides rather than just protecting you.
The clause every freelance contract needs
A proper IP ownership clause states three things clearly: what is being transferred, when it transfers, and what you retain. The most freelancer-protective and client-acceptable standard is: full IP rights transfer to the client upon receipt of final payment in full, not upon delivery of the work.
This single condition, tying transfer to payment rather than delivery, is the most important protection in the entire clause. Without it, a client can receive your final files, delay or refuse payment, and still legally own everything you made. With it, unpaid work legally remains yours, which gives you real leverage if a client tries to walk away without paying.
What you should keep, even after IP transfers
A well-written IP clause does not have to hand over everything. You can and should carve out specific rights for yourself even after the client owns the final deliverable.
Portfolio rights are the most important carve-out for freelancers. Add a line stating you may display the work in your portfolio and reference the client relationship, unless the work is covered by a separate NDA restricting disclosure. Without this, a strict IP clause can quietly prevent you from ever showing your best work to future clients. General skills, techniques, and reusable components you developed while working on the project also remain yours; only the specific deliverable for that client transfers.
If a client sends their own NDA that conflicts with your contract's portfolio rights, resolve the conflict before signing either document. The guide on freelance NDAs in India covers exactly how to negotiate a portfolio carve-out into an NDA a client hands you.
Code and software IP works differently from design IP
For developers, the same payment-triggered transfer principle applies, but the mechanics differ. Do not transfer repository ownership, deployment access, or production credentials until final payment clears. Give the client read access to review progress during the project, but keep admin control until the invoice is settled.
Open-source components and libraries you use are governed by their own licenses regardless of your contract. Your IP clause covers the custom code you wrote, not the underlying frameworks or packages. State clearly in the contract that third-party libraries remain under their original licenses and are not part of what transfers to the client.
Beyond IP, developer contracts need a few clauses a generic template does not cover at all, like post-launch bug-fix windows and deployment access. See the full breakdown in the guide on freelance contracts for developers in India. Designers have their own set of missing clauses too, covered in the guide on freelance contracts for designers in India.
What to do if a client already has your unpaid work
If a client is using work you delivered but have not been paid for, and your contract states IP transfers only on final payment, you have a real legal claim, not just a moral one. Send a written notice referencing the specific clause and demanding either payment or removal of the work.
This is significantly harder to enforce if you never had a written IP clause in the first place, which is exactly why getting this into your standard contract template matters more than most freelancers realise until it becomes a problem. For the full recovery process once a client is not paying, see the guide on what to do when a client does not pay.
Rinto's contract templates include a payment-triggered IP transfer clause by default, so you are not relying on remembering to add it manually to every proposal you send.
Frequently Asked Questions
Who owns the copyright to freelance work in India by default?
The freelancer owns the copyright by default under the Copyright Act, 1957, even after the client has paid for the work, unless a contract explicitly transfers ownership. This surprises most clients and freelancers, since paying for work is commonly assumed to include automatic ownership. Without a written IP clause, the freelancer retains legal rights over the work even after delivery and payment.
Should IP transfer on delivery of the work or on final payment?
On final payment, not delivery. Tying IP transfer to full payment gives you real legal leverage if a client delays or refuses to pay after receiving the work. If IP transfers on delivery instead, a client can receive everything and then withhold payment with no legal consequence, since they already legally own what you made.
Can I still show client work in my portfolio after signing an IP transfer clause?
Only if your contract specifically carves out that right. A standard IP transfer clause that says "all rights transfer to the client" can technically prevent you from displaying the work anywhere without permission. Add a specific line allowing portfolio display, unless the project is covered by a separate confidentiality agreement that restricts disclosure of the work's existence.
Do open-source libraries I use in a project belong to the client after IP transfers?
No. Open-source and third-party libraries remain under their own original licenses regardless of your contract with the client. Your IP transfer clause only covers the custom code, design, or content you personally created for that specific project. State this distinction clearly in the contract so there is no confusion about what is actually being transferred.
What can I do if a client uses my work without paying?
If your contract states IP transfers only upon full payment, you have a legal claim, not just a grievance. Send a written notice citing the specific clause and demanding payment or removal of the work. This is far more effective with a written IP clause in place than trying to argue ownership after the fact with no contract to point to, which is why adding this clause before starting any project matters more than remembering it after a dispute begins.