There is no federal non-compete ban in 2026. The FTC's 2024 rule was blocked in court, the agency withdrew its appeal in September 2025, and the rule was formally struck from the Code of Federal Regulations in February 2026. Enforceability now depends entirely on state law: California, Minnesota, North Dakota, and Oklahoma void most non-competes outright, a growing list of states restrict them by wage threshold, and most others allow them if reasonably tailored. For a remote hire, the controlling law is generally the state where the employee actually works, not where your company is headquartered, which trips up more hiring managers than the ban itself ever did.
Somewhere in the last two years, a lot of hiring managers absorbed a headline about non-competes getting banned and never quite caught the follow-up story. It's an understandable mix-up. In April 2024, the FTC did issue a sweeping rule that would have voided nearly every employee non-compete in the country. It just never took effect, and the legal fight over it is now, definitively, over.
What's left in its place is arguably more complicated to navigate than a clean nationwide ban would have been: a patchwork of state laws pulling in different directions, several of which changed again just this year, layered on top of a workforce that increasingly works remotely from a state that has nothing to do with where the company is headquartered.
What Actually Happened to the FTC's Ban
The timeline matters, because it explains why so much lingering confusion is out there. The FTC finalized its non-compete ban in April 2024. A federal court in Texas blocked it nationwide that August, ruling the agency had exceeded its rulemaking authority. The FTC initially appealed, then withdrew that appeal in September 2025 under a new chair, ending the federal effort. In February 2026, the agency formally removed the rule from the Code of Federal Regulations, closing the loop administratively.
The FTC hasn't disappeared from this space entirely. It's shifted from broad rulemaking to targeted, case-by-case enforcement against specific employers, including a consent order against a national pest control company earlier this year. But that's a narrower tool than a blanket rule, and it doesn't change the baseline: whether a non-compete is enforceable now depends on the law of the state where the employee actually works.
Where Non-Competes Stand State by State
The state landscape isn't static, and several changes just happened or are about to.
States With Near-Total Bans
California, Minnesota, North Dakota, and Oklahoma void most employee non-competes outright today. Washington joins this group on June 30, 2027, under a law that applies retroactively to agreements signed before that date, meaning a Washington non-compete signed this year could become void once the law takes effect regardless of when it was signed.
States With Wage-Threshold or Conditional Restrictions
A growing list, including Colorado, Illinois, Massachusetts, Oregon, and Virginia, restricts non-competes to roles above a specified salary level or under specific conditions. Virginia's new rule, effective July 1, 2026, voids a non-compete if the employer terminates the employee without cause and doesn't provide severance, a meaningful new wrinkle for anyone relying on a standard template.
States That Apply a Reasonableness Test
Most remaining states will enforce a non-compete if it's reasonably tailored in scope, duration, and geography to a legitimate business interest, though courts have grown more skeptical of loosely drafted agreements even in employer-friendly jurisdictions.
The Outlier Moving the Other Direction
Florida passed a law making non-competes easier to enforce, a reminder that this landscape isn't moving in one uniform direction even as most states tighten restrictions.
The Rule Most Hiring Managers Get Wrong
The single most common mistake in 2026 isn't misjudging which state has the strictest law. It's assuming the company's home state law applies to a remote hire at all. Generally, the state that actually governs a non-compete is the one where the employee performs the work, not the employer's headquarters and not necessarily whatever state is named in the contract's governing-law clause.
California and Minnesota have gone a step further, passing statutes that explicitly void out-of-state choice-of-law clauses written specifically to route around local employee protections. In practice, that means a company headquartered in, say, Delaware, with a governing-law clause pointing to Delaware or another employer-friendly state, can still find that clause worthless the moment the employee in question is actually living and working in California.
A remote hiring footprint spread across a dozen states means a dozen different possible answers to "is this non-compete enforceable," and the answer for each one turns on where that specific employee sits, not on anything the company's legal template assumed when it was drafted.
What This Means When You're Hiring
When a strong candidate discloses an existing non-compete from a competitor, the instinct is often to treat the letter from their old employer's counsel as the final word, either as an automatic dealbreaker or something to wave off entirely. Neither reaction is grounded in what actually determines enforceability. The real first question is which state's law governs based on where the candidate has actually been working, since that alone can make the agreement close to meaningless or genuinely binding. This is worth a real answer from employment counsel before extending an offer with a specific start date or scope of responsibilities that assumes the non-compete either matters or doesn't.
What This Means for Retention
The flip side is protecting the company's own competitive position when an eCommerce director or VP with deep knowledge of pricing strategy, supplier relationships, or growth playbooks leaves for a direct competitor. In a growing number of states, a broad non-compete simply isn't the tool that's going to hold up. For most roles, a well-drafted non-solicitation agreement paired with a strong NDA protects the same real interests, customer relationships and confidential information, with meaningfully less legal risk and a better track record of actually surviving a court challenge.
That leaves genuine non-competes as a tool worth the added legal complexity for a narrower tier: senior, customer-facing, or strategy-setting roles where the specific risk is someone taking deep, current competitive intelligence directly to a rival. A blanket non-compete applied uniformly across every hire, regardless of level, is increasingly both the wrong tool for the job and, depending on the state, simply unenforceable.
A Practical Playbook for 2026
- Know the actual work state of every remote employee and candidate, not just the company's headquarters state, since that's what determines which law applies.
- Segment protection strategy by role tier rather than applying one template company-wide. Save true non-competes for the roles where the risk genuinely justifies them.
- Build in non-solicitation and NDA protections as the default for most roles, since they protect similar interests with less legal exposure.
- Review any standing non-compete template against this year's state-law changes specifically, Washington's upcoming ban and Virginia's new without-cause carve-out are exactly the kind of updates a template written even a year ago won't reflect.
- Loop in employment counsel before making commitments to a candidate who's currently bound by a non-compete from a previous employer, rather than treating it as a hiring-manager judgment call.
None of this requires becoming an employment lawyer. It requires treating "which state's law actually applies here" as a real question with a real answer, rather than an assumption borrowed from wherever the company happens to be headquartered.
Frequently Asked Questions
Is there a federal ban on non-competes in 2026?
No. The FTC issued a rule in April 2024 banning nearly all non-competes nationwide, but a federal court blocked it in August 2024, the FTC withdrew its appeal in September 2025, and the agency formally struck the rule from the Code of Federal Regulations in February 2026. No federal ban exists, and none is expected in the near term. Enforceability is governed entirely by state law.
Which states ban non-competes outright?
California, Minnesota, North Dakota, and Oklahoma currently void most employee non-competes outright. Washington joins that group on June 30, 2027, under a law that applies retroactively to agreements signed before that date. A growing list of other states, including Colorado, Illinois, Massachusetts, Oregon, and Virginia, allow non-competes only above a wage threshold or under specific conditions, while most remaining states permit them if they're reasonably tailored in scope, duration, and geography. Florida moved the opposite direction, passing a law that makes non-competes easier to enforce.
Which state's law governs a remote employee's non-compete?
Generally, the law of the state where the employee actually performs the work, not where the company is headquartered or what governing-law clause is written into the contract. California and Minnesota have gone further and passed statutes that explicitly void out-of-state choice-of-law clauses written to get around local protections, meaning a non-compete governed by a different state's law on paper can become unenforceable the moment the employee is working from California, regardless of what the contract says.
Should eCommerce companies still use non-competes?
For most roles, a well-drafted non-solicitation agreement and NDA protect the same competitive interests, customer relationships and trade secrets, with far less legal risk and better odds of holding up in court. Non-competes are worth the legal complexity mainly for a small tier of senior, customer-facing, or strategy-setting roles where the real risk is someone taking deep competitive knowledge directly to a competitor. A blanket non-compete applied to every hire regardless of level is increasingly the wrong tool, and in a growing number of states, simply unenforceable.
What should hiring managers do when a candidate has an existing non-compete?
Find out which state actually governs the agreement based on where the candidate has been working, not just what the document says, before assuming it's a dealbreaker or a non-issue either way. In an outright-ban state the agreement may carry little weight regardless of its language. In a reasonableness-test state, the details, scope, duration, and geography, matter enormously. This is a genuine legal question, not a judgment call for a hiring manager to make alone, so involve employment counsel before making promises about start dates or role scope to a candidate who's still bound by one.