Who Owns the Work? IP in Freelance Contracts

Work-for-hire vs assignment

Under U.S. copyright law, “work made for hire” is a special authorship rule. If a work truly qualifies, the hiring party is treated as the author and initial copyright owner. For employees, that usually means work created within the scope of employment. For independent contractors, Copyright Office Circular 30 explains that a commissioned work is work made for hire only if there is a signed written agreement saying so and the work fits one of nine statutory categories (such as a contribution to a collective work, part of a motion picture, a translation, a compilation, an instructional text, a test, answer material for a test, a supplementary work, or an atlas).

Many freelance logos, websites, and custom software projects do not fit those categories. That is why contracts often use assignment language as a fallback: even if work-made-for-hire status fails, the freelancer assigns copyright to the client. Either path can give the client ownership of custom deliverables — but the label alone does not always make something work made for hire.

What you should keep: background IP

Background IP (or "pre-existing IP") is what you bring to the project — frameworks, libraries, design systems, general methodologies, and tools you use across clients. A fair contract assigns custom deliverables to the client while you retain background IP and grant the client a license to use deliverables.

• Custom deliverables created for the client → client owns
• Your pre-existing code, templates, and tools → you retain
• General skills and knowledge → always yours, not assignable
• License grant: client can use deliverables; you can reuse non-client-specific components

Exclusive vs. non-exclusive license

Sometimes the client doesn't need full ownership — they need a license to use the work. Exclusive license: only they can use it (you can't resell that design). Non-exclusive license: they can use it, and you can license the same work to others. Exclusive licenses cost more because you're giving up reuse rights.

Portfolio and attribution rights

Many freelancers want to show work in their portfolio. Contracts sometimes prohibit this under confidentiality. Negotiate a portfolio carve-out: you can display work in your portfolio after public release, with or without client name. Get it in writing — "verbal permission" doesn't survive a strict NDA.

Red flags in IP clauses

Watch for: assignment of "all work product" without background IP exclusion, claims on inventions developed outside project scope, IP assignment that survives project termination indefinitely, and restrictions on using general skills learned during the project.