Build This Now
Build This Now
What Is Claude Code?Claude Code InstallationClaude Code Native InstallerYour First Claude Code Project
speedy_devvkoen_salo
Blog/Handbook/Core/The EU AI Act, Explained: What Changes on August 2, 2026

The EU AI Act, Explained: What Changes on August 2, 2026

On August 2, 2026, the EU AI Act's transparency rules kick in — you must be told when you're talking to AI, and AI content must be labeled. Here's what the Act actually requires, what got delayed, and who it affects.

Stop configuring. Start building.

SaaS builder templates with AI orchestration.

Published Jun 13, 20268 min readHandbook hubCore index

The EU AI Act is the world's first comprehensive AI law, and its headline 2026 milestone is August 2, 2026, when the transparency rules start to apply: people must be told when they're interacting with an AI, and AI-generated content like deepfakes must be labeled. It sorts AI systems into risk tiers and regulates them accordingly — banning a few uses outright, tightly controlling "high-risk" ones, and requiring disclosure for the rest. One catch that made 2026 news: the strictest high-risk obligations were pushed back to 2027–2028 by a May 2026 amendment, so August is mostly about transparency, not the full rulebook.

If you build or use AI and touch European users, this affects you — even from outside the EU. Here's the plain-English version.

Table of Contents

  1. The Big Idea: Regulate by Risk
  2. The Four Risk Tiers
  3. What Actually Happens August 2, 2026
  4. What Got Delayed (the Digital Omnibus)
  5. Does It Affect You?
  6. Frequently Asked Questions

Stop configuring. Start building.

SaaS builder templates with AI orchestration.

The Big Idea: Regulate by Risk

The Act's core move is simple: it doesn't regulate "AI" as one thing. It regulates AI by how risky the use is. An AI that recommends songs is treated completely differently from an AI that screens job applicants or controls medical equipment. The riskier the application, the more rules apply. This is why the same law can leave a chatbot mostly alone while heavily governing an AI used in hiring.

The Four Risk Tiers

TierWhat it coversWhat the Act does
UnacceptableSocial scoring, manipulative AI, most real-time public face-scanningBanned outright
High-riskAI in hiring, credit, education, medical devices, critical infrastructureStrict requirements: risk management, documentation, human oversight, transparency
Limited riskChatbots, deepfakes, AI-generated contentTransparency duties — disclose it's AI / label the content
Minimal riskSpam filters, AI in video games, most everyday toolsEssentially unregulated

Most consumer AI lands in "limited risk," which is exactly the tier the August 2026 deadline targets.

What Actually Happens August 2, 2026

From 2 August 2026, the Article 50 transparency obligations apply. In plain terms:

  • You must be told you're talking to an AI. A chatbot or voice agent has to make clear it isn't human (unless that's obvious).
  • AI-generated content must be labeled. Deepfakes and synthetic media must be disclosed as artificially generated.
  • Machine-readable markers must be embedded in AI-generated content so systems (not just humans) can detect it — the watermarking requirement, with a short grace period (until 2 December 2026) for content from systems already on the market.

The goal is straightforward: reduce deception. You should know when a face, voice, or message is synthetic. (This connects directly to why AI voice scams and AI video became 2026 flashpoints.)

Source: European Commission — Navigating the AI Act, Latham & Watkins on the 2026 amendments.

What Got Delayed (the Digital Omnibus)

In May 2026, EU lawmakers agreed to a "Digital Omnibus" amendment that postponed the toughest high-risk deadlines, citing the need for more time and clearer standards:

  • High-risk obligations for standalone (Annex III) systems → deferred to 2 December 2027.
  • High-risk AI embedded in regulated products (Annex I) → deferred to 2 August 2028.

So August 2026 is real but narrower than originally planned: it's the transparency layer, not the heavy compliance machinery for high-risk systems. Don't let "the AI Act takes effect in August" mislead you into thinking everything applies at once — it's phased.

Does It Affect You?

Probably yes if you touch EU users — and here's the part non-EU builders miss: like the GDPR before it, the AI Act applies based on where your users are, not where you are. If your AI product is used by people in the EU, you're in scope.

Practically, for most builders the near-term to-do is the transparency tier:

  • If you ship a chatbot or AI assistant, disclose that it's AI.
  • If you generate images, audio, or video, label it as AI-generated and support machine-readable markers.
  • If you operate in a high-risk domain (hiring, credit, health), start preparing now for the 2027–2028 obligations — they're stricter and take time.

The reassuring news for most apps: if you're honest that AI is AI, the August 2026 bar is very reachable.

Stop configuring. Start building.

SaaS builder templates with AI orchestration.

Frequently Asked Questions

What is the EU AI Act in simple terms?

It's the first comprehensive law governing artificial intelligence. It sorts AI uses into risk tiers — banning the most dangerous, tightly regulating "high-risk" uses like hiring and credit, and requiring transparency (disclosure and labeling) for things like chatbots and deepfakes.

What changes on August 2, 2026?

The transparency obligations begin. People must be told when they're interacting with AI, AI-generated content like deepfakes must be labeled, and machine-readable markers must be embedded in synthetic content (with a short grace period for pre-existing systems).

Did the EU delay the AI Act?

It delayed the strictest parts. A May 2026 "Digital Omnibus" amendment pushed high-risk system obligations back to December 2027 (standalone systems) and August 2028 (AI embedded in regulated products). The August 2026 transparency rules still apply on schedule.

Does the EU AI Act apply to companies outside the EU?

Yes, if your AI is used by people in the EU. Like the GDPR, it's based on where your users are, not where your company is headquartered. Non-EU startups serving European users are in scope.

What do I need to do to comply with the August 2026 deadline?

For most apps, it's about transparency: clearly disclose when users are interacting with AI, label AI-generated images/audio/video, and support machine-readable AI markers. If you operate in a high-risk area like hiring or credit, begin preparing for the stricter 2027–2028 requirements now.

Continue in Core

  • 1M Context Window in Claude Code
    Anthropic flipped the 1M token context window on for Opus 4.6 and Sonnet 4.6 in Claude Code. No beta header, no surcharge, flat pricing, and fewer compactions.
  • AGENTS.md vs CLAUDE.md Explained
    Two context files, one codebase. How AGENTS.md and CLAUDE.md differ, what each one does, and how to use both without duplicating anything.
  • Why a Hidden Line of Text Can Hijack Your AI Browser
    AI browsers read the whole web page — including text hidden from you. That's the door behind prompt injection, OWASP's #1 AI security risk in 2026. Here's how the attack works, in plain English.
  • AI Research for Builders: The Latest Breakthroughs, Explained Monthly
    A monthly digest of the latest AI research — agents, reasoning, efficiency, and models — with every claim traced to its source and translated into what it means if you build with AI.
  • 10 AI Research Breakthroughs That Matter for Builders (June 2026)
    The latest AI research, explained: AI disproved an 80-year-old math conjecture, agents got cheaper and more reliable, and inference costs dropped up to 100x. What each finding means if you build with AI.
  • Did Anthropic Call for an AI Pause? What It Actually Said
    Anthropic did not call to halt the AI boom. Here is what its June 2026 'recursive self-improvement' post actually said, why the 80%-of-its-own-code stat spooked it, and what it means if you build with Claude Code.

More from Handbook

  • Agent Fundamentals
    Five ways to build specialist agents in Claude Code: Task sub-agents, .claude/agents YAML, custom slash commands, CLAUDE.md personas, and perspective prompts.
  • Agent Harness Engineering
    The harness is every layer around your AI agent except the model itself. Learn the five control levers, the constraint paradox, and why harness design determines agent performance more than the model does.
  • Agent Patterns
    Orchestrator, fan-out, validation chain, specialist routing, progressive refinement, and watchdog. Six orchestration shapes to wire Claude Code sub-agents with.
  • Agent Teams Best Practices
    Battle-tested patterns for Claude Code Agent Teams. Context-rich spawn prompts, right-sized tasks, file ownership, delegate mode, and v2.1.33-v2.1.45 fixes.

Stop configuring. Start building.

SaaS builder templates with AI orchestration.

On this page

Table of Contents
The Big Idea: Regulate by Risk
The Four Risk Tiers
What Actually Happens August 2, 2026
What Got Delayed (the Digital Omnibus)
Does It Affect You?
Frequently Asked Questions
What is the EU AI Act in simple terms?
What changes on August 2, 2026?
Did the EU delay the AI Act?
Does the EU AI Act apply to companies outside the EU?
What do I need to do to comply with the August 2026 deadline?

Stop configuring. Start building.

SaaS builder templates with AI orchestration.