The Online Safety Act age verification requirements are simple to state: if your service makes pornographic content available to UK users, you must use "highly effective" age assurance so that children are not normally able to encounter it. Self-declaration ("I am over 18" buttons), warnings and terms of service do not count. The duty has applied to sites publishing their own pornography since 17 January 2025 and to user-to-user platforms hosting pornography since 25 July 2025, and Ofcom has been fining non-compliant providers since late 2025.
This guide covers who is in scope, the two sets of duties (Part 5 and Part 3), the methods Ofcom accepts, what you must document, and how enforcement works in practice. It is general information, not legal advice; for decisions about your own service, take advice from a UK online safety lawyer.
Who the Online Safety Act age verification rules cover
The Online Safety Act 2023 applies to services with "links with the United Kingdom". Under the Act, a service has UK links if it has a significant number of UK users, or if the UK is one of its target markets. Being based in Cyprus, the Netherlands or the US does not take you out of scope: Ofcom has fined providers incorporated outside the UK.
For age verification, three groups matter:
- Publishers of their own pornography (paysites, studio sites, creator-owned sites, AI image generators that output pornographic material). These fall under Part 5 of the Act.
- User-to-user services that allow pornography (tube sites with user uploads, fan platforms, forums, social networks that permit adult content). These fall under Part 3 and Ofcom's Protection of Children Codes.
- Services that are both. A tube site that uploads its own studio content and also accepts user uploads has duties under both parts. Our guide to Part 5 vs Part 3 duties walks through the distinction.
Text-only content and paid-for advertisements are excluded from the Part 5 definition of "regulated provider pornographic content". Affiliate and review sites that only link out are usually not publishers, but explicit embeds change that (see below).
Part 5: duties for sites that publish pornography
Section 81 of the Act sets out the Part 5 duties. If you publish or display regulated provider pornographic content, you must:
- Use age verification, age estimation or both to ensure children are not normally able to encounter the content.
- Make sure the method is highly effective at correctly determining whether a particular user is a child.
- Keep a written record, in an easily understandable form, of the methods you use and how you apply them, including how you took UK privacy and data protection law into account when choosing them.
- Publish a summary of that record in a publicly available statement, explaining which methods you use and how.
These duties came into force on 17 January 2025, the day after Ofcom published its age assurance guidance. Ofcom wrote to in-scope providers asking them to explain their methods and rollout plans by early March 2025, and opened its first investigations during 2025.
Part 3: duties for user-to-user platforms
Part 3 applies to user-to-user and search services. Pornography is "primary priority content" that is harmful to children, and the children's safety duties in section 12 require platforms that allow it to use highly effective age verification or estimation to prevent children from encountering it.
The timeline for Part 3 ran in stages:
| Date | What applied |
|---|---|
| 16 April 2025 | Deadline for children's access assessments (whether children are likely to access the service) |
| 24 July 2025 | Deadline for children's risk assessments |
| 25 July 2025 | Protection of Children Codes in force: platforms allowing pornography must have highly effective age assurance |
Ofcom's fines against tube-style platforms in 2026 were issued under section 12, which shows the Part 3 route is enforced just as actively as Part 5.
Which age checks Ofcom accepts
Ofcom does not approve individual vendors. It sets four criteria a method must meet (technical accuracy, robustness, reliability and fairness) and lists methods that are capable of being highly effective if implemented well:
| Capable of being highly effective | Not capable of being highly effective |
|---|---|
| Photo-ID matching | Self-declaration of age |
| Facial age estimation | Debit cards or payment methods that do not require the user to be 18 |
| Open banking | Warnings, disclaimers and "18+ only" labels |
| Mobile network operator age checks | General terms of service banning under-18s |
| Credit card checks | |
| Digital identity services | |
| Email-based age estimation |
The method alone is not enough; the implementation matters. Ofcom expects the check to happen before any pornographic content is visible (no explicit thumbnails behind a modal), circumvention to be mitigated, and nothing on the service to direct children to ways around the check, such as content promoting VPNs for that purpose. Our detailed guide to highly effective age assurance methods explains each criterion and the common implementation failures.
Common mistake: putting a compliant age check on the homepage but leaving category pages, embeds or RSS feeds open. Ofcom looks at whether children are "normally able to encounter" content anywhere on the service, not just the front door.
Age checks and data protection
Age assurance involves processing personal data, sometimes biometric data, so UK GDPR applies alongside the Online Safety Act. Ofcom and the ICO have been clear that you must comply with both; one is not a trade-off against the other. In practice that means:
- Choosing a method that collects the minimum data needed to answer "over 18 or not".
- Preferring providers that do not pass identity details back to you, and that delete images and documents promptly.
- Doing a data protection impact assessment before rollout.
- Explaining the check clearly in your privacy notice.
Your Part 5 written record must show how you weighed privacy when choosing a method, so document this as you go.
How Ofcom enforces the age verification rules
Ofcom's toolkit is broad:
- Information notices. Legally binding requests for information. Failing to respond accurately and on time is a separate breach, and Ofcom has added separate fines for it in almost every age-check case so far.
- Investigations and provisional decisions. Providers get a chance to respond and to fix the problem before a final decision.
- Penalties of up to £18 million or 10% of qualifying worldwide revenue, whichever is greater, plus daily penalties for continuing breaches.
- Business disruption measures. Ofcom can apply to court for orders requiring payment providers, advertisers or internet service providers to withdraw services from, or block, a non-compliant site.
Fines so far have ranged from £50,000 for a small nudification site to £1.35 million for a multi-site operator, and at least one provider choosing to block UK users rather than implement checks. Our tracker of Ofcom age verification fines lists each decision and what drove its size.
Where affiliates, hosts and payment providers fit
The duties sit with the provider of the service that makes the content available, but the knock-on effects reach the whole supply chain:
- Affiliates and review sites. If you only link to adult offers and describe them in text, you are unlikely to be publishing regulated provider pornographic content. If you embed explicit previews, trailers or galleries, you may be. Many programs now send UK traffic to an age gate first, so expect conversion rates on UK clicks to change.
- White-label and tube site operators. If you run a white-label cam or VOD front end on your own domain, check your contract: who is the "provider" of that service in Ofcom's eyes, and who implements the check? Get it in writing.
- Hosts and CDNs. They are not usually the provider, but business disruption orders could require third parties to withdraw services from a non-compliant site, so some hosts now ask adult customers about their age assurance.
- Payment providers and advertisers. Ofcom can seek court orders requiring them to stop working with a non-compliant service. Expect more compliance questions during onboarding and reviews.
For UK-focused affiliates, our market guide to the Online Safety Act for affiliate sites covers the practical changes in more detail.
A practical compliance checklist
- Map your service. List every domain, subdomain, app and feed that displays pornographic content, and decide whether each is provider content (Part 5), user-generated (Part 3) or both.
- Choose a method or a mix. Offering two or three options (for example facial age estimation with an ID fallback) reduces drop-off and helps fairness for users the first method struggles with.
- Gate before content. No explicit previews, thumbnails or autoplay before the check is passed.
- Test circumvention. Try the check with photos of photos, masks, borrowed cards and repeated attempts. Ask your vendor for its testing evidence.
- Write the record and the public statement (Part 5), or include age assurance in your children's risk assessment (Part 3).
- Prepare for information notices. Name a senior contact, keep evidence of rollout dates and monitoring, and diarise response deadlines.
- Review at least annually, and whenever your vendor, traffic mix or Ofcom guidance changes.
To compare vendors, start with our compliance and verification services directory, and ask each vendor for independent testing evidence against Ofcom's four criteria.
Frequently asked questions
Does the Online Safety Act apply if my company is outside the UK?
Yes, if your service has a significant number of UK users or targets the UK. Ofcom has investigated and fined providers incorporated outside the UK. If you do not want to comply, the alternative is to genuinely block UK access, which Ofcom will monitor.
Is a credit card check enough?
Credit card checks are on Ofcom's list of methods capable of being highly effective, because UK credit card holders must be 18 or over. Debit cards and other payment methods are not, because children can hold them. How you implement the card check still matters.
Do I need to re-check returning users?
Ofcom's guidance focuses on outcomes: children must not normally be able to encounter the content. A logged-in adult account that was verified properly can usually be relied on, but shared devices and account-sharing are risks you should address in your record or risk assessment.
What about the UK traffic impact?
Expect drop-off at the age gate, especially on free tube traffic. Offering more than one method and keeping the flow short on mobile are the two changes that usually help most.
Next steps
If you publish your own content, start with your Part 5 written record and vendor choice. If you run a platform, check your children's risk assessment covers age assurance properly. Remember that the illegal content duties apply alongside age checks, and browse the rest of our age verification guides for other European countries.