Gemini SynthID: 10 video checks a day, which clips to submit
Google's Gemini app allows about 10 video checks per 24 hours, up to 5 minutes in total. Work out how many clips fit and which ones are worth checking.

How many videos can I verify in the Gemini app each day?
About ten. Google's help page says that within any 24-hour period you can do approximately 10 image checks, 10 video checks (up to 5 minutes total) and 10 audio checks (up to 3 hours total). So a batch of 40 clips cannot all be checked in a day, and you have to decide which ones to submit.
The page says approximately, so treat the numbers as a planning guide and re-read them before a big job.
Which limit binds: the count or the minutes
With 10 video checks sharing 5 minutes (300 seconds), short clips hit the count limit first and long clips hit the minutes first. The table is my arithmetic on Google's figures, with whole clips only.
| Clip length | Allowed by the minutes (300 / length) | Allowed by the count | Checks you can run |
|---|---|---|---|
| 8 seconds | 37 | 10 | 10 |
| 30 seconds | 10 | 10 | 10 |
| 60 seconds | 5 | 10 | 5 |
| 85 seconds | 3 | 10 | 3 |
Decide which clips are worth a check
The help page says SynthID currently works for Google AI-generated content, and that Gemini cannot yet recognise watermarks from other sources. A clip from a non-Google model will not come back positive, so spending a check on it tells you little. Spend them on the clips where a Google model was involved.
That is a record-keeping job. Keep the catalog model id with each finished job. The Video Router lists gemini-omni-flash-1.1 next to Seedance, Wan and MiniMax ids, and your log lets you separate the Gemini Omni outputs from the rest.
- Check the final cut you will publish, not every intermediate.
- Check the clips with a Google model in the chain first.
- Write the result and the time next to the job id.
- Leave an unchecked clip marked unchecked rather than assumed clean.
Measure length before you spend a check
A check burnt on a file that is too long is wasted effort. Run video inspect with frames: false and read probe.duration_seconds and probe.size_bytes for each candidate. The help page lists 100 MB and under 90 seconds as the per-file limits. A probe-only call uses no transcript, so the speech-to-text rate does not apply.
A log that keeps the plan honest
One row per clip is enough. Columns that earn their place are the Sume job id, the catalog model id, the clip length from probe.duration_seconds, whether it was submitted to the app, the date, and the answer. Because Google counts per 24-hour period, group your submissions in batches of no more than the limit and note when each batch ran.
Leave anything you did not check marked as unchecked. A blank cell is honest; a green tick that means 'we did not look' is not.
Sources
Related posts
More in Media tools
- Gemini SynthID video check: 100 MB, under 90 seconds, trim first
Google's Gemini app checks videos for its SynthID watermark up to 100 MB and under 90 seconds. Trim a longer Sume video to fit, and know what a miss means.
- Does a Google Ads video need YouTube first? Public or unlisted
Google Ads video ads need a YouTube upload first, public or unlisted. The help pages, two upload routes, and what a Sume MP4 must do before it is an ad.
- H3 Max 1080p image-to-video: check the first frames for a crop jump
Some 1080p MiniMax H3 Max image-to-video clips carry a baked crop jump after two frames. How to confirm it with video-frames and trim 2/24 s with source_in.
- Halloween teaser cut: Video trim start and duration, exact or keyframe
Cut a short Halloween teaser from a longer clip with Sume Video trim: start plus duration, frame-exact or keyframe copy, at a flat public rate per job.
Written by Sume