SynthID text watermark: a Gemini script in a Sume avatar video
Google says SynthID marks Gemini app text. If it becomes a Sume avatar script, the video is a new render, and no docs say the mark carries over.
Google DeepMind lists text from the Gemini app and web experience among the content SynthID watermarks (DeepMind, read 2026-10-02). If you paste such a script into a Sume avatar video, the finished file is a new render of speech and picture. Neither page says the text mark carries into that video, so do not assume it does.
What Google says SynthID covers
The page lists several media types under one name, which is easy to read as one mark that follows content everywhere. It is a family of marks, one per modality.
| Modality | Where the page says it is applied |
|---|---|
| Images and video segments | Content from Google's generative tools |
| Audio | Lyria music generation and NotebookLM podcast features |
| Text | Gemini app and web experience |
| Checking | Upload to Gemini, or the SynthID Detector portal (early testing, waitlist) |
What happens to a script in an avatar render
The Sume docs describe avatar video as script-driven: you send a script or ordered video_inputs, and Sume returns a talking video. The words are turned into speech and frames. A statistical mark in the wording of text is a property of that text, and the docs do not describe it being read, preserved or re-applied.
The same goes for captions. If you burn the script as text on screen, the characters are pixels, not the original string.
What you can say honestly
- "The script was drafted with a Gemini model" is a statement about your process and is yours to make or omit.
- "The video carries a SynthID text mark" is not supported by anything on either page.
- If a platform or law asks about AI-written text, the public-interest text rules are separate from the video label; see the related post on AI-written scripts.
- Keep the original script file with the job id so you can show what was written and what was rendered.
Honest limit
Google says the detector is limited to its own tools and that access is staged. A missing mark in a Sume video does not show the script was human-written, and a present one in the script would not label the video.
Sources
Related posts
More in Models
- Veo 3.1 and Veo 3.1 Fast previews end October 22: what replaces them
Google's deprecations page sets October 22, 2026 as the shutdown date for the Veo 3.1 and 3.1 Fast previews. Dates, the replacement id and what Sume lists.
- Veo seed doesn't make output repeatable; Sume rejects seed
Google says Veo's seed only slightly improves determinism. Sume's v1 video models report seed false and reject the field; keep the output file to get a repeat.
- Which AI video model gives 1080p on Sume, and which stop at 768p?
Sume lists 1080p for Seedance, Wan 3.0, Kling 3.0 and Auto; MiniMax H3 is native 480p or 768p in the panel. Resolution table by model, with the API check.
- Voxtral TTS: open weights under CC BY-NC versus the paid API
Mistral's Voxtral TTS has open weights under CC BY-NC 4.0 and a paid API. What the licence means for a product, and what Sume offers instead.
Written by Sume