The short answer: check the state, not just the contract
A noncompete clause in a freelance contract is only as strong as the state law behind it, and in 2026 that law moved in four states at once. Tennessee now voids noncompetes for employees earning under $70,000 a year. Virginia now makes a noncompete unenforceable against a worker fired without cause who got no severance. Louisiana now bars noncompetes for interns and apprentices. And Washington passed a near-total ban that takes effect June 30, 2027 — including for independent contractors, and including agreements signed before that date.
That last point matters most for freelancers. Most freelance advice about noncompetes still reads like it was written for employees in one state, with one employer, under one set of rules. Your reality is different. You may live in one state, sign a contract governed by the laws of another, and work for clients in five more. A clause that looks standard in the paperwork can be void where you live, enforceable where the client sits, or rewritten by a court into something narrower than either side expected.
This guide is written for that reality. It walks through what actually changed in 2026, which clauses still have teeth, and what to propose instead of signing a broad noncompete. If you are reviewing a full agreement, read it alongside a checklist of the clauses every freelance contract needs — the noncompete is only one paragraph in a document where the payment, IP, and termination terms matter just as much. One important boundary up front: this is general information about state laws, not legal advice for your specific contract. If a client threatens to enforce a clause against you, or if a contract is worth a large share of your income, talk to an employment lawyer licensed in the relevant state before you sign, break, or ignore anything.
What changed in 2026, state by state
Tennessee: a $70,000 floor and a two-year presumption
Tennessee’s House Bill 1034, signed May 7, 2026, took effect July 1, 2026 for noncompetes entered into, renewed, or amended on or after that date. A law-firm analysis of the Tennessee and Virginia laws confirms the $70,000 threshold and the duration presumptions summarized here. It does two things freelancers should understand separately, because they do different work.
First, it bars employers from requiring, requesting, or enforcing a noncompete against an employee earning less than $70,000 in annualized compensation. That figure includes wages, salary, commissions, and nondiscretionary bonuses. For hourly workers, the law annualizes pay by multiplying the hourly rate by 40 hours and then by 52 weeks. A noncompete below that threshold is void and unenforceable, not merely weak.
Second, it creates rebuttable presumptions about duration. A restriction of two years or less is presumed reasonable for employees and independent contractors. For distributors, dealers, franchisees, and certain licensees, the presumption runs to three years. For sale-of-business deals, it runs to five years or the payment period, whichever is longer. “Presumed reasonable” is not the same as “automatically enforceable.” It shifts the argument, but a court can still find a clause unreasonable on its scope, geography, or the interest it protects. Tennessee courts also got express authority to “blue pencil” an overbroad covenant — to trim it down to something reasonable rather than throwing it out entirely. That is a warning, not a comfort: a clause you assumed would fail outright might instead survive in a narrower form.
Here is the freelancer trap in Tennessee. The $70,000 ban is written for employees. The two-year duration presumption expressly covers independent contractors. So a freelancer working as a contractor in Tennessee should not read the $70,000 figure and assume they are automatically protected. Your protection depends on how the contract classifies you, what the clause actually restricts, and whether a court treats the relationship as employment in substance. If a client hands you a contractor agreement with a noncompete, the Tennessee question to ask is not “do I earn under $70,000?” but “does this clause restrict me for more than two years, across more geography or more work than the client can justify?”
Virginia: fired without cause, no severance, no noncompete
Virginia already banned noncompetes for low-wage employees before 2026. The 2026 change, Senate Bill 170, signed April 13, 2026 and effective July 1, 2026, adds a new trigger tied to how the work ends. A post-employment noncompete with a Virginia-based employee who is terminated without cause is unenforceable unless the employer provides severance benefits or another monetary payment.
For 2026, Virginia’s low-wage threshold sits at average weekly earnings of $1,507.01, or $78,364.52 a year. That figure is the statewide average weekly wage, and it moves annually, so a contract that was enforceable one year can fall under the threshold the next. The law also covers all workers entitled to overtime under the Fair Labor Standards Act — in plain terms, non-exempt workers — regardless of their weekly earnings.
For freelancers, the Virginia change matters in two less obvious ways. First, many freelance agreements are really employment in disguise: set hours, exclusive availability, integration into the client’s team, and payment that looks like a salary. If a dispute lands in court, classification is argued on facts, not on the label at the top of the agreement. Second, the severance rule gives you a concrete negotiation lever. If a client insists on a noncompete, the Virginia model suggests a fair trade: if they want to restrict your future work, they should pay for the restriction. A clause with no payment for the restricted period is exactly the kind of one-sided term the 2026 law pushes against.
Louisiana: interns and apprentices are out
Louisiana’s HB 315 (Act 150), effective August 1, 2026, bars noncompete provisions covering paid or unpaid interns and apprentices, for work after the internship or apprenticeship ends. Confidentiality, intellectual property, and data protection agreements remain enforceable. The act voids noncompetes entered into with an intern or apprentice as of August 1, 2026, though it does not expressly state that all pre-existing agreements are void, so older paperwork deserves a closer read.
Why does this belong in a freelancer guide? Because a large share of freelance careers start in exactly this grey zone: an unpaid or low-paid internship, a “trial project” that turns into regular work, or an apprenticeship-style arrangement with a studio or agency. If your first contract with a company was signed while you were an intern or apprentice, and it still purports to block you from working for competitors, Louisiana law now gives you a strong argument that the noncompete portion does not hold. The confidentiality and IP portions may still hold, and that distinction matters — you can be free to take new clients while still being bound not to share the old client’s trade secrets or hand over their files.
Washington: the ban coming June 30, 2027
Washington’s Engrossed Substitute House Bill 1155, signed March 23, 2026, is the biggest change on this list, and it is also the easiest to misunderstand because it has not taken effect yet. A detailed breakdown of Washington’s new ban confirms the June 30, 2027 effective date, the October 1, 2027 notice deadline, and the $5,000 statutory penalty for violations. From June 30, 2027, nearly all noncompete covenants are void and unenforceable in Washington, regardless of when the agreement was signed. The only real carve-out is for sale-of-business covenants where the person holds at least a 1% ownership interest.
Until that date, Washington’s current thresholds still apply: for 2026, noncompetes are void for employees earning less than $126,858.83 a year and for independent contractors earning less than $317,147.09. Duration over 18 months is presumed unreasonable, terms must be disclosed in writing by the time an offer is accepted, and a laid-off worker must be paid base salary during the restricted period, minus new earnings.
Three practical consequences follow. First, if you are a Washington freelancer, a noncompete signed today may already be unenforceable under the current thresholds, and it will be void under the ban next summer — but the ban does not protect you from a lawsuit filed before June 30, 2027, which would be governed by the current statute. Second, Washington employers must make reasonable efforts by October 1, 2027 to notify workers whose noncompetes are still in effect that those clauses are void. Third, the ban redefines what counts as a noncompete: an agreement blocking you from accepting business from a customer is treated as a noncompete, not a gentler non-solicitation clause.
The wider map freelancers keep missing
Tennessee, Virginia, Louisiana, and Washington are the 2026 headlines, but they are not the whole map, and a freelancer with clients in several states needs the wider picture before signing anything.
Illinois voids noncompetes for workers earning $75,000 a year or less in 2026, rising to $80,000 on January 1, 2027, and voids non-solicitation agreements for workers earning $45,000 or less, rising to $50,000 in 2027. Colorado voids noncompetes for workers earning less than $130,014 in 2026, with a lower threshold for non-solicitation agreements. Oregon voids noncompetes below $119,541 in 2026 and caps duration at 12 months. Minnesota voided noncompetes for all workers for agreements signed after July 1, 2023. California, North Dakota, and Oklahoma have long treated most noncompetes as void, with narrow sale-of-business exceptions.
The pattern is consistent: states are moving toward income floors, shorter durations, and outright bans, with floors high enough to cover most early-career and mid-career freelancers. But there is no federal ban, so your rights still depend on state law, and a choice-of-law clause creates real litigation risk without being automatically decisive.
| State | 2026 change or key threshold | What it means for freelancers |
|---|---|---|
| Tennessee | Under $70,000 ban (employees); 2-year presumption for contractors | Contractor clauses over 2 years face a presumption of unreasonableness |
| Virginia | No-cause firing without severance voids the clause; low-wage bar at $78,364.52 | Ask for paid restriction periods; check classification, not just the label |
| Louisiana | Intern/apprentice noncompetes barred from Aug 1, 2026 | Early-career contracts may have a void noncompete but a live NDA |
| Washington | Near-total ban from June 30, 2027; 2026 contractor floor $317,147.09 | Most freelancer clauses die in 2027; pre-2027 suits use current law |
| Illinois | $75,000 bar in 2026, $80,000 from Jan 1, 2027 | Mid-career freelancers gain protection at the turn of the year |
| Colorado | $130,014 bar in 2026 | High floor covers most independent workers |
What still has teeth: NDAs, non-solicits, and IP clauses
One of the most common freelancer mistakes in 2026 is celebrating the death of a noncompete while ignoring the three clauses right next to it that still bind. Every one of the 2026 state changes preserves confidentiality agreements, and most preserve properly drawn non-solicitation and intellectual property clauses. That is not a loophole. It is the point. States are protecting workers’ ability to earn a living, not giving anyone a right to hand a former client’s customer list to a competitor.
A confidentiality clause can still bar you from disclosing trade secrets, proprietary processes, unreleased product details, and non-public client data. An IP assignment clause can still transfer ownership of work you created for the client, within the scope you agreed. A non-solicitation clause can still bar you from actively recruiting the client’s employees or pitching customers you personally served — provided it is drawn narrowly, limited in time, and, in Washington after June 2027, limited to customers you dealt with directly and to 18 months.
What states are killing is the broad version: a clause that says you cannot work in your entire field, for any competitor, anywhere, for two years, unpaid. When you review a contract, separate the clauses in your head. Ask of each one: what exactly does it stop me from doing, for whom, where, and for how long? A two-year ban on working for “any company in the technology industry worldwide” is a different animal from a 12-month ban on soliciting the three clients you personally managed. The first is the kind of clause 2026 laws target. The second is the kind most courts will still enforce.
The five freelancer traps hiding in plain sight
1. Renewal resets the clock
Tennessee’s law applies to agreements entered into, renewed, or amended on or after July 1, 2026. Washington’s ban reaches back to older agreements, but most state reforms do not. Every time you renew a retainer, sign a new statement of work that incorporates the old master agreement, or accept an amended rate card, you may be re-signing the noncompete under the new law — or, in a state that has not reformed yet, reaffirming a clause that would otherwise have expired. Before you renew, read the restrictive covenants again as if they were new. They effectively are.
2. The client list is not the industry
A clause that bars you from “competing” is often drafted to cover an entire industry, when the client’s legitimate interest is a handful of named competitors or direct clients. Push for a named list. “You may not provide brand-design services to Acme, Beta, and Gamma for 12 months” is a clause you can plan around. “You may not work in design” is a clause that can end your business. If a client refuses to name competitors, that refusal tells you something about how they intend to use the clause.
3. Unpaid restriction periods
A noncompete that pays you nothing during the restricted period is asking you to fund the client’s competitive advantage out of your own pocket. Virginia’s 2026 rule makes this explicit for no-cause terminations. Even where no statute requires payment, ask for it: a monthly payment during the restriction, a shorter restriction, or a buyout clause that lets the client pay to extend it. If the restriction is genuinely worth something to the client, they can pay for it. If they will not pay, they have told you what it is worth to them.
4. The platform terms you clicked past
Marketplace and agency platforms sometimes include noncompete or non-circumvention terms in their terms of service, separate from your client contract. A non-circumvention clause — which bars you from working directly with a client you met through the platform — is not the same as a noncompete, but it can have a similar effect on your pipeline. Read platform terms before you build a business on a platform, and keep a copy of the version you accepted. Platforms update terms quietly, and the version that governs a dispute is often the one in force when you accepted the work.
5. Geography that ignores remote work
Old noncompetes draw circles on maps: 50 miles from the client’s office, or the state where the client is headquartered. Remote freelancers do not work in circles. A clause that bars work “within 100 miles of Chicago” means little if your clients are worldwide, and a clause that bars work “anywhere the client does business” can mean everywhere. Replace geographic bans with client-based limits wherever possible. Geography made sense for a salesperson with a territory. It makes little sense for a designer, writer, or developer whose market is the internet.
What to propose instead of a broad noncompete
Clients ask for noncompetes because they are afraid of two things: losing customers and losing secrets. You can address both fears without signing away your livelihood, and offering an alternative usually works better than simply refusing.
Offer a narrow non-solicitation clause: for 12 months, you will not actively solicit the specific clients you served for this client, or recruit their employees. Offer a strong confidentiality clause with a clear definition of what counts as confidential, a carve-out for information that becomes public through no fault of yours, and a return-or-delete duty for client materials at the end of the engagement. Offer an IP clause that is scoped to the deliverables the client paid for, not to everything you create during the engagement — a distinction that matters enormously for freelancers who work on their own products alongside client work.
If the client still wants a true noncompete, negotiate its four dials down: duration, scope, geography, and consideration. Get a written release process: a short email from the client confirming that a specific new opportunity is not covered.
If a client threatens to enforce a clause
Do not ignore a threat letter, and do not reply with a legal argument you wrote yourself. Save everything: the contract, every amendment and renewal, the statements of work, and any emails about the clause. Note the dates that matter: when the agreement was signed, when it was last renewed, when the work ended, and whether you were paid any severance or restriction payment. Those dates decide which version of a state’s law applies.
Then get a short consultation with an employment lawyer in the state whose law is most likely to govern. Many lawyers will review a single clause for a fixed fee, and that review is often cheaper than either complying with a void clause for a year or breaching an enforceable one. Bring the whole agreement, not just the noncompete paragraph, because classification, choice-of-law, and severability clauses all change the analysis.
The bottom line for freelancers in 2026
The direction of travel is clear, and it favors freelancers. States are raising income floors, shortening durations, requiring payment for restrictions, and, in Washington’s case, banning noncompetes outright. But the protection is patchwork, and it rewards the freelancer who reads the contract, checks the state, and negotiates before signing.
Before your next contract, run this five-minute check. Which state’s law governs, and where do you actually work? Does the clause name specific competitors or an entire industry? Is the restriction paid, and for how long? Does renewal re-sign it? And what would you offer instead — a narrow non-solicit, a tight NDA, and scoped IP terms — that gives the client what they actually need? Answer those five questions in writing before you sign, and you will rarely be surprised by a noncompete again. If the contract also changes how you are paid or structured, compare the LLC versus S-corp choice for freelancers and run your real take-home pay after platform and payment fees before you agree to any restriction period.
This article is general information about state laws, not legal advice. Laws change, thresholds adjust annually, and the outcome for any specific contract depends on its exact wording and facts. For a contract that affects your livelihood, consult a licensed employment attorney in the relevant state.
Frequently Asked Questions
Are noncompetes banned everywhere in the US in 2026?
No. There is no nationwide ban. California, North Dakota, Minnesota, and Oklahoma void most noncompetes, and Washington’s near-total ban starts June 30, 2027, but most other states still enforce narrow, reasonable noncompetes. Your rights depend on the state where you work and the clause’s wording.
Does Tennessee’s $70,000 noncompete ban protect freelancers?
The $70,000 ban is written for employees, not independent contractors. Tennessee’s two-year duration presumption does cover independent contractors, so a contractor clause longer than two years faces a presumption of unreasonableness. Freelancers should not assume the $70,000 figure alone protects them.
What changed in Virginia for noncompetes in 2026?
From July 1, 2026, a noncompete with a Virginia-based employee fired without cause is unenforceable unless the employer provides severance or another monetary payment. Virginia also already bars noncompetes for low-wage workers, defined for 2026 as average weekly earnings below $1,507.01.
Will Washington’s noncompete ban void my existing agreement?
From June 30, 2027, Washington voids nearly all noncompete covenants regardless of when they were signed, except sale-of-business covenants. But lawsuits filed before that date are governed by the current law, with its 2026 income thresholds, so do not ignore a live clause today on the strength of the future ban.
Is a non-solicitation clause the same as a noncompete?
No, but the line is narrowing. A non-solicitation clause bars actively recruiting clients or employees, while a noncompete bars working in a field or for competitors. Washington’s 2027 law treats a clause that blocks accepting business from a customer as a noncompete, so a “non-solicit” drafted that broadly will be treated as a ban.
What should I ask for instead of signing a broad noncompete?
Offer a narrow non-solicitation clause for named clients, a clear confidentiality clause, and IP terms scoped to paid deliverables. If a true noncompete is required, negotiate duration, named competitors, and payment during the restricted period, plus a written release process for new opportunities.
