A Feature Request Granted Two Weeks After a Deadline
Google's Gemini team turned a user-experience complaint into a settled feature almost overnight. Gemini VP Josh Woodward had asked his followers on X for their biggest frustrations with the product; removing the visible corner watermark on Nano Banana images, Omni-generated video and Lyria music tracks came back as one of the top ten answers. On August 14, 2026, Woodward announced that Gemini and Google's Flow video editor will ship a Settings > Media Watermark toggle within days, letting a user turn the visible mark on or off for every future generation. Search support is described as coming later.
The timing is what turns a minor UX fix into a policy story. Twelve days earlier, the enforcement machinery behind the EU AI Act's transparency rules had switched on for the first time, with the European Commission's AI Office newly empowered to investigate and fine the exact category of company Google is.
What Article 50 Actually Asks For
The EU AI Act's Article 50 transparency obligations became enforceable on August 2, 2026, according to the European Commission's AI Office, which can now request technical documentation from general-purpose AI providers, evaluate their models, demand risk mitigation, and issue fines of up to EUR 15 million or 3 percent of global annual turnover, whichever is higher. The rule's core demand is that AI-generated or manipulated image, video, audio and text content be marked in a way that is machine-readable and detectable as artificial, and that deepfakes in particular carry a clear label.
Nothing in the AI Office's own published materials specifies that the mark has to be visible to a human. That silence is the gap Google's product decision now sits inside.
The Bet Behind the Toggle
Google's position, stated plainly by Woodward, is that SynthID's invisible digital watermark and the C2PA content-credential metadata travel with a file regardless of what the visible-watermark setting is doing. Both are machine-readable in the literal sense: a detector tool or a C2PA-aware application can read them even though a person looking at the picture cannot see anything. That is a defensible reading of Article 50's text. It is also a different product than what most people who followed the AI Act's public rollout were told to expect, which was closer to a visible label they could rely on with their own eyes.
The practical effect is to move the burden of detecting AI content from the viewer to whichever software the viewer happens to be using - and most consumer apps, social feeds and messaging clients do not run a SynthID detector or read C2PA fields today.
What an EU Business Publishing AI Media Should Check This Week
Any EU organization that uses Gemini, Nano Banana or Flow output in marketing, product photography or social content now has a decision to make once the toggle reaches its account, and a second, less obvious one to verify: whether its own publishing pipeline preserves C2PA metadata at all. Many content management systems, social schedulers and image compressors strip embedded metadata on upload as a routine optimization step - which means that once the visible watermark is switched off, an image can leave a company's own systems carrying no detectable AI-origin signal whatsoever, invisible watermark included, even though Google's file did carry one when it left Gemini.
Read next: Google Marked Every Image and Pulled It in a Day | Google Assistant Shuts Down September 4 for Gemini



