FindVideoMomentBETA

INDEPENDENT EVIDENCE / UPDATED OCTOBER 8, 2026

EmbeddingGemma 2 Browser Video Search Benchmarks

Useful matches. Real misses. Measured waiting times.
This is a small lab dataset, not a general accuracy claim.

By FindVideoMoment · Updated . This EmbeddingGemma 2 video search benchmark reports independent POC measurements and their method, separately from voluntary community data.

Independent laboratory results

Measured October 7–8, 2026 on Apple M5, 16 GiB RAM, macOS 26.5.1, Tabbit Chromium 152, Apple Metal WebGPU. Transformers.js 4.3.1, q4, model revision daa72c51243991dfcaf9f9137d2c573d8f7790c0, 1fps and four-second windows. These are prior POC results, not release-build measurements.

Fixed single-target interval retrieval · 15 frozen queries per tutorial
VideoToken budgetIndex time (s)Top-1Top-3Top-5
LibreOffice screen tutorial140818.214/157/158/15
LibreOffice screen tutorial70491.905/157/157/15
Blender tea tutorial1401312.016/1510/1511/15
Blender tea tutorial70641.068/1511/1512/15

Video durations: LibreOffice 14:19; Blender 22:50. The 70-token runs were 39.9% and 51.1% faster than their respective 140-token baselines. The quality protocol checked whether a candidate window’s center fell inside one pre-labelled target interval. Labels were not independently reviewed and did not enumerate all valid alternative scenes.

At 70 tokens, LibreOffice indexing took 491.90 seconds. Top-3 retrieval found 7/15 targets: 7 of the 15 pre-labelled LibreOffice targets had a matching candidate among the first three results. This is a result for that frozen query set, not general model accuracy.

Failures matter

LibreOffice’s landscape print preview, cell-border popup and selected four-column table were missed in the Top-5 at 70 tokens. Blender’s faceted cylinder, selected lower semicircle and upright green leaf were also missed. The dataset does not establish dependable professional retrieval.

Synthetic stress tests — 140 tokens

Repeated video content · speed and stability only · NOT the 70-token release configuration
DurationIndexing timeInterpretation
10 minutes575.64 sSynthetic repeated content; no quality conclusion
30 minutes1852.71 sSynthetic repeated content; no quality conclusion
60 minutes3393.19 sSynthetic repeated content; no quality conclusion

No crash or sustained linear JS-heap growth was observed in these runs. GPU memory and total-process peak memory were not verified. A 300-second run previously encountered Apple hardware decode error NSOSStatusErrorDomain -12905; its retry succeeded. A 70-token, 60-minute release-build stress test remains a launch gate.

First use, progressive search and reuse

Privacy scope of the original experiments

The observed browser network traffic did not upload video, frames, thumbnails, queries or embeddings. The wider research process was not strictly zero-upload: thumbnail contact sheets were sent into an assistant session for annotation. Browser-runtime privacy and the entire research workflow are different scopes.

Voluntary community statistics

Rolling window: last 30 days. Snapshot checked: . Refresh target: hourly.

Insufficient samples

Opt-in sessions only. No community performance figures are available.

How community data is counted

Only consented sessions that actually start indexing qualify. We count the first started run per temporary tab session and its first terminal event. Completion rate uses started sessions as its denominator; median indexing ratio includes only completed runs, creating survivor bias. Duplicate event IDs are ignored, fields and impossible timing ratios are rejected, and global plus session limits restrict spam. These are self-selected, unverified browser reports, not unique people or laboratory ground truth.

Groups below 30 qualifying sessions are hidden; completion metrics also require at least 30 completed sessions. User-reported found rate is Yes/(Yes + No) among explicit respondents in the consented session subset. Unsure answers are excluded from that denominator. It is not Top-3 accuracy. Answers submitted without diagnostic consent are not linked to session metrics. No comments or individual records are public. Collection remains off until retention cleanup is verified. See retention and privacy.

Google’s Video Moments Finder vs. this browser benchmark

Google’s Video Moments Finder runs inside the Google AI Edge Gallery app on Android and iOS, as described in the official Google announcement. FindVideoMoment is an independent browser tool: it searches local video without uploading it and can run on compatible desktop Chromium browsers with WebGPU. It is not developed, operated, certified or endorsed by Google. Both offer on-device search; the distinction here is the app versus browser experience, not a claim of better accuracy or speed.

These timings and retrieval counts measure our independent browser POC, not Google AI Edge Gallery. No equivalent test of the official app was run, so this dataset cannot rank the two tools against each other.

Sources and limitations

Prior POC reports and frozen evaluation files are preserved in the independent local research repositories. No copyrighted video frames are republished on this page. The animated action sample used Big Buck Bunny, © 2008 Blender Foundation, CC BY 3.0. Tutorial sources: Creating Charts With LibreOffice by DistroTube and Blender Tutorial. A cup of tea. by Fun with Open Source, both CC BY 3.0 according to the preserved source/license records checked October 7, 2026. No tutorial media is hosted here.

One Mac, two tutorials, small frozen query sets, no independent human adjudication, and limited codec coverage. No comparable competitor evaluation has been performed. Search demand and future Google or ChatGPT visibility remain unknown.

Try Your Own Video → Read about the model