ByteDance Create Video Asset

ByteDance Create Video Asset is the unglamorous but essential setup node for Seedance 2.0's personal-asset system. ByteDance's video models are API-only - the KB frames ByteDance as the lab that keeps its flagship products (Seedream, Seedance) behind the API while giving away the components underneath - and the way Seedance 2.0 keeps a specific person consistent across generations is to register reference videos as assets tied to your account. This node does exactly that: it uploads a video, registers it in an asset group, and hands you back the IDs that every other Seedance node can use.

You'll recognize this node as a warm-up act. Its real value lands later, when you feed its outputs into ByteDance2FirstLastFrameNode's first_frame_asset_id / last_frame_asset_id inputs so a character stays "the same person" instead of a lucky interpretation of a prompt.

The inputs

• video - the clip to register as a personal asset.
• group_id - the crux of the whole node. Leave it empty and the node runs a real-person H5 authentication flow in your browser (a human-verification step) and creates a new asset group for you. Once you have a group, paste its ID back in to skip that verification on future runs.

The outputs

Two strings, and this is the "write these down" moment:

• asset_id - identifies the registered video.
• group_id - identifies the person/group the asset belongs to.

The node even prints a message reminding you to save both, because re-registering (and re-verifying) is the waste this node exists to prevent.

Gotchas

• The auth flow is a one-time human step, and it's real. If you leave group_id empty, expect a browser verification before the asset registers. It's the vendor's consent mechanism, not a bug.
• Save the IDs. Lose them and you're back to re-running the verification flow.
• Assets are bound to the verified person. This is a personal-consent system - the asset is tied to the authenticated identity, so don't treat it as a generic stock-clip library.
• It's a network call, not a local op. No local model, no VRAM - just upload, register, wait, done. Billed through your Comfy account like the rest of the partner/video family.

Thin node, outsize importance if you care about character consistency across a Seedance workflow. Run it once, keep the two strings handy, and your later generations get a lot more specific.