Create a VOD clip from a live-to-VOD asset on Mux, including safely clipping while the source broadcast is still active
domain: docs.mux.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For instant, non-re-encoded clipping of a live-to-VOD or on-demand asset, apply playback modifier query parameters (or equivalent JWT claims for signed playback) to the playback URL specifying relative start/end times, which trims the HLS manifest on the fly without creating a new asset
For a durable, standalone clip asset, POST to the assets endpoint with an input object whose url is set to mux://assets/{asset_id}, referencing the source asset to clip from
Set start_time and end_time (in seconds, offset from the beginning of the source) on the clip's input object; start_time defaults to 0 and end_time defaults to the full duration of the source if omitted
When clipping from the active asset of a live stream that is still broadcasting, always provide an explicit end_time, since the source asset is still growing and an omitted end_time will default to the asset's duration at the moment of clip creation rather than a fixed point you intended
Poll or use webhooks to detect when the new clip asset finishes processing (ready state) before serving its playback ID to viewers
Decide whether to use instant playback-URL clipping (fast, no new asset, ideal for quick highlight sharing) or asset-based clipping (creates a durable, independently manageable VOD asset) based on whether you need the clip to persist and be managed separately from the source
Known gotchas
Omitting end_time while clipping an actively-broadcasting live stream's asset produces a clip that ends wherever the source happened to be at creation time, not a stable, predictable point - always pass an explicit end_time for live clipping
Instant playback-URL clipping and asset-based clipping are different mechanisms with different tradeoffs (no new asset/storage vs. a durable, independently retrievable clip) - picking the wrong one for your use case leads to either unnecessary asset sprawl or a clip you can't manage independently
Relative time markers for instant clipping are based on the start of the asset being clipped, not wall-clock time, so clipping the live-to-VOD recording requires knowing the recording's own elapsed time, not the broadcast's real-world timestamp
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?