Flow’s visible watermark is now optional
On 14 Aug 2026 Google made Gemini and Flow’s visible watermark optional. SynthID and C2PA stay. Versely credits are unchanged.
On 14 August 2026 Google made the visible watermark optional on the Gemini app and on Flow. Invisible SynthID and C2PA stay embedded. Turning the sparkle off is not an unmarked file. Versely credit prices did not move because a Google toggle moved.
TechCrunch, 14 August 2026 is the dated product note. Fastlane’s 24 August 2026 recap citing that 14 August change is a second dated source. Josh Woodward, VP for Gemini, said the visible mark is now a setting in Gemini and Flow, with Search described as coming next, and that SynthID plus C2PA remain. This page is the toggle. It is not a SynthID architecture explainer, and it is not a claim that Flow became a studio.
What Google toggled on 14 August 2026
The control is Settings → Media watermark (Gemini’s copy also says “Show watermark”). It covers visible marks on images, videos, and songs from the Gemini stack Woodward named: Nano Banana (images), Omni (video), Lyria (music). Flow gets the same visible-mark choice because Flow is Google’s video editor surface for that stack.
The Gemini app account (@GeminiApp, 14 August 2026) is the one-sentence version: you can decide whether creations have visible watermarks; invisible SynthID and C2PA metadata “will always stay embedded in the background.” Woodward’s own post called it a papercut fix, with an exception: countries where law requires the visible mark to stay. Engadget’s 14 August recap names the EU’s authentic-looking deepfake rules as the kind of regime that can keep chrome on.
What the toggle is: optional chrome. A corner sparkle, a persistent overlay on video, a player badge on a track. What it is not: a provenance off switch. Google did not announce a way to disable SynthID. Google did not announce a way to strip C2PA from the generator’s export. Credentio, the C library Google said it was open-sourcing the same week, is for checking Content Credentials locally, not for deleting them.
If you generate in Flow and turn the visible mark off, the download can look clean to a client. The file is still a Google generation for anyone running a detector, and the bytes may still carry a C2PA manifest until the next tool re-encodes them. Plan the deliverable around that, not around the screenshot of a clean corner.
What did not change
Three things teams will try to infer from the toggle. None of them moved.
The model. Flow is still how Gemini users run Veo / Omni-class video. Google Flow is a Veo surface, not a studio is the product boundary. A watermark setting does not add captions, a second family, or a shared credit pool. Veo 3.1 in the Versely catalog is still native audio, official 4K tier, 4 / 6 / 8 second clips. Omni on Google’s side is still Google’s roster. Optional chrome does not make Flow a multi-model studio.
The invisible layers. SynthID is a detector-readable signal in the output, not a logo. Content Credentials are a signed manifest bound to exact bytes. Woodward’s line, quoted by TechCrunch: visible watermarks are optional; SynthID and C2PA are still used for transparency; you can still ask Gemini or Search whether an image was AI-generated. That is Google’s verification path. It is not your Article 50 overlay.
Versely credits. Catalog rows are priced in credits. They did not get cheaper or dearer because Gemini hid a sparkle. Do not tell a client the 40-credit Veo 3.1 row changed on 14 August. It did not.
Provider marking under Article 50 is also not this toggle. The article applied 2 August 2026. Providers of generative systems still owe machine-readable marking of synthetic audio, image, video, and text, with a grace period to 2 December 2026 for systems already on the market before 2 August. SynthID and C2PA are how Google is answering that class of duty. A user-facing sparkle was never the whole duty.
Flow is still a Veo surface
The practical mistake is treating “I can ship a Flow clip without a corner mark” as “I can live in Flow.”
You still export. You still caption. You still pick a different family when the job is a 30-second hold, a motion-control pass, or a talking presenter Flow does not own. Optional visible chrome only removes a reason not to use Flow for the hour you generate Veo. It does not remove the rest of the week.
If the slate is actually Veo-shaped cinematic clips, Flow is a tolerable launcher, watermark on or off. If four of the last ten clips needed another row, you are still assembling a studio out of launchers. Run Veo 3.1 next to Seedance 2.0 and the rest of the catalog. The watermark toggle is a Flow setting. It is not a reason to move the whole slate into Gemini.
Regional locks matter for the chrome only. Woodward said the visible mark stays where law requires it. That is a visible-label problem in those countries, not a SynthID problem. Do not tell an EU buyer the file is unmarked because Flow’s corner is empty. The deployer still owes a perceivable label at first exposure for authentic-looking deepfakes. The disclosure template is that copy.
Versely credits are not this toggle
Bill the job the way the catalog bills it.
- Veo 3.1: 40 credits, native audio, 4K tier, 4 / 6 / 8s
- Seedance 2.0: 69 credits, native audio, 1080p, 4–15s
- Seedance 2.5: 47 credits, native audio, 720p ceiling, 4–30s
Those numbers did not come from Google’s Media watermark setting. They will not track it. If a client asks whether turning Flow’s mark off “saves” anything on Versely, the answer is no. If they ask whether they should generate in Flow to avoid a mark, the honest answer is: you can hide Google’s visible mark in Gemini and Flow as of 14 August 2026, except where law keeps it on; you cannot hide SynthID; C2PA stays on the export until something strips it; you still caption and disclose somewhere else.
The AI video generator is the Versely generate door. Captions are a later pass. If the week is generate-plus-finish rather than live-in-Flow, sign up and treat Google’s toggle as chrome on one vendor surface, not as a studio feature.
FAQ
Does turning Flow’s watermark off remove SynthID?
No. Google’s 14 August 2026 announcement is explicit: invisible SynthID and C2PA stay embedded. The setting only hides the visible mark, and not in countries where law requires that mark to remain.
Did Versely change credit prices when Google shipped the toggle?
No. Catalog credits are Versely prices. They are not Gemini plan SKUs and they did not move on 14 August 2026 because a sparkle became optional.
Is Flow now fine as the only app if the clip looks clean?
Only if the slate is only Google’s video family and you are willing to caption and publish elsewhere. A clean corner is not captions, not a second model, and not a shared bill. Flow is still a surface.