alici.ai
alici.ai

Free Seedance 2 Watermark Remover

Upload one video and run a unified frontend removal flow for short AI-generated videos. The page follows the Nano Banana 2 interaction shell.

INPUT

One uploaded video only. No platform selector. No ratio selector.

OUTPUT

Exports one cleaned MP4 while keeping the source video ratio and audio track.

HOW IT WORKS

  1. Upload one generated video file.
  2. The page reads resolution, duration, and aspect ratio automatically before sampling frames.
  3. It prepares the matching watermark removal plan automatically.
  4. The browser merges those corner masks and exports one cleaned MP4 locally.

USE CASES

  • Running one upload-first AI video watermark removal workflow.
  • Cleaning stable corner watermarks from fixed-profile platforms.
  • Applying broader corner coverage for dynamic corner watermark layouts.
  • Exporting a local MP4 without sending the source video to a server.

ABOUT THIS TOOL

This page is the Seedance 2 video counterpart to the Nano Banana 2 image remover. It keeps the same upload-first interaction model while switching the input to video and adding aspect-ratio-aware watermark planning.

The current engine stays frontend-only and uses a unified ffmpeg export pass after building fixed-profile and dynamic corner coverage branches. That keeps the flow honest and local instead of faking a result preview.

The product shape remains simple: one uploaded video in, one processed MP4 out, with platform and aspect ratio handled internally.

FAQ

Do I need to choose the platform manually?
No. The workflow is one upload input with internal platform and aspect-ratio handling.
Which platforms are being prepared?
The current implementation handles supported watermark layouts internally without exposing platform-specific choices in the UI.
Which aspect ratios are supported?
The page prepares profiles for 16:9, 9:16, 1:1, 4:3, 3:4, 21:9, plus a fallback bucket for other ratios.
Does this build export a cleaned video?
Yes. The current implementation analyzes the uploaded video, builds the removal masks, and exports one cleaned MP4 locally in the browser.
Will processing stay local?
Yes. The target architecture remains frontend-only browser processing, consistent with the rest of this project.