FAQ

Yes for local desktop workflows when the local engine, source media, and required tools are available. Cloud sync, workers, licensing checks, and OAuth integrations require backend access.

No. Cloud login syncs account/project/job metadata, but source videos stay on the device unless you explicitly choose Upload to cloud or full media import/download.

The app can inspect and import supported public links where access is allowed. Some links fail due to restrictions or login requirements.

They may be private, removed, region-blocked, login-required, protected, or unsupported by the current downloader/source rules.

No. The app can help track rights information, but it cannot guarantee that rights issues will never happen or that a platform has cleared the content.

Yes, but use music you own or have permission to use. Royalty-free music still has license terms.

Yes. Use 9:16 exports, caption-safe layout, and platform-ready metadata.

Yes. Caption Studio supports text, timing, style, preview, SRT export, and burned-in captions.

Yes. Transcript Editor removes video/audio sections by timestamped transcript ranges.

The queue can track multiple jobs. Avoid overloading low-power machines with too many heavy tasks.

Exports are saved in the configured local export/storage folder. Check Storage Manager and Settings.

Yes, carefully. The folder must stay available locally while jobs run.

Only where official provider credentials, app review, secure token storage, and provider publishing code are implemented. Manual posting preparation remains available.

It is a review score based on transcript/timing signals. It helps prioritize clips but does not make final editorial decisions.

Speed depends on source length, audio quality, model size, CPU/GPU capability, and memory.

Check Error Logs, Processing Queue, source media availability, disk space, and FFmpeg status.