2026-09-16
What the EU AI Act's Article 50 actually requires from a background cutout (in effect since August 2, 2026)
On August 2, 2026, the transparency rules in Article 50 of the EU AI Act became enforceable, and outlets covering it plainly — Euronews' headline is "AI-generated label becomes mandatory in the EU for companies" — are not overstating it. A law firm client alert from Cooley confirms the same date and adds the number that makes it more than a compliance suggestion: breaches can draw fines of up to €15 million or 3% of worldwide annual turnover, whichever is higher. If you edit photos for a living or for a shop, a listing, or a portfolio, that headline raises one specific question that neither Euronews nor most coverage answers directly: does a plain background cutout — no generated scenery, nothing composited in — count as the kind of "AI-generated or manipulated" content this law is actually aimed at?
What actually took effect on August 2, 2026
Article 50 isn't one rule; per the European Commission's own FAQ and the AI Act service desk's article page, it's at least two separate obligations aimed at two different roles. Providers — companies that build or offer an AI system — must make sure synthetic audio, image, video, or text output is "marked in a machine-readable format and detectable as artificially generated or manipulated." Deployers — anyone using an AI system's output under their own authority — have a separate duty: if what they're putting out is a "deepfake," they must disclose that the content has been artificially generated or manipulated, "upon first exposure at the latest," in a way a person can understand without needing special tools. Content published before August 2, 2026 doesn't need retroactive labeling, and providers of generative systems already on the market get until December 2, 2026 specifically for the marking-and-detection half of the obligation.
Two obligations, two different tests
| Provider marking — Art. 50(2) | Deployer disclosure — Art. 50(4) | |
|---|---|---|
| Who it binds | Whoever builds or offers the AI system | Whoever uses the system's output under their own authority, in a professional capacity |
| What's required | Output marked machine-readable & detectable as AI-generated/manipulated | A clear, human-readable statement that the content is artificially generated or manipulated |
| Key exemption | "Assistive editing functions" for standard editing tasks that don't substantially alter the input data or its meaning | Content that doesn't meet the legal deepfake test (below); personal, non-professional use isn't "deploying" at all |
| Penalty ceiling | Up to €15 million or 3% of worldwide annual turnover, whichever is higher | |
The legal definition of "deepfake" — and what it excludes
The word "deepfake" isn't used loosely in the regulation. Per Article 3(60)'s definition, it means "AI-generated or manipulated image, audio or video content that resembles existing persons, objects, places, entities or events and would falsely appear authentic or truthful." Both halves of that sentence have to be true at once: the content has to resemble something real, and it has to be the kind of thing a viewer could mistake for genuine. The Commission's own FAQ gives a concrete negative example that's useful precisely because it isn't about photorealism at all — "background scenes, special effects, or technical pre- and post-processing as part of standard movie production processes" fall outside the deepfake test, because an audience watching a film already expects staged content and isn't being deceived about what's real. The same source notes that "clearly fantastical or physically impossible content" (dragons, people flying) is excluded for the same underlying reason: it cannot falsely appear authentic, because no reasonable viewer would take it as a genuine depiction of something that happened.
Where a plain cutout sits — reasoned, not officially confirmed
Neither Commission source we found addresses background removal by name, so what follows is reasoning applied to the text and the FAQ's own examples, not a quoted Commission statement about cutout tools specifically. A background-removal step that isolates a real, unaltered subject and produces a transparent PNG — adding no scenery, fabricating no location, changing nothing about what the subject itself looks like — doesn't make anything "falsely appear authentic," because there's no fabricated scene being passed off as real in the first place; the subject is exactly the real subject, just without its original background. That reading lines up with the wording of the Article 50(2) marking exemption for "assistive editing functions" that don't "substantially alter the input data or its meaning": isolating a subject changes what's around it, not who or what it is. Where the picture changes is the moment a fabricated scene gets added back in and presented as if it were the real setting.
Where it stops being "just a cutout"
The line above is about isolation, not about anything downstream of it. Take the exact same transparent cutout and composite it into a fabricated room, a fabricated location, or a fabricated studio backdrop, then present the result as if it were an authentic, unaltered photo of that scene, and the analysis changes — that composited image does resemble a place, and it is being presented as if it were real. This is precisely the pattern this blog's own post on New York's and California's real estate photo rules already covers at the industry level: virtual staging, digitally "fixed" views, and added landscaping are legal, but New York's trend alert and California's AB 723 both require disclosing that the image was altered. The EU AI Act's Article 50(4) runs on a related but separate logic — it isn't limited to real estate, and it isn't about whether a state real-estate regulator considers the depiction misleading, it's about whether the result would falsely appear authentic to a viewer under the AI Act's own deepfake definition. Either way, the trigger is the fabricated scene being passed off as genuine, not the subject having been cut out of its original photo in the first place.
Who this actually reaches
One more piece of the text narrows this further than the headlines suggest. Article 3(4)'s definition of "deployer" explicitly excludes "use in the course of a personal non-professional activity" — a person editing their own vacation photo, a dating-profile picture, or a family portrait for a holiday card isn't "deploying" an AI system under the Act at all, no matter what tool they used or what they did with the cutout afterward. The obligation is aimed at businesses, agencies, and other organizations acting under their own authority: a marketplace seller, a real estate brokerage, a publisher, a marketing agency, or any other professional user putting AI-edited images in front of the public. If you're isolating a subject from a photo for personal use, Article 50 as described here doesn't reach you as a deployer in the first place; if you're doing it professionally and then compositing the result into a fabricated scene presented as real, the disclosure question above is worth taking seriously.
What NearBG does and doesn't do here
- No compositing, no generated background. NearBG's output is a transparent PNG of the isolated subject. It doesn't add a background, a scene, or any fabricated content — that step, if someone wants it, happens in a separate tool, and this post's analysis of Article 50(4) applies to whatever that separate tool produces, not to NearBG's own output.
- No legal or compliance determination. NearBG doesn't label, certify, or flag anything as "AI Act compliant." Whether a specific downstream use counts as deploying a deepfake is a judgment call for the professional using the image, made against the Article 3(60) test above and, ideally, their own counsel.
- On-device only, same as every other post on this blog. The removal itself runs entirely in the browser, with no upload and no account, using the same U2Netp segmentation pipeline this blog's first post documents.
- One photo at a time, no batch. A catalog or portfolio of images means running the tool once per photo.
Honest summary
Article 50's August 2, 2026 effective date, its €15 million-or-3%-of-turnover penalty ceiling, the text of the provider marking duty and its "assistive editing" exemption, the deployer deepfake-disclosure duty, the Article 3(60) deepfake definition and its "clearly fantastical" and "standard movie production" exclusions, and Article 3(4)'s personal-use exclusion from "deployer" are all quoted or closely paraphrased from the European Commission's own FAQ and service-desk pages, from Cooley's client alert, and from artificialintelligenceact.eu's article-by-article text. None of it is legal advice, and no Commission source we found addresses background-removal tools by name — the conclusion that a plain, non-composited cutout sits outside the deepfake test is this post's own reasoning applied to that text, not a quoted official statement about cutout tools specifically, and it's flagged that way rather than stated as settled law. What doesn't change under any reading: the moment a fabricated scene gets composited in and presented as real, a separate, well-documented disclosure question opens up — and that step happens after NearBG, not inside it.