Does it work without existing subtitles?
Yes. The intended workflow starts from the audio in a local video file, not from YouTube, Netflix, or an existing subtitle track.
The FAQ should remove friction around file support, privacy, subtitle formats, and playback. These are the objections users will have before they trust the tool.
Yes. The intended workflow starts from the audio in a local video file, not from YouTube, Netflix, or an existing subtitle track.
Yes. The product is positioned around user-owned local files. Upload, preview, generate, edit, and export are the core loop.
For learners, English can become visual noise. The translation stays available in notes and can be toggled on when needed.
Desktop players such as VLC, IINA, mpv, and PotPlayer commonly support ASS. SRT remains the broad compatibility format.
SRT is easiest across devices. For mobile users who cannot load external subtitles, burned-in MP4 should be a later export option.
The planned cloud design should delete source files after processing, with account controls for data deletion and saved artifacts.
The current build demonstrates the upload, preview, edit, and export experience before backend ASR is connected.