PRACTICAL GUIDES / UPDATED 2026-11-15

Choose a Video Watermarking Profile

Use Economy5s for the lowest measured export cost when your product publishes the whole final video. Evaluate Economy2s when short clips and common trims matter. Use Resilient when you want fresh watermark work throughout the timeline and can afford its CPU cost. The SDK default remains Economy5s; choose per export or in your product configuration.

Start with the delivery scenario

Your output A practical starting point Check before shipping
Whole 5–15 second entertainment download, with no later edits promised Economy5s Your intact export, routine recompression and actual verification time
Short clip likely to lose its opening, or platform-generated excerpts Evaluate Economy2s The exact trim offsets and excerpt lengths you expect
A campaign or asset where temporal coverage matters more than export latency Resilient Your delivery edits, visible quality and worker budget
Different crops, aspect ratios or encodes from one master Mark each final rendition A marked landscape master does not qualify a later portrait crop

These are engineering starting points, not separate legal certifications. No preset guarantees recovery after arbitrary edits or deliberate removal.

What each mode actually does

Economy5s computes a fresh watermark on each selected frame in 125 ms windows every five seconds. Economy2s uses the same window length every two seconds. Resilient computes a fresh signal on every frame. All three still decode and encode the complete video. They use the same SDK and watermark engine.

A three-second Economy5s export normally has only its initial window. Removing the first 0.2 seconds can remove that window. Economy2s adds a window near two seconds, but an excerpt between its windows can also miss the mark. Per-frame processing improves temporal coverage; it does not make cropping or watermark removal impossible. See the exact profile protocol.

Measured warm export time on CPU

Whole SDK export, 720p engineering fixtures, two CPU / 4 GiB container, three resident runs per cell; median wall seconds. Models were already provisioned. Fixtures differ in FPS, so these rows are not a pure duration-scaling experiment.

Clip Economy5s Economy2s Resilient
5 s · 24 fps 4.00 s 6.41 s 44.32 s
10 s · 30 fps 9.16 s 13.85 s 107.64 s
15 s · 30000/1001 fps 13.55 s 21.16 s 155.82 s

For the ten-second 720p fixture, median CPU work was 13.16 / 21.49 / 189.35 CPU seconds respectively. The current benchmark includes first-job latency, 1080p, peak memory and raw measurements. These timings do not measure delivery robustness.

Configure the existing SDK

"sdk": {
  "audio_kind": "none",
  "video_profile": "economy_2s"
}

This fragment belongs in your product profile; audio_kind="none" is for a silent video. Valid video values are economy_5s, economy_2s and resilient. For a CLI export, use --video-profile economy_2s or --video-profile resilient; omit it for Economy5s. Use the complete configuration instructions for product-profile precedence.

A small acceptance checklist

  1. Export representative final files with each candidate profile; retain receipts and versions.
  2. Independently verify the intact outputs, then your actual recompressions, trims and crops.
  3. Keep an unmarked control. Record not_checked and budget-limited searches separately from completed negatives.
  4. Choose using recovered evidence, quality and worker cost. Keep the final export gate enabled and never publish the unmarked input as a fallback.

Inspect the CPU benchmark · Integrate your own files · Estimate costs

Compare recovery counts after edits, by version — intact short exports and window-free excerpts have separate rows.

Browse documentation ↗