KIDS Act & SCREEN Act: Age Verification, OnlyFans 2026

TL;DR. Two different federal bills are in play, and keeping them straight matters. The SCREEN Act is the one that actually mandates adult-site age verification: it would require platforms serving content harmful to minors to run real verification instead of a "click here if you're 18" button, hand enforcement to the Federal Trade Commission, and check IP addresses including known VPN and proxy ranges. The KIDS Act (Kids Internet and Digital Safety Act, H.R. 7757) is a separate, much broader kids-safety omnibus built around a revised Kids Online Safety Act and COPPA 2.0. On June 29, 2026 the U.S. House passed the KIDS Act by a vote of 267 to 117, and the SCREEN Act's age-verification language rode along as a title inside that package. Both are now in the Senate, where the path is far less certain, especially after Senate sponsors called the House version of the kids-safety piece "dead" for dropping the original duty-of-care standard. For an OnlyFans agency, the near-term change is nothing: this is a bill in progress, not law, and the platforms you build funnels on already verify age. The strategic question is what happens if a national age-verification standard lands on top of the roughly 26 states that already require age checks, and whether that ends geo-blocking as a traffic-routing tactic. This is educational, not legal advice.

The reason this belongs on your radar is not that it changes your obligations tomorrow. It does not. It is that federal age-verification language, for the first time in years, has cleared a full chamber of Congress inside a broad child-safety package with genuine momentum. Whether it becomes law or dies in the Senate, the agencies that read the trajectory correctly avoid two mistakes: panicking over a bill that has not passed, and being caught flat-footed if it does. This post separates the two bills, breaks down where each stands, how a federal mandate would differ from the current state patchwork, why national preemption is the variable that matters most for your funnels, and how to brief your creators without overreacting.

Two bills, not one: how the SCREEN Act and the KIDS Act fit together

The first thing to get right is that these are two distinct pieces of legislation, and only one of them is the adult-site age-verification bill.

The SCREEN Act is the age-verification bill. Its full name is the Shielding Children's Retinas from Egregious Exposure on the Net Act. It exists in two standalone versions that have sat in committee for over a year: S.737, introduced in the Senate by Senator Mike Lee in February 2025, and its House companion H.R. 1623, led by Representative Mary Miller. Neither standalone version has passed on its own. What actually moved in June 2026 is that the SCREEN Act's text was folded in as a title inside the larger KIDS Act package, which is how its age-verification language reached a House floor vote for the first time.

The KIDS Act is the broader omnibus. House Energy and Commerce Chairman Brett Guthrie introduced H.R. 7757 in March 2026 as a consolidation of roughly fourteen previously separate proposals: a revised Kids Online Safety Act, COPPA 2.0, the SAFE Bots Act aimed at chatbot features for minors, the SPY Kids Act, the Safer GAMING Act, education and research measures, and, as one title among many, the SCREEN Act. The important nuance is that the core of the KIDS Act, the KOSA and COPPA 2.0 machinery, is about platform design duties and children's data, not adult-site age gates. Analysts reviewing the text note that this core does not itself impose the hard adult-content verification mandate. That mandate comes specifically from the SCREEN Act title. So when you hear "the KIDS Act passed the House," the part that matters to the adult-content economy is the SCREEN Act riding inside it, not the omnibus as a whole. Packaging them together is a legislative strategy: it lets a chamber pass a lot of child-safety policy in one vote and makes each piece harder to strip out.

Because the SCREEN Act is the operative age-verification bill, focus on what it does. It does four things that matter to you. It requires online services that distribute content harmful to minors to deploy "technology verification measures" confirming a user is not a minor before serving that content. It outlaws self-attestation, the decades-old "I am 18 or older, enter" button, as a compliant method. It puts enforcement with the Federal Trade Commission, which would treat violations as unfair or deceptive practices. And it reaches into routing: services would have to subject users' IP addresses, including known VPN and proxy ranges, to verification, unless the service determines the user is outside the United States.

Read those four features together and you can see why this differs from the state laws already on the books. A state statute binds platforms doing business with that state's residents. A federal standard, enforced by a single national regulator, would apply the same rule everywhere at once, and the explicit VPN language targets the workaround people use to dodge state-level checks. None of this touches your agency directly, because you do not host adult content or run the verification gate. But it reshapes the platforms and traffic paths your funnel depends on, which is why it is worth understanding at altitude rather than ignoring until it is law.

Where the bill stands in Congress right now

Be precise about the status, because the whole strategic posture depends on it. As of July 2026, the KIDS Act package, with the SCREEN Act folded into it, has passed the House of Representatives and nothing more. The House vote came on June 29, 2026, 267 to 117, taken under suspension of the rules, which requires a two-thirds majority and signals broad bipartisan support in that chamber. The package then moved to the Senate. The two standalone SCREEN Act bills, S.737 in the Senate and H.R. 1623 in the House, remain parked in committee and have never had their own floor vote, which is exactly why the omnibus route was the one that finally advanced the age-verification language.

The Senate is where these bills historically go to stall, and this time there is a specific fault line. The House stripped out the Kids Online Safety Act's original "duty of care," the enforceable obligation for platforms to act in minors' interest, and replaced it with a lighter standard. Senate sponsors of KOSA reacted sharply, with one calling the House bill "dead" in the Senate precisely because it gutted that provision. That fight is about the omnibus core, not the SCREEN Act title, but it threatens the whole vehicle: if the Senate cannot reconcile the duty-of-care dispute, the age-verification language riding inside the package stalls with it. Add to that the general track record. Child online-safety legislation has repeatedly cleared committees or one chamber in recent Congresses and then failed to reach the finish line, often over privacy and free-speech objections from digital-rights groups and a subset of senators. Public appetite is real: polling in early 2026 showed strong majority support for a federal age-verification requirement. But support in the abstract is not the same as sixty votes for a specific bill.

So the honest read is this. A federal age-verification mandate is closer than it has been in years, having ridden a full chamber inside a popular package. It is also not law, has no guaranteed Senate path, and could easily die or be rewritten before anyone signs anything, and the fight over the omnibus core could take the age-verification title down with it. Treat it as what it is: a live bill in progress, not settled policy. Your job now is to understand the scenarios, not to rebuild your operation around one that has not arrived.

How a federal mandate differs from the state-by-state patchwork

To see what a national standard would change, you have to understand what you are living with today. Since the Supreme Court's June 2025 decision in Free Speech Coalition v. Paxton upheld Texas HB 1181 and removed the main First Amendment obstacle, states have moved fast. By mid-2026 roughly 26 states had age-verification laws for adult content in effect, with West Virginia's taking hold in June 2026. That is not a coherent framework. It is a patchwork, and the patchwork itself is the problem.

Every one of those state laws has its own definition of covered content, its own accepted verification methods, its own thresholds, and its own enforcement mechanism, from state attorneys general to private lawsuits. Platforms serving a national audience have to reconcile all of them at once, and the result has been visible for a while: some large adult sites simply block entire states rather than build a compliant gate for each, and users there either lose access or reach for a VPN. We track the moving pieces in our US state age-verification rollout schedule, and the through-line is that the map keeps changing state by state, quarter by quarter.

A federal mandate would, in theory, collapse that complexity into one rule. One definition of what must be gated, one regulator, one accepted-methods standard, one enforcement regime. That is genuinely simpler for the platforms, and simpler for the platforms tends to mean fewer sudden state-level blackouts that disrupt your traffic. But there is a critical catch you have to confront directly: as currently drafted, the SCREEN Act is not written as a preemption of state law. Analysts reading the text describe it as setting a national floor rather than sweeping the states aside, which means platforms could end up complying with both the federal standard and the stricter state statutes simultaneously. A single national framework only truly simplifies things if Congress writes explicit preemption into it, and that is exactly the provision that would be fought over hardest. For the broader legal grounding on where these laws already touch your operation, our overview of age-verification laws and OnlyFans agencies is the companion piece to this one.

Why national preemption would end geo-blocking as a compliance play

Here is the strategic hinge, and it is worth slowing down on. The single most consequential question in this whole debate, from a traffic-operator's point of view, is not whether age verification is required. It is whether a federal law preempts the states or merely stacks on top of them.

Under the current patchwork, geo-blocking is a live tactic. When a state's law takes effect, a platform can choose to block that state rather than verify, and the market has adapted around that choice. Traffic reroutes, users in blocked states find other paths, and the friction is regional and uneven. Some of your funnel math implicitly assumes this: certain states go dark, certain traffic sources shift, and you plan around a map with holes in it. We have written about the downstream effect of that on discovery and conversion in our piece on age-verification traffic collapse and funnel rebuild, because geo-blocking is not a hypothetical, it is already reshaping where subs come from.

A truly preemptive federal standard would take geo-blocking off the table. If the rule is national and uniform, there is no "just block the state with the aggressive law" option, because the aggressive law is the same everywhere. The upside is stability: no more sudden state-by-state blackouts scrambling your traffic mix. The downside is universality: the friction of a hard age gate would apply to every U.S. visitor, not just those in the strictest states, raising the verification barrier across your entire domestic funnel at once.

But, and this is the part you cannot skip, the SCREEN Act as it currently reads does not deliver that clean preemption. It layers a federal floor on top of the states. So the geo-blocking-ends scenario is the one to plan for, not the one that is guaranteed. If Congress adds preemption during Senate negotiation, the map goes uniform and geo-blocking dies. If it does not, platforms carry federal and state obligations at once, and geo-blocking survives in the states that go beyond the federal floor. Watching which way that drafting choice breaks is the highest-value thing you can do with this bill.

What a single national verification framework would require operationally

Play out the scenario where a national framework does arrive, whether preemptive or as a floor. What actually changes at the operational level for an agency? Less than a panicked reading suggests, and more than a dismissive one does.

Start with what does not change. You are not the regulated party. The SCREEN Act, like the state laws, targets the services that host and profit from adult content, meaning OnlyFans, Fansly, and the platforms in that tier. Those platforms already verify creators with government ID and run their own age gates. A federal mandate raises the bar on how they verify fans at the point of access, but the compliance engineering sits with them. You do not build the gate, store anyone's ID, or become an FTC-enforced entity by running marketing direction. That distinction is not a technicality, it is the whole shape of your risk exposure.

What would change is the friction profile of your funnel. If self-attestation is banned nationally and replaced by real verification, everything upstream of the paywall gets more sensitive to drop-off. Age-estimation scans, ID checks, or third-party verification wallets all add a step between "clicked your link" and "subscribed," and every added step costs conversion. That reprices the value of warm, high-intent traffic and penalizes spray-and-pray volume. The winners in a hard-verification world are the funnels that send fewer, better-qualified fans who are already committed enough to clear a friction gate. This is where marketing direction actually earns its keep, and it is why the EU's parallel move toward verification wallets is worth studying now: our breakdown of EU age-verification mini-wallets and OnlyFans funnels is a preview of the mechanics a U.S. standard would import.

The second shift is intelligence. Under a national framework, the compliance question stops being "which states are blocked this quarter" and becomes "what does the federal standard accept, and how are platforms implementing it." Simpler to monitor, but more consequential, because when it changes it changes everywhere at once. Your job is to keep the map current and adjust traffic strategy, not to build verification infrastructure you will never own.

Scenario planning: what to prepare now versus wait on

The discipline here is separating what is worth doing today, regardless of how the bill breaks, from what you should explicitly wait on. Spending money and attention preparing for a specific legislative outcome that has not happened is how agencies burn resources on ghosts.

Do these now, because they pay off under every scenario:

• Diversify traffic sources. An agency whose entire funnel depends on one platform's age-gate friction is fragile whether the friction comes from a state or from Washington. Broaden across enough surfaces that no single verification rule can hollow out your top of funnel. This is good practice with or without the SCREEN Act.

• Bias toward qualified traffic. Every path this bill could take raises verification friction somewhere. Funnels built on high-intent, well-warmed fans absorb friction better than volume plays. Tightening qualification now is a no-regret move.

• Keep a compliance map current. Track the state rollout and the federal bill's status in one place, reviewed monthly. You are not implementing anything, you are staying oriented so you are never surprised.

• Confirm your own legal footing. A federal spotlight on the adult ecosystem raises scrutiny on everyone adjacent to it. If you have not recently checked whether your structure is clean, whether running an OnlyFans agency is legal in 2026 is the right starting point, followed by a conversation with qualified counsel.

Explicitly wait on these, because acting early is waste:

• Do not rebuild funnels around a national verification flow that does not exist. The bill has passed one chamber. Reengineering your entire acquisition path for a standard that could be rewritten or killed in the Senate is premature.

• Do not assume geo-blocking ends. As drafted, the SCREEN Act is a floor, not a preemption. Do not tear up your state-by-state planning on the assumption of a uniform national map until preemption is actually in the enacted text.

• Do not build or buy verification tooling. You are not the regulated party. The verification burden sits with the platforms. Any vendor selling you an age-verification product for your agency is selling you a solution to a problem you do not have.

The posture that wins is watchful, not reactive. Stay oriented, keep the durable habits sharp, and let the platforms carry the compliance engineering that is theirs to carry.

How to brief creators without overreacting to a bill in progress

Your creators will hear about this, and they will hear it in the worst possible frame, because headlines about "age verification" and "adult content bans" travel fast and lose nuance instantly. A creator who reads that Congress just passed an age-verification law can easily conclude her income is about to be gated out of existence. Your role is to be the calm, accurate voice that replaces alarm with an accurate picture.

Lead with the status, not the drama. Tell her plainly: a bill has passed the House, it is now in the Senate where similar bills have stalled for years, and it is not law. The platform she works on already verifies age today, so nothing about her account or her earnings changes right now. That single accurate framing defuses most of the panic, because the panic is built on the false premise that something already happened.

Then explain what would actually change if it passed, in her terms. The verification step would sit at the fan's point of access, on the platform, not on her. It could make casual, low-intent traffic harder to convert, which is a reason to lean into loyal, high-value fans rather than chasing volume, exactly the direction good marketing pushes anyway. Frame it as a shift in funnel quality, not an existential threat, because that is what it is.

Finally, model the posture you want her to hold: informed, unpanicked, and prepared. Tell her you are tracking the bill, that you will flag any real change the moment it happens, and that the plan does not change based on a vote in one chamber. A creator who trusts that her agency is watching the landscape so she does not have to is a creator who stays. Overreacting to a bill in progress does the opposite: it signals that you do not understand the process well enough to tell a passed-the-House headline from an enacted law, and that erodes exactly the confidence you are trying to build. This is also part of the wider information hygiene of operating in a heavily regulated space, which we cover alongside content-integrity rules in our look at the Take It Down Act and creator content.

Frequently asked questions

Did the KIDS Act or SCREEN Act become law in 2026?

No. As of July 2026 the KIDS Act (H.R. 7757), the broad kids-safety omnibus that carries the SCREEN Act as one of its titles, passed the House of Representatives on June 29, 2026 by a vote of 267 to 117, and then moved to the Senate. It has not been enacted. The standalone SCREEN Act bills, S.737 in the Senate and H.R. 1623 in the House, have sat in committee since early 2025 without their own floor vote. Treat all of it as a live bill in progress, not settled law.

What is the difference between the KIDS Act and the SCREEN Act?

They are two different bills. The SCREEN Act is the one that mandates adult-site age verification: real verification instead of a self-attestation button, FTC enforcement, and IP and VPN-range checks. The KIDS Act (H.R. 7757) is a much broader kids-safety omnibus built around a revised Kids Online Safety Act and COPPA 2.0, aimed at platform design duties and children's data rather than adult content. The two connect because the SCREEN Act's text was folded into the KIDS Act as one title, which is how it reached a House vote. When coverage says "the KIDS Act," the part relevant to the adult-content economy is the SCREEN Act inside it, not the omnibus as a whole.

What would the SCREEN Act actually require of adult platforms?

It would require services that distribute content harmful to minors to use "technology verification measures" to confirm a user is not a minor before serving that content, and it would ban the old "click here if you're 18" self-attestation as non-compliant. Enforcement would sit with the Federal Trade Commission. Notably, platforms would have to apply verification to IP addresses including known VPN and proxy ranges, unless the user is determined to be outside the United States.

Does a federal age-verification law replace the state laws?

Not as currently drafted. Analysts reading the SCREEN Act describe it as setting a national floor rather than preempting state statutes, which means platforms could face both the federal standard and stricter state laws at the same time. Whether Congress adds explicit preemption during Senate negotiation is the single most important variable, because true preemption is what would end state-by-state geo-blocking. For the current state picture, see our US state age-verification rollout schedule.

Does any of this make my OnlyFans agency the regulated party?

No. The SCREEN Act, like the state laws, targets the platforms that host and profit from adult content, meaning the services that run the age gate and store verification data. As a marketing partner you do not host content, build the verification gate, or store anyone's ID, so you do not become an FTC-enforced entity by running funnels and content direction. Your exposure is indirect: it flows through how the rules change the platforms and traffic paths your funnels depend on, not through direct regulation of your agency.

How does federal age verification affect my funnels?

Indirectly but meaningfully. If real verification replaces self-attestation, every step between clicking a link and subscribing becomes more sensitive to drop-off, which penalizes low-intent volume traffic and rewards warm, qualified fans who will clear a friction gate. The strategic response is to diversify traffic sources and bias toward high-intent audiences now, since those moves pay off under every version of this bill. Our breakdown of age-verification traffic collapse and funnel rebuild covers the mechanics.

What should I do right now while the bill is in the Senate?

Stay oriented, not reactive. Keep a compliance map current, diversify your traffic so no single verification rule can hollow out your funnel, and tighten toward qualified traffic that absorbs friction. Do not rebuild your funnels around a national standard that does not exist yet, do not assume geo-blocking is ending, and do not buy verification tooling you will never be the regulated party for. If you want a marketing partner tracking this landscape so you do not have to, WhaleFinders works white-label inside OnlyFans agencies and you can reach us on Telegram at t.me/whalefindersupport. This is general education, not legal advice, so confirm anything specific with qualified counsel.