Alex is Sprintlaw's co-founder and a legal technology leader. He holds law and media degrees from the University of Sydney and has been recognized by Australasian Lawyer, Lawyers Weekly and the Sydney Young Entrepreneur Awards for his work building Sprintlaw and improving access to business legal support.
Are you asking yourself, "Does my freelancer own my website code?" The first answer is: maybe, but this is usually fixable if you move carefully and get the paperwork right.
This issue often pops up at the worst time. You might be preparing to sell your business, raise capital, rebuild your site, or move to a new developer when someone asks, "Who actually owns the code?"
If your developer contract didn't clearly assign intellectual property to your business, don't panic. What matters now is working out what you have, what you need, and how to put a clean assignment and handover process in place.
Does A Freelancer Own My Website Code If There Is No Assignment?
Yes, a freelancer may own the copyright in the website code if there isn't a written IP assignment to your business.
Under the US Copyright Act, copyright usually belongs first to the person who creates the work. For employees, the employer may own work created within the scope of employment under the "work made for hire" rules. For independent contractors, the position is much narrower.
A contractor's work is only treated as a work made for hire if:
- There's a written work for hire agreement saying it's a work made for hire, and
- The work fits within one of the Copyright Act's specific categories.
Many website and software development projects don't fit neatly into those categories. That's why a written IP assignment is usually the safer route for code, designs, databases, technical documentation and related materials.
The practical problem is this: even if you paid every invoice, payment alone doesn't automatically transfer copyright. You may have an implied license to use the website, especially if the developer built it for you and delivered it. But an implied license can be hard to prove and may not let you do everything you need, such as:
- Sell the website or software as part of a business sale
- Let a new developer modify the source code
- Commercialize the code in a new product
- Use the code across multiple brands or locations
- Give investors clean IP ownership documents during due diligence
State contract law can also affect how your agreement is interpreted, especially if emails, invoices, purchase orders or platform terms are part of the deal. If the stakes are high, it's worth getting the actual documents reviewed rather than guessing from the invoice alone.
What Should You Do First?
You should first gather the contract trail, check what was actually promised, and avoid making threats or cutting off access until you know your position.
Start with a calm document review. You're trying to answer three simple questions: what did you buy, what rights were granted, and what still sits with the developer?
Collect The Paper Trail
Pull together anything that shows the deal between your business and the developer, including:
- Signed service agreements or statements of work
- Proposals, quotes and invoices
- Emails and messages about ownership, licensing or handover
- Platform terms if you hired the freelancer through an online platform
- Change requests and milestone approvals
- Payment records
- Admin account invitations and access logs
Don't just look for the words "copyright" or "IP." Developers sometimes use words like "source files," "deliverables," "assets," "license," "handover," "repository," or "final files." These can make a real difference.
Check What You Currently Control
Next, work out what your business can access today. This might include:
- Your domain registrar account
- Your hosting account
- Your content management system admin login
- Your code repository, such as a private repository
- Your database and backups
- Your design files
- Your API keys, plugins and paid software accounts
If you don't have access to source code, you may only have access to the live website. That can be enough to operate day to day, but it may not be enough to maintain, scale or sell the business.
Keep Communications Practical
If you contact the developer, keep it businesslike. Ask for a copy of the contract, source code, design files and deployment notes. Avoid accusing them of wrongdoing before you know what the documents say.
A simple message like this can work: "We're cleaning up our IP records for diligence and need to confirm ownership and access to the website code. Could you please send through the source code, repository access and any IP terms that applied to the project?"
How Do You Fix A Missing IP Assignment?
You fix a missing IP assignment by getting a written assignment signed by the person or company that owns the relevant rights.
The Copyright Act requires a transfer of copyright ownership to be in writing and signed by the owner of the rights. An exclusive license also needs to be in writing. A casual email might help show what everyone intended, but it's usually not enough if you need a clean ownership record for a buyer, investor or new developer.
There are a few ways to remediate the position.
Option 1: Full IP Assignment
This is usually the cleanest option. The developer assigns to your business all rights, title and interest in the agreed deliverables, including source code, custom scripts, custom designs and documentation.
This is the option most buyers and investors prefer because it gives your business the clearest ownership story.
Option 2: Broad Perpetual License
If the developer won't assign ownership, you may be able to negotiate a broad software license agreement. For example, the license might be perpetual, worldwide, royalty-free, transferable and sublicensable.
This can be useful if the developer has reusable code libraries they use across many clients. In that case, they may not want to transfer ownership of their background code, but they may agree that your business can use, modify and transfer the website without further permission.
Option 3: Assignment Of Custom Code Plus License To Background Tools
This is often the most realistic middle ground. Your business owns the custom code built specifically for your website, while the developer keeps ownership of pre-existing tools, templates or libraries. Your business then gets a clear license to use those background materials as part of the website.
For example, Maya runs an online meal prep business. She paid a freelance developer $18,000 to build a customer ordering portal. Two years later, she's negotiating a $750,000 asset purchase agreement and the buyer asks for proof that the business owns the portal code. Her original contract only said "website build" and didn't mention IP. Maya negotiates an assignment of the custom portal code, a license to the developer's reusable booking module, and repository access for the buyer's technical team. The sale can move forward because the ownership position is documented rather than left to assumptions.
How Can You Negotiate Access To The Source Code?
You can negotiate source code access by separating ownership from handover, then asking for a practical list of files, credentials and technical information your business needs.
Sometimes the developer isn't refusing to help. They may simply see source code, deployment notes or build scripts as outside the original quote. Other times, they may be worried you'll reuse their background tools without permission. A clear proposal can reduce friction.
What To Ask For
Ask for a handover package that includes:
- Access to the current source code repository
- A downloadable copy of the source code as at a specific date
- Database schema and backup files, if relevant
- Build and deployment instructions
- Admin credentials or transfer of account ownership
- A list of third-party plugins, libraries, fonts, themes and APIs
- License keys and renewal details for paid tools
- Known issues, dependencies and maintenance notes
If the developer wants to be paid for handover work, ask for a clear fixed scope. For example, "two hours to prepare repository access, one hour to document deployment steps, and one handover call." That helps avoid a vague and expensive cleanup exercise.
What If The Developer Says No?
If the developer refuses, don't immediately escalate the dispute. First, check whether your contract already gives you rights to the source files or final deliverables. If it does, you may be able to point to the clause and ask them to comply.
If the contract is silent, your leverage may come from practical factors rather than strict ownership. For example, the developer may want to preserve the relationship, get paid for outstanding work, or avoid a dispute affecting a business sale.
If the website is business-critical or there's a sale or funding deadline, get legal help before sending a formal demand. A poorly worded demand can make the developer defensive and harder to deal with.
What Should An IP Assignment Include?
An IP assignment should clearly identify the project, transfer the right IP, deal with background materials, and require the developer to help with handover.
Templates can be a helpful starting point, but they often miss the details that matter most for software and websites. A lawyer should tailor the document before you use it, especially if you're preparing for due diligence.
IP Assignment And Source Code Handover Outline
- Parties: Name your business and the developer or development company signing the assignment.
- Project Description: Describe the website, app, portal or codebase covered by the assignment.
- Assigned IP: State what rights are being transferred, including copyright in custom code, design files, documentation and other deliverables.
- Effective Date: Say whether the transfer applies from creation, from the original project date, or from signing.
- Background Materials: Identify any pre-existing tools, libraries, templates or code the developer keeps.
- License To Background Materials: Give your business the rights it needs to use, modify, host, transfer and maintain the website.
- Third-Party Materials: List plugins, open source packages, stock assets, fonts and paid tools used in the project.
- Source Code Delivery: Set out exactly what must be delivered and when, including repository access and backups.
- Further Assistance: Require the developer to sign extra documents or answer reasonable diligence questions if needed.
- Warranties: Include promises that the developer created the work or has the rights needed to assign or license it.
- Payment Or Release: Deal with any agreed payment, final invoice, or mutual release tied to the cleanup.
- Governing Law: Choose the law that applies to the agreement, noting state law can affect contract interpretation.
If more than one person worked on the project, make sure you know who needs to sign. A company can't assign rights it never received from its subcontractor. If your freelancer used another coder, designer or agency, you may need a chain of assignments rather than one signature.
What If The Developer Used Open Source Or Third Party Code?
You need to identify third-party code because your developer usually can't assign rights they don't own.
Most modern websites use open source packages, plugins, themes, fonts, APIs and other third-party materials. That's normal. The issue is whether your business has the rights it needs to keep using them, and whether any license terms create problems for a sale, relaunch or new product.
Ask your developer for a simple software bill of materials. This is a list of the third-party components used in the website or application, along with the applicable licenses and account details.
Pay particular attention to:
- Open source licenses: Some are permissive, while others may have sharing obligations if you distribute modified software.
- Paid plugins and themes: Check whether the license is in your business name and whether it can be transferred.
- Stock images, icons and fonts: These may have their own license limits.
- APIs and cloud services: Your website may depend on accounts, keys or usage limits you don't control.
- Developer background code: This may be reusable code the developer keeps, with your business receiving a license to use it.
If your business plans to register copyright in key software, the US Copyright Office process may also require you to identify parts of the work that were previously published, third-party, or not owned by you. Copyright exists automatically when original code is fixed in a tangible medium, but registration can matter if you ever need to enforce rights. For example, registration is generally needed before filing a copyright infringement lawsuit in the US, and timing can affect statutory damages and attorneys' fees.
Frequently Asked Questions
Can I Still Sell My Business If The Website IP Is Messy?
Yes, but messy IP can slow the sale, reduce buyer confidence, or lead to a holdback until the issue is fixed. Buyers usually want clear evidence that your business owns or can transfer the website assets it relies on.
Is A Paid Invoice Enough To Prove I Own The Code?
No, not usually. A paid invoice helps show there was a project and payment, but copyright ownership usually needs a written assignment signed by the owner of the rights.
Should I Register Copyright In My Website Code?
It depends on how valuable and original the code is. Registration with the US Copyright Office isn't required for copyright to exist, but it can strengthen your position if enforcement becomes necessary.
How Much Does It Cost To Fix Website IP Ownership?
The cost depends on how many documents need review, whether the developer cooperates, how many contributors were involved, and whether source code handover is part of the deal. A free template may miss key software issues, an online fixed-fee service may give you more certainty up front, and a traditional firm billing hourly may suit more complex negotiations.
Key Takeaways
- Paying a freelancer doesn't automatically mean your business owns the website code.
- Under the Copyright Act, contractor-created code usually needs a written assignment if you want clear ownership.
- Start by collecting the contract trail, payment records, access details and all project communications.
- A cleanup document can assign custom IP, license background code and require source code handover.
- Third-party plugins, open source packages and paid tools need their own review because the developer may not own them.
- If you're selling, raising funds or relaunching, fix the IP position early so it doesn't derail the next step.
If you'd like help with reviewing your developer contract, preparing an IP assignment, and negotiating source code handover, you can reach our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they're provided by licensed US lawyers at ElevateNext US, LLC, a trusted US law firm, through the Sprintlaw platform.
Drafted by Taylor, Sprintlaw's AI, and overseen by Alex Solo. How we write







