SynthID stays when the visible mark is off

Do not treat optional chrome as optional provenance. Google’s 14 August 2026 Media watermark setting hides the visible mark on Gemini and Flow. SynthID stays. A detector can still read the file. Cropping the corner does nothing, because the signal was never in the corner.

TechCrunch, 14 August 2026 and Josh Woodward’s same-day post are the source. Fastlane’s 24 August 2026 recap, citing 14 August, is a second dated source. This page is the operational rule for producers: the sparkle is furniture; SynthID is the mark that remains. It is not a walkthrough of how the watermark is embedded.

The toggle only hides the sparkle

Gemini Settings → Media watermark (or “Show watermark”) is a preference for future images, videos, and songs. Woodward named Nano Banana, Omni, and Lyria. Flow inherits the same visible-mark choice. Search was described as coming next. In countries where law requires the visible mark, the toggle does not win.

That is the entire user-facing change. The Gemini app post (14 August 2026) says invisible SynthID watermarks and C2PA metadata “will always stay embedded in the background.” Woodward’s quoted balance: creative control versus safety; visible optional; SynthID and C2PA still used for transparency; you can still use Gemini or Search to see if an image was AI-generated.

If you are turning the setting off so a brand deck looks “native,” say that. Do not say the clip is clean. Do not say the detector will miss it. Do not say a platform cannot auto-label from a surviving cooperative signal. You asked for less chrome. You received less chrome.

Flow is still a launcher for Google’s video family. Optional sparkle does not caption the file, does not pick Seedance 2.0 when Veo is the wrong row, and does not publish. Google Flow is a Veo surface, not a studio remains true with the mark hidden.

SynthID is in the pixels

SynthID is Google DeepMind’s invisible watermark for AI media: a detector-readable signal in the output, not a logo. The glossary definition is the one to keep. It is a watermark, not a manifest. Content Credentials hash exact bytes and break when those bytes change, which is what a platform re-encode does. SynthID is built to sit in the pixels or the samples and still be readable after ordinary social handling.

A few production consequences follow, and they did not start on 14 August:

• Do not crop a corner to remove the AI mark. The sparkle was in the corner. SynthID is not.
• Do not screenshot as a strip. A screenshot may drop C2PA. It does not reliably drop an invisible watermark, and it produces a worse file.
• Do not treat a failed C2PA inspect as “unmarked.” The cooperative metadata can be gone while the robust pixel signal remains. That is a worse position than either extreme: you look unsigned, and a provider detector can still hit.
• A SynthID hit is origin, not compliance. It says this file, or a descendant of it, came through a Google generator that embeds the mark. It does not say who published it, whether a viewer was told, or whether the picture is a deepfake of a real person.

YouTube’s 27 May 2026 labelling post is a useful adjacent fact: labels alone do not impact recommendations or monetization eligibility on that platform, and YouTube can auto-detect if the creator does not disclose. Auto-detection is the class of system SynthID is for. Hiding chrome does not opt you out of that class.

Do not treat optional chrome as optional provenance

Provenance is the recorded origin of a file. Optional chrome is a UI preference.

If a SOW says “no watermarks,” parse it. Most clients mean no vendor wordmark in the frame. That is now sometimes available on Gemini and Flow. If they mean “not detectable as AI,” you cannot sell them a Flow export. If they mean “no C2PA so Meta will not AI-info the ad,” stripping metadata is a different, often unwise, conversation: Meta has also been detecting third-party AI on ads since 1 June 2026 (per Fastlane), and Ads Manager auto-applies AI info for Background Generation, Image Generation, and Add Animation (Coinis, 16 July 2026). Hiding a sparkle does not negotiate those surfaces.

If a legal memo says “provider marking,” point at SynthID and C2PA, not at the Media watermark setting. Article 50 provider duty is machine-readable marking, grace to 2 December 2026 for systems already on the market before 2 August 2026. Google leaving the invisible layers on is how that duty still gets met after the papercut fix.

If a creator asks whether they should generate in Flow because the mark is optional, the answer is: only if they already wanted Flow’s model. The toggle is not a quality upgrade. It is not a rights upgrade. Versely still does not stamp its own visible watermark on catalog outputs; that was already true, and it is not the same as Google skipping SynthID on Veo.

A client who asks you to “run it through Flow with the mark off so we can say it isn’t AI” is asking you to lie about provenance. The setting hides chrome. It does not rewrite origin. Say no, or say exactly what the toggle does: empty corner, SynthID still in the pixels, C2PA still on the export until the next hop.

What you still owe the viewer

A detector is not a viewer. A viewer does not open Gemini and paste your Reel.

For photoreal people, places, or events that would appear authentic, the deployer label at first exposure is still due in the EU. Burn it or speak it. The disclosure template is the copy. Instagram’s 31 August 2026 AI-generated profile badge is for an AI person on the profile, not a substitute for a file-level line. Meta organic AI info is a platform control. Put the words in the picture if mute autoplay is how the clip is seen.

Then finish the file as a file: burned-in captions, safe-area, SKU spelling. Optional Flow chrome does not typeset those. The AI video generator is the generate door when you want Google’s family next to other rows. If the job is keep the model and stop living in the launcher, sign up and leave SynthID where Google put it — in the pixels, with or without a sparkle.

FAQ

Can I inpaint or crop Flow’s corner to remove SynthID?

No. The visible sparkle is what you inpaint. SynthID is not stored there. Google’s 14 August 2026 toggle is the supported way to hide chrome, and even then the invisible mark stays.

If C2PA is stripped on upload, is SynthID gone too?

Not by default. A manifest is metadata bound to bytes. SynthID is a pixel-level signal. Platforms that re-encode often kill the first and leave the second. Plan disclosure as if a detector can still fire.

Does optional chrome change Versely’s Veo row?

No. Veo 3.1 is still the catalog job: native audio, 4K tier, 4 / 6 / 8s, 40 credits. A Gemini setting is not a credit change and not a provenance off switch.