Topic added Dec 21, 2024

Put Sora Ai Watermark On Video

Apply an owned watermark image to a short video at the chosen position, scale, and opacity while preserving the original audio.

videoA watermarked H.264 MP4 with original audio, preview, and download.

Examples

See the workflow in action

Review a representative image and video example before you run the workflow, then compare the result against the details that matter for your use case.

Video example

Provider migration

Temporarily unavailable

This workflow is paused while its generation route is moved to WaveSpeed. It cannot start a legacy provider task or charge credits.

How it works

Put Sora Ai Watermark On Video end-to-end workflow

01
Upload the source file and check the preview.
02
Choose only the controls that materially affect this task.
03
Run the job and keep the progress state visible.
04
Compare the result, revise if needed, then download the final asset.

Inputs

Prepare these inputs before running

Prepare the required Source video (10 seconds max), Watermark image, Position, Opacity, Scale before starting Put Sora Ai Watermark On Video.
Use a small representative source first; keep an untouched original for comparison.
State one desired change and a measurable pass condition instead of combining unrelated requests.

Result checks

What a usable result should pass

Compare the Put Sora Ai Watermark On Video result with the untouched source at the same timestamps.
Inspect faces, edges, camera movement, reconstructed areas, and audio for new artifacts.
Reject the result if unrelated subjects, timing, framing, or approved content changed.

Limitations

What this workflow may not guarantee

Generation can produce artifacts; inspect the result before publishing or delivering it.
Do not upload media or use a person, voice, logo, or copyrighted work without permission.
Short-video limits and source quality can prevent stable motion, faces, text, or audio.

Publish checks

What must work before publish

Required inputs are validated before a run starts.
Progress, errors, and retry state remain visible.
The result can be inspected before download.
Failed remote jobs do not consume credits.