Drop a Gemini or Veo clip and the sparkle watermark is cleaned out of every frame on your own device. No upload, no render queue, no account.
MP4 or WebM from Gemini / Veo — the sparkle watermark is removed frame by frame, right in your browser.
Processed frame-by-frame on your device — never uploaded.
Drop your MP4 or WebM into PixKit's video playground and click Remove watermark. Sample frames are scanned to locate the sparkle, low-confidence matches require your review, then each frame is cleaned and the clip is re-encoded locally with WebCodecs. Runtime depends on resolution, duration, codec and your device.
Clean the Gemini sparkle, then finish the job — crop, resize, convert and adjust without uploading a single pixel.
Reverse-alpha math restores the true pixels under the Gemini logo — no blur, no AI guesswork.
Crop to any aspect ratio with draggable handles, then resize to exact pixels or quick scales.
Export to PNG, JPG or WebP with a quality slider and a live file-size estimate.
Every tool runs locally with undo/redo. Nothing is uploaded — it even works offline.
One button, a live before/after wipe, and a downloadable MP4 — all local.
Drag an MP4 or WebM straight from Gemini or Veo onto the drop zone, or click Choose a video. The original loads into the player instantly — it never leaves your device.
PixKit scans sample frames to lock onto the sparkle, then reverse alpha-blends it out of every frame while WebCodecs re-encodes the clip. The progress bar counts frames as they're processed.
Drag the divider across the player to wipe between the original and the cleaned version, then hit Download to save the result as yourname-clean.mp4.
Generated b-roll and concept shots look far more polished on Instagram, X or LinkedIn without a vendor logo pinned to the corner of every frame.
Vertical AI clips get stitched into edits where a corner sparkle survives crops and captions. Clean it once here before it enters your editing timeline.
Storyboards, animatics and pitch videos built from Veo output read as finished work when the tooling watermark is gone — and client footage never touches a third-party server.
A reel mixing filmed and generated shots keeps a consistent look when no frame carries a corner badge. The invisible SynthID still discloses AI origin where it matters.
AI-generated cutaways inside a product walkthrough stop drawing the eye once the animated sparkle is removed from the corner.
Common questions about removing watermarks from Gemini and Veo videos locally.
Google's Gemini app and the Veo models stamp a small sparkle logo — and sometimes a "Veo" text mark — into the corner of every generated video. PixKit removes the visible mark the same way its image tool does, extended across time: it detects the watermark's exact position and scale, then mathematically reverses the alpha-blend that composited it, frame by frame. Because the watermark's own captured alpha maps are used rather than a generic template, the underlying pixels are restored instead of blurred or patched over.
Before cleaning, PixKit samples a dozen frames spread across the clip and scores watermark candidates on each one, voting across frames so a busy background in any single frame can't fool the detector. The winning position and alpha map are then applied to every frame, with residual cleanup that smooths whatever faint footprint the blend leaves behind on hard textures.
Video can't be edited in place, so the cleaned frames are re-encoded to H.264 MP4 (about 12 Mbps) using your browser's built-in WebCodecs hardware pipeline. That means the output is not bit-for-bit lossless — the same trade-off any video editor makes — though at this bitrate a Veo clip looks visually identical. The original audio track is copied through untouched whenever its codec is MP4-compatible. WebCodecs needs a current Chrome, Edge or Safari; Firefox support is still catching up.
PixKit deliberately removes only the visible watermark. Google's invisible SynthID signal, which marks the clip as AI-generated at the pixel level, is left intact — the point is a clean-looking video for your edit or feed, not disguising its origin. And as with every PixKit tool, nothing is uploaded: the whole pipeline runs in your tab, which you can verify from the network panel.
| PixKit | Typical online tools | |
|---|---|---|
| Where your image is processed | On your device — nothing is uploaded | Uploaded to the tool's servers |
| Price, accounts & limits | No sign-up or usage credits; browser safety limits apply | Free-tier caps, accounts, paywalls |
| Speed on large files | No upload or queue; speed depends on the device | Upload, wait in queue, download |
| Works offline | Yes — installs as a PWA | No connection, no tool |
| Where your video is processed | Every frame on your own device via WebCodecs — verifiable in the network panel | Uploaded to a server, queued for a render farm, then downloaded back |
| Cost and limits | No per-minute credits or added logo; practical limits depend on browser memory and codec support | Per-video fees or minute-based credits; free tiers often stamp their own watermark |
| Turnaround for a short clip | Starts locally with live frame progress and a cancel control; speed depends on the device | Upload + queue + render + download — minutes even for tiny files |
One private editor, a tool for every job — all 100% local, no upload.