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.
You paid a freelancer to design your brand, build your website, write code, create content or manage your accounts. Now the project is stuck because they won't hand over final files, source code, login access or the work you need to keep operating.
It's frustrating, especially when a launch date, customer campaign or investor update is on the line. The good news is that you usually have a few practical options before things become a formal dispute.
The right move depends on your contract, what was actually promised, what you've paid, and who owns the underlying intellectual property. Let's work through the steps in a way you can use today.
What Should You Do First If A Freelancer Won't Hand Over Files?
First, pause the back-and-forth and gather the contract, payment records and project messages before you send another demand. You need to know exactly what the freelancer agreed to deliver.
Look for these documents and records:
- Written agreement: a services agreement, statement of work, proposal, quote, email acceptance or online terms.
- Deliverables list: anything that names file types, source files, source code, working files, login credentials, repositories, admin access or editable formats.
- Milestones and payment terms: when payment was due, whether final payment is tied to delivery, and whether there's a cure period for missed deadlines.
- IP ownership clause: whether copyright, design files, code, templates or other rights are assigned to your business.
- Termination clause: what happens if either side ends the project before completion.
- Messages: emails, chat messages, project management comments and file transfer records showing what was promised and what was delivered.
Then write a short timeline. For example: deposit paid on May 1, first draft due May 15, final files due May 30, final invoice paid June 2, files still not provided as of June 10.
This helps you separate a legal issue from a communication issue. Sometimes the freelancer is withholding files because of an unpaid invoice. Sometimes they're refusing to deliver work they were clearly paid to provide. Those are very different conversations.
Does The Freelancer Have To Give You Source Files Or Source Code?
It depends on what your agreement says. In many projects, final output and source files aren't automatically the same thing.
For a designer, the final output might be PDF, PNG, JPG or SVG files. The source files might be editable Adobe Illustrator, Photoshop, InDesign, Figma or Canva files. For a developer, the final output might be a working website or app. The source code, repository access, build files, documentation and deployment credentials may be separate deliverables.
If your contract clearly says the freelancer must provide source files or source code, refusing to do so may be a breach of contract. Your next step is usually a written notice asking them to deliver the missing items by a specific date.
If your contract only says they will provide a completed logo, website or app, the answer is less clear. You may still have arguments based on the project scope, emails, industry context or what the freelancer said during the sales process. But you may not be able to assume that every working file, plugin, framework, template or editable asset is included.
Login access is a little different. If the account belongs to your business, such as your hosting account, domain account, email platform or advertising account, you should usually have admin access. Instead of asking someone to email passwords, ask for a secure admin transfer, removal of their access, and confirmation that recovery details have been updated to your business email.
Who Owns The Work If You Paid For It?
Payment alone doesn't always mean your business owns the copyright. Under the US Copyright Act, a freelancer usually owns the copyright in what they create unless there's a signed written assignment, a work for hire agreement, or another basis for treating it as work made for hire.
Work made for hire is narrower than many people expect. It usually covers work created by an employee within the scope of their job, or certain specially commissioned works where the parties sign a written agreement saying it's work made for hire and the work fits within specific legal categories. Many common freelancer projects don't fit neatly into those categories.
That means your contract matters a lot. Ideally, it should say that the freelancer assigns to your business all rights, title and interest in the deliverables, including copyright, once agreed conditions are met. Sometimes the assignment only happens after full payment. Sometimes it happens as work is created. The difference can be huge if a dispute starts halfway through the project.
You may still have an implied license to use the work for the purpose everyone understood, especially if you paid for it and the freelancer delivered it for use in your business. But an implied license may not let you edit, resell, sublicense or transfer the work freely.
For logos and brand assets, trademark rights can also matter. Federal trademark rights under the Lanham Act focus on use of a mark in commerce, but you still want clear ownership of the artwork and permission to modify it. If you plan to file with the USPTO, clean IP paperwork can make the process smoother.
How Do You Negotiate Release Without Making Things Worse?
Start with a calm written request that ties the missing files to the agreement and gives a clear path to resolution. You want to sound firm, not heated.
A useful message usually includes:
- The project details: name the project, dates and agreement or proposal.
- The missing items: list each file, folder, code repository, credential or access permission.
- The contract basis: quote the deliverables clause, IP clause, milestone or email promise if you have one.
- Your requested deadline: choose a specific date and time, especially if your contract has a notice or cure period.
- Payment position: say whether invoices are paid, disputed or ready to be paid on delivery.
- Access method: ask for secure transfer, not password sharing.
- Next step: say you want to resolve it commercially, but you'll consider your options if the files aren't delivered.
A Worked Example
Say Maya runs an online skincare business. She pays a designer $4,000 for a brand refresh, with $3,000 paid upfront and $1,000 due on final delivery. The signed proposal says the final package includes logo files in PNG, SVG and AI formats, plus a 12-page brand guide.
The designer sends PNG files only and asks for the final $1,000 before releasing the AI files. Maya checks the proposal and sees that final payment is due upon delivery of the final package, not before.
Maya sends a short notice listing the missing AI files and brand guide, attaches proof of the $3,000 payment, and says she'll pay the remaining $1,000 within one business day after receiving the full final package. She gives a five business day deadline because the proposal has a five business day cure period.
That kind of message keeps the focus on the contract and gives both sides a practical way out.
What Records Should You Keep If The Dispute Continues?
Keep records that show the promise, the payment, the missing work and the business impact. If you need an attorney to step in, good records make the advice faster and more useful.
Create one folder with:
- The agreement and scope: signed documents, quotes, proposals, purchase orders and accepted terms.
- Invoices and receipts: deposit, milestone and final payment records.
- Delivery evidence: links, downloads, file transfer notifications, repository logs and screenshots.
- Access evidence: who has admin access, who owns the account, and any access changes.
- Communications: emails, messages and meeting notes, saved in date order.
- Business impact: missed launch dates, extra costs, replacement developer estimates or customer delays.
Try not to lock the freelancer out of systems or remove their access in a way that breaks the project unless you have a clear operational reason. If there's a security concern, act quickly to protect your business, but keep a record of what you changed and why.
Federal law can also become relevant when source code, confidential information or access credentials are involved. The Defend Trade Secrets Act may help protect trade secrets if you've taken reasonable steps to keep them secret. Platform access and unauthorized access issues can raise separate legal concerns, so get tailored advice before taking aggressive technical steps.
State law can affect contract remedies, deadlines and available claims. You don't need to solve that on your own, but you should avoid threats you can't back up.
How Do You Prevent This Happening Again?
The best way to prevent this is to make your service agreement specific about deliverables, ownership, access and handover. Vague scopes are where many freelancer disputes begin.
For future projects, your agreement should cover:
- Exactly what will be delivered, including file formats and editable files.
- Whether source code, design files, raw footage, datasets, prompts, templates or documentation are included.
- Who owns IP in the final work and when that ownership transfers.
- Whether the freelancer can reuse pre-existing tools, code, libraries or templates.
- What third-party licenses apply, including fonts, stock images, plugins or open source components, and whether an open source policy applies.
- When payment is due and whether payment is conditional on delivery.
- Who owns and controls accounts, domains, repositories and hosting.
- What happens on termination, including whether a termination agreement is needed and how work in progress will be handed over.
- Confidentiality and trade secret protection.
- Dispute steps before either side walks away.
A Fill-In Outline For Your Next Freelancer Agreement
This outline isn't a finished legal document. A lawyer should tailor it before you use it, because a design project, software build and marketing campaign can need very different wording.
- Parties: name your business and the freelancer or contractor correctly.
- Project Scope: describe the work, milestones, assumptions and exclusions.
- Deliverables: list final files, source files, formats, repositories, documentation and access to be handed over.
- Timeline: set deadlines, review periods and what happens if feedback is late.
- Fees And Payment: state deposits, milestone payments, final payment triggers and disputed invoice steps.
- IP Ownership: say what your business owns, when ownership transfers, and what rights are only licensed.
- Pre-Existing Materials: identify freelancer tools, templates, code libraries and third-party materials that aren't assigned.
- Accounts And Access: require business-owned accounts, admin rights and secure handover.
- Confidentiality: protect business information, customer data, code, strategy and trade secrets.
- Acceptance And Revisions: explain how you approve work and how many revision rounds are included.
- Termination And Handover: require delivery of work completed to date and orderly access transfer.
- Dispute Process: set a practical notice process before either side escalates.
Templates can be a useful starting point, but they often miss the details that matter most when files, code and access are at stake.
Frequently Asked Questions
Can I Refuse To Pay The Final Invoice Until I Get The Files?
Sometimes, yes, if your contract makes final payment conditional on delivery or the freelancer hasn't met an agreed milestone. If the payment terms are unclear, get advice before withholding payment, because non-payment can give the freelancer their own claim.
Can I Hire Someone Else To Rebuild The Work?
You can usually hire a replacement, but be careful about using code, designs or files that you don't own or don't have permission to modify. Ask the replacement provider to document what they create from scratch and what existing materials they use.
What If The Freelancer Deleted The Files?
If the freelancer was contractually required to deliver or preserve the files, deletion may strengthen your breach of contract position. Keep evidence of the request, their response and the cost of recreating the work.
Should I Send A Formal Demand Letter?
A demand letter can help when a calm request hasn't worked, especially if the contract is clear. It should be accurate, measured and based on the documents, not threats or assumptions.
Key Takeaways
- If a freelancer won't hand over files, start by checking the contract, scope, payment terms and messages before escalating.
- Source files, source code and editable working files aren't always included unless the agreement says so.
- Under the US Copyright Act, paying for work doesn't automatically mean your business owns the copyright.
- A calm written notice should list the missing items, refer to the agreement and give a practical deadline.
- For future projects, your agreement should clearly cover deliverables, IP ownership, access, payment and handover.
- State law and your contract can change the remedies available, so get tailored advice if the dispute is affecting your business.
If you'd like help with reviewing your freelancer agreement, negotiating release of your files, or tightening your IP, confidentiality and access clauses, 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








