For the CapCut "Stickers" panel. Stickers must first obtain a stable resource identity and authorization, then be added to the draft by time, position, scale, and rotation.
When to use
- Find trending, Vlog, interactive, masking, holiday, e-commerce, or brand stickers.
- Download and add official stickers, or move, copy, or delete existing stickers.
- Validate the sticker's time range, layer, and safe zone.
Capability boundaries
- ✅ Can do: sticker candidate search, preview/download planning, timeline addition, move, copy, delete, and inspect.
- ⚠️ Requires conditions: official stickers need entitlement receipts; writes need isolated drafts; layout conclusions need playback.
- ❌ Should not use: do not generate new sticker images, do not guess resource IDs, do not use stickers for unauthorized trademarks or likenesses.
Quick start
You can simply say: "Find a Vlog travel arrow sticker", "Add a data chart sticker at 3–5 seconds", "Delete the sticker covering the subtitles". On first use, load feature flow。
Run contract
- Trigger conditions: the user requests sticker search, filtering, download, addition, adjustment, copy, or deletion.
- Required capability:
media.sticker、media.official_resource、media.official_resource_apply、timeline.edit、timeline.duplicate、timeline.remove。 - Minimum CLI version:
1.6.19; locally known resources can go throughmedia add-sticker, official download/application still depends on capability and Adapter. - Default risk:
reversible_write。 - Input facts: resource ID, format and authorization, start/duration, position, scale, rotation, track layer, and frame safe zone.
- Confirmation points: confirm separately for downloading restricted resources, writing drafts, covering brand elements, or native playback.
- Success evidence:
playback; thumbnails and material entries cannot prove the sticker is in the correct on-screen position. - Prohibited actions: do not guess resource IDs by name, treat membership marks as commercial authorization, cover protected subtitles/faces, or repeatedly download without stateful readback.
Workflow
Step 1 — Search candidates
Search candidates by purpose, style, aspect ratio, entitlement, and usage, and preview them.
Step 2 — Obtain resources
After downloading, register the official resource receipt, or confirm the local resource ID already exists.
Step 3 — Add and transform
According to feature flow add to the isolated draft and adjust time/transform.
Step 4 — Validate
Validate materials, tracks, and time range, then play back to check occlusion, edges, and rhythm.
Step 5 — Recover
If not passing, locally delete/move; if download or application is ambiguous, query rather than resubmit.
Rules
- Candidates first pass authorization, format, and usage gates, then are sorted by style.
- Stickers must be bound to an explicit time range and safe zone.
- All transforms use absolute values and segment IDs.
- Download, application, and playback are three different kinds of evidence.
Gotchas
- Membership icon treated as a license: Pro entitlements do not automatically cover commercial publishing rights.
- Sticker covers subtitles: Check the safe zone and protected objects before applying.
- Too many stacked on the same screen: Limit density per the brief; do not use all just because there are many candidates.
- Copy shares state: Verify whether the copy's materials and transforms are independent.
- Repeated clicks after download timeout: First query the resource status and the local cache identity.
Security and data
Do not collect account secrets; official resources store only a minimal entitlement snapshot, resource ID, file digest, and purpose, avoiding recording irrelevant account information.
See the minimal Job at examples/minimal-job.json。