Beyond Age Verification: Four New Legislative Threats Targeting Adult Platforms in 2026

Age verification has consumed most of the adult industry's legal and lobbying bandwidth for the past two years — and for good reason, given the Supreme Court's ruling in Free Speech Coalition v. Paxton that upheld Texas's law and opened the door for 25+ states to begin enforcement. But while operators have been watching that front, state legislatures have been quietly opening three or four others.

The Free Speech Coalition's early 2026 legislative roundup identifies four distinct categories of bills now moving through state legislatures — each with meaningfully different compliance implications for platform operators. None of these are theoretical. Several are already past committee.

---

1. Punitive Taxation on Adult Content

States: Utah (SB 73), Virginia (HB 720), Alabama (existing law)

Virginia's HB 720 has been tabled until next session, but Utah's SB 73 is still active. If it passes, Utah will join Alabama as the second state to impose a content-based excise tax specifically on adult speech.

This is a novel enforcement mechanism that's worth taking seriously. Unlike fines tied to specific violations, a recurring tax creates permanent, compounding compliance overhead. More concerning: content-based taxation has historically survived constitutional challenge more easily than outright bans, because courts apply different scrutiny to tax schemes than to direct speech restrictions.

What this means operationally: If Utah's bill passes, platforms with Utah-based revenue will need to track adult content sales separately for state tax reporting — similar to how sin taxes work for tobacco or alcohol. Depending on bill language, this could also affect platforms based outside Utah that serve Utah residents.

Watch for this model to spread. Alabama's law provides a template. If Utah validates it, expect copycat legislation in 8-12 other states within 18 months.

---

2. Consent Documentation Minefields

States: Arizona (HB 2133), North Carolina (existing), Alabama (existing)

Arizona's HB 2133 is the one to watch right now — it's moving fast. The bill would require notarized model releases for any adult content uploaded online. FSC describes the requirements as "complicated, contradictory" — a common pattern with these laws, where the drafting is deliberately impossible to satisfy rather than merely burdensome.

North Carolina and Alabama passed similar laws last year. As we've discussed in the context of the FTC's action against Aylo, content consent documentation is rapidly becoming a federal and state compliance requirement simultaneously — but the state-level requirements are fragmenting in ways that create direct conflicts.

Here's the operational problem: notarization requirements effectively ban remote content submission. A platform that accepts uploads from creators across the country cannot realistically require every submitter to have a document notarized before upload. That's presumably the point.

What this means operationally:

• Platforms with any Arizona nexus (users, creators, or company presence) need to flag HB 2133 immediately
• If passed, this could require blocking Arizona-based creator uploads entirely, or building a notarization workflow — neither is trivial
• More broadly, your consent documentation system needs to be flexible enough to accommodate state-specific requirements that will increasingly conflict with each other
• 2257 record-keeping obligations require specific documentation already — but state-level notarization mandates layer on top of, not instead of, federal requirements

---

3. VPN Blocking Requirements

States: Michigan (HB 4938), West Virginia (SB 498), Wisconsin (AB 105)

This is the most technically demanding category. Michigan's bill — which would ban VPNs outright — is likely dead according to FSC. But West Virginia and Wisconsin's bills, which would require adult sites to identify and block all VPN traffic, are more viable politically and far more complicated technically.

VPN detection is an arms race. The commercial VPN industry actively works to evade detection. A legal mandate to block VPN traffic creates ongoing liability for platforms that can't achieve 100% detection rates — which is every platform.

The age verification connection is direct: These bills exist because legislators know that VPNs are the primary workaround for age verification laws. If your platform implements age verification to comply with Texas, Louisiana, or any of the 25+ states with active laws, users simply route through a VPN. The legislative response is to make VPN circumvention the platform's problem, not the user's.

What this means operationally:

• Implementing VPN blocking at a technically reliable level requires commercial threat intelligence feeds (MaxMind, IP2Proxy, etc.) integrated into your access control layer
• No technical solution achieves 100% VPN detection; bills that impose liability for any VPN traffic slipping through create an unwinnable compliance posture
• Document your VPN-blocking efforts regardless — demonstrating good-faith technical implementation matters when enforcement is discretionary
• This is an area where your infrastructure choices now will determine your exposure later

---

4. Mandatory Health Warning Labels

States: Wisconsin (AB 961/SB 938), Washington (HB 2112), Missouri (HB 1839), Alabama (existing), Texas (enjoined)

FSC has an ongoing injunction against Texas's warning label law. Alabama's health warning requirement is currently in effect. Now Wisconsin, Washington, and Missouri are introducing similar legislation.

The legal status here is genuinely uncertain. FSC's Texas injunction suggests these laws are vulnerable to First Amendment challenge — but Alabama's law remains in effect while that litigation continues, meaning platforms operating in Alabama need to comply today regardless of what eventually happens in court.

What this means operationally:

• If you have users in Alabama, you likely need to display health warning labels on adult content now
• Track the Texas litigation carefully — FSC's injunction isn't a final ruling, and an adverse outcome would remove the only active precedent blocking these laws
• Warning label implementation is relatively straightforward technically, but requires a geo-detection layer that can conditionally render compliance notices by state — the same infrastructure you'd build for state-level age verification

---

The Bigger Picture: Compliance Fragmentation Is Accelerating

The four legislative categories above share a common structure: they impose state-specific, technically demanding, and sometimes mutually conflicting requirements on platforms that operate nationally or globally.

Consider what full compliance looks like across active 2026 state requirements:

Requirement	States	Technical Complexity	Legal Status
Age verification	25+ states	High	Enforceable post-Paxton
Content-based taxation	Alabama, potentially Utah	Medium	Active
Notarized model releases	NC, Alabama, potentially AZ	High	Active in NC/AL
VPN blocking	WV, WI (proposed)	Very High	Pending
Health warning labels	Alabama (active), TX (enjoined), WI/WA/MO (proposed)	Low-Medium	Mixed

No single compliance framework handles all of these simultaneously. And that's before you layer in federal obligations — REPORT Act CSAM reporting requirements, 2257 record-keeping, and the payment network compliance requirements from Visa's VAMP program and Mastercard's revised MMP standards.

---

Action Items for Platform Operators

1. Audit your state exposure now. Map your users, creators, revenue, and corporate presence by state. Your compliance obligations differ significantly depending on which states you're "in" for jurisdictional purposes.

2. Track Arizona HB 2133 weekly. If it passes, you'll need either a notarization workflow for creator uploads or a geo-block on Arizona creator accounts. Build the infrastructure before you need it.

3. Implement geo-detection infrastructure if you haven't already. Warning labels, age verification, and eventual VPN blocking all require the ability to identify user location and conditionally serve different experiences. This is foundational — build it once, use it for everything.

4. Review your consent documentation system for state-specific extensibility. Federal 2257 requirements are the floor. Alabama and North Carolina have already raised it. Arizona may next. Your system needs to capture additional attestations per-state without requiring a full rebuild each time.

5. Subscribe to FSC's legislative tracker (action.freespeechcoalition.com). They're tracking the bills listed above and more. Legislative monitoring isn't optional compliance work — missing a bill that passes can mean retroactive liability.

6. Document VPN-blocking efforts proactively. Even before WV or WI bills pass, implementing commercial VPN detection demonstrates good faith to payment networks and regulators. Your acquirer is watching your compliance posture regardless of what any specific state law requires.

7. Understand the difference between enjoined and repealed. Alabama's health warning law is active. Texas's is enjoined — which means it could become active if FSC's litigation fails. Don't treat injunctions as permanent relief.

---

What to Watch in the Next 90 Days

We're still early in the 2026 legislative calendar. FSC explicitly notes it expects additional bills to be introduced before sessions close. The most important near-term signals:

• Utah SB 73 — does it pass? If so, content taxation becomes a proven model other states will replicate quickly.
• Arizona HB 2133 — how far does it advance? Notarized consent requirements spreading beyond two states would create a genuine operational crisis for creator platforms.
• West Virginia SB 498 / Wisconsin AB 105 — do these clear committee? VPN blocking mandates would be the most technically disruptive requirement yet imposed on adult platforms.
• FSC's Texas warning label litigation — any movement toward a final ruling (rather than ongoing injunction) would clarify the constitutional landscape for warning label laws nationally.

The compliance picture for adult platform operators in 2026 is more complex than it's ever been — and it's still getting more complicated. Age verification was the wave everyone saw coming. The four fronts above are the ones that will surprise operators who haven't been watching closely.