What To Do If A Contractor Won't Hand Over Source Files

byAlex Solo10 min read

What can you do if a contractor won't hand over source files after you've paid for the work? The reassuring first answer is this: you may have strong options, but the right next step depends heavily on your contract.

When a developer, designer, freelancer or agency holds onto code, design files, login details or other project assets, it can feel like your business is stuck in someone else's hands. You might be unable to launch, change suppliers, fix bugs, update your branding or keep trading smoothly.

The good news is that these disputes often turn on a few practical issues: what was promised, who owns the IP, whether payment is due, and what a sensible handover should look like.

Can A Contractor Refuse To Hand Over Source Files?

Yes, sometimes a contractor can refuse to hand over source files, but only if the contract, payment position or ownership rights support that refusal.

Start with the contract. Look for the parts that describe the deliverables. This might include:

  • source code, object code, repositories and deployment files
  • editable design files, such as layered design files or brand assets
  • website themes, plugins, templates and configuration files
  • admin logins, hosting access, domain access and API keys
  • documentation, user guides and technical handover notes
  • third-party licenses, fonts, stock images or software dependencies

If the contract only says the contractor will deliver a finished website, app, logo or campaign, it may be less clear whether editable or behind-the-scenes files were included. A finished website isn't always the same thing as source code. A logo image isn't always the same thing as the editable vector file.

Payment matters too. Some contracts say the contractor doesn't need to release final deliverables until invoices are paid. Others say ownership transfers only after full payment. If you're withholding payment because the work is incomplete, you may need to show exactly what hasn't been delivered and why payment isn't yet due.

If there's no written contractor agreement, you can still look at emails, proposals, quotes, invoices, project management comments and messages. Those records can help show what both sides expected.

Who Owns The Source Code Or Design Files?

It depends, but under the federal Copyright Act, the creator usually owns copyright unless there's a written assignment or the work qualifies as a narrow category of work made for hire.

This surprises a lot of businesses. Paying a contractor to build your website, write code, create graphics or design packaging doesn't automatically mean your business owns all copyright in those files. Payment gives you strong commercial expectations, but copyright ownership usually needs clear wording.

For software, copyright can cover source code and object code. For creative work, it can cover illustrations, copy, photos, layouts, music, videos and design assets. For your brand, federal trademark law under the Lanham Act protects names, logos and other signs that identify your goods or services, but trademark ownership is a different question from who owns the editable artwork file.

Check whether your contract says:

  • assignment: the contractor assigns all rights, title and interest in the work to your business
  • license: your business can use the work, but the contractor keeps ownership
  • work made for hire: the parties agreed to that status in writing, and the work fits a legally recognized category
  • pre-existing materials: the contractor keeps ownership of reusable tools, code libraries, templates or know-how
  • third-party materials: you only get the rights the contractor was allowed to pass on

For many contractor projects, a tailored assignment plus a license back for the contractor's pre-existing materials is cleaner than relying on work made for hire wording alone.

What Should You Check Before Sending A Demand Letter?

You should check the contract, payment records, deliverables list and project communications before sending a demand letter.

A demand letter works best when it's specific. A vague complaint or waiver of rights like "send everything now" is easier to ignore. A clear letter that says what is missing, why it's owed and when you need it's much stronger.

Step 1: Build A Deliverables List

Create a simple list of what you're missing. Separate the items into practical categories:

  • must-have to operate: live site files, app repository, database exports, hosting access, admin credentials
  • must-have to change suppliers: source code, design files, documentation, deployment instructions
  • nice to have: working notes, old mockups, unused concepts or drafts

Step 2: Match Each Item To The Contract

Next to each item, write down where it appears in the contract, quote, proposal or email chain. If it isn't clearly listed, note why you think it was part of the deal. For example, maybe the proposal said the project included "complete brand files" or "full code handover on final payment".

Step 3: Check The Money

Confirm what has been paid, what remains unpaid and whether any amount is genuinely disputed. If the contract has milestones, check whether the contractor reached each milestone. If you paid a 50% deposit and the final 50% is due only after handover, say that clearly.

Under general contract principles, the wording matters. Some obligations are independent. Others are conditional on payment, approval or acceptance. The Uniform Commercial Code can also affect certain transactions involving goods, but custom software and creative services often turn on the contract and state law. If the project mixes goods, software and services, get tailored advice.

How Do You Ask For Source Files Without Escalating Too Fast?

You can start with a calm written request that gives a clear handover list, deadline and payment position.

You don't need to make the first message aggressive. Many disputes happen because both sides are working from different assumptions. A developer may think you only bought a working website. You may think you bought the full repository. A designer may think editable files cost extra. You may think they were included.

Try this approach first:

  • keep the tone professional and factual
  • attach or refer to the relevant contract sections
  • list each file, account or access item you need
  • state what has been paid and what remains outstanding
  • offer a reasonable handover process, such as a shared drive transfer or repository access
  • give a practical deadline, often 5 to 10 business days depending on urgency and project size
  • avoid threats you aren't ready to follow through on

Say Mike runs a subscription meal planning platform. He paid a freelancer $18,000 in three milestones to build a custom web app. The final invoice is $3,000, but the freelancer won't give him repository access unless he pays first. Mike checks the contract and sees the final milestone says "handover of source code, database schema and deployment instructions" before final acceptance. His best first move isn't just to refuse payment. It's to write to the freelancer, identify the final milestone wording, offer to pay the $3,000 immediately after complete handover, and propose a date for a screen-share handover session.

That gives the contractor a clear path to get paid and gives Mike a written record if the dispute continues.

What Should A Demand Letter Or Settlement Agreement Include?

A demand letter should set out what you want, why you're entitled to it, and what happens next if the contractor doesn't respond.

If the first written request doesn't work, a more formal demand letter may be the next step. You may also need a short settlement agreement if both sides agree to a compromise, such as partial payment in exchange for file handover and a release.

Templates often miss the details that matter most in source file disputes, especially IP ownership, software license terms, third-party materials and access credentials. A lawyer should tailor any demand letter or settlement document before you use it.

Demand Letter Outline

  1. Parties And Project: identify your business, the contractor and the project.
  2. Contract Background: list the agreement date, proposal, quote or key emails.
  3. Deliverables Owed: itemize the files, access credentials and documentation required.
  4. Payment Position: state what has been paid, what is outstanding and whether any payment is conditional.
  5. IP Position: explain the assignment, license or ownership wording you rely on.
  6. Handover Method: say how the files should be delivered, such as repository access, export files or shared folder transfer.
  7. Deadline: give a clear date and time for response or handover.
  8. Reservation Of Rights: state that your business reserves its rights if the issue isn't resolved.

Settlement Agreement Outline

  1. Handover Items: list exactly what the contractor will provide.
  2. Payment Terms: say what you'll pay, when you'll pay it and whether payment is held until verification.
  3. IP Assignment Or License: confirm who owns the work and what rights each side keeps.
  4. Third-Party Materials: identify fonts, stock assets, plugins, libraries and license limits.
  5. Confidentiality: protect your business information, credentials and trade secrets.
  6. Mutual Release: set out what claims each side is releasing, if any.
  7. No Admission: say the settlement doesn't mean either side admits fault.
  8. Cooperation: require reasonable help with access, passwords, deployment and transition questions.

What If The Contractor Is Withholding Code, Logins Or Trade Secrets?

You should act quickly if the contractor is holding critical code, credentials or confidential business information, especially if your operations are affected.

Start by protecting what you still control. Change passwords for accounts you own. Check who has admin access to hosting, domains, analytics, payment tools, customer databases, cloud storage and project management platforms. Keep screenshots showing access, lockouts, deleted files or refusal messages.

If your source code or business data includes confidential information, trade secret law may also matter. The federal Defend Trade Secrets Act can protect business information that derives value from being secret, if you've taken reasonable steps to keep it secret. That could include private repositories, access controls, confidentiality clauses, password protection and limiting who can view sensitive information.

If the contractor is also using your brand name, logo or customer-facing materials in a way that confuses customers, federal trademark law may be relevant too. If they copied or reused your creative work beyond what was allowed, copyright law may be relevant. The Copyright Office handles copyright registration, and registration can affect enforcement options.

Be careful with self-help. For example, don't access systems you're not authorized to access, even if you paid for the project. Don't make public accusations that could inflame the dispute. Focus on records, access control, contract rights and a clean written demand.

How Can You Avoid This Problem In Your Next Contractor Agreement?

You can avoid most source file disputes by making file handover, IP ownership and payment milestones crystal clear before work starts.

Your independent contractor agreement should say more than "build a website" or "create brand assets". It should explain what your business gets at the end, in what format, and when.

For a developer, consider wording that covers:

  • source code repository access
  • database schema and exports
  • deployment scripts and environment notes
  • technical documentation
  • admin accounts and credentials handover
  • open-source and third-party components
  • security obligations and deletion of confidential information after handover

For a designer or agency, consider wording that covers:

  • editable design files
  • final export files
  • font files or font license details
  • stock image license details
  • brand guidelines
  • unused concepts, if you want them included
  • social media, ad account or website access

Payment milestones should line up with handover. For example, you might pay 40% upfront, 40% after a working draft, and 20% after complete handover and a defined acceptance period. If final payment is due before handover, say so. If final payment is due after handover, say that too.

You should also decide whether the contractor can reuse any part of the work. Many developers and designers rely on reusable tools, snippets, templates and systems. A fair contract can let them keep those pre-existing materials while giving your business the rights it needs to operate, modify and grow.

Frequently Asked Questions

Can I Withhold Final Payment Until I Receive The Files?

It depends on your contract. If final payment is conditional on delivery or acceptance, you may have a strong basis to withhold it, but if payment is due first, withholding it could put your business in breach.

Are Editable Design Files Automatically Included?

No, not always. A finished logo, PDF, image or website design doesn't automatically include editable design files unless the contract, quote or communications say they do.

What If The Contractor Used Open-Source Code?

Open-source code can be fine, but the license terms matter. Some licenses require notices, source code availability or limits on commercial use, so ask for a list of open-source components and license details.

Should I Pay Something To Settle The Dispute?

Sometimes paying a negotiated amount is cheaper and faster than a prolonged dispute, especially if you need the assets urgently. Put any settlement in writing before money changes hands.

Key Takeaways

  • If a contractor won't hand over source files, start by checking the contract, quote, emails, payment milestones and deliverables list.
  • Under the Copyright Act, paying for work doesn't always mean you own the copyright. Look for a written assignment or clear license terms.
  • A calm written request should identify the missing files, the handover method, the payment position and a practical deadline.
  • If the issue escalates, a demand letter or settlement agreement should deal with deliverables, payment, IP ownership, confidentiality and release terms.
  • For future projects, spell out source code, editable files, logins, third-party assets and final payment conditions before work starts.

If you'd like help with reviewing your contractor agreement, recovering project assets, preparing a demand letter or documenting a settlement, 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

Alex Solo
Alex SoloCo-Founder

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.

Need legal help?

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.