Workspace · VideoPublic pageBest for one-off clip planning. Workspace laneBest future home for repeat clip workflows. Current scopeClip plan JSON only, no heavy browser export chain.
Plan clip ranges without leaving the video lane.
Keep clip planning in the workspace when the cut is one stage in a repeat-use workflow instead of a single public-page visit.
Why this lane exists
Clip planning is execution, not acquisition copy.
This route mirrors the live public clip planner so later presets, history, and export paths can grow in the right layer.
Capability boundary
Playback is a verification step first. Treat the browser as a clean way to test stream health before heavy actions.
- CORS, DRM, hotlink protection, or unsupported codecs can block playback.
- When playback fails, route back to inspector or link-checker instead of pretending every stream is supported.
- Large-screen modes help review playback, but they do not expand browser codec support.
Large-screen mode
Theater mode is for wide layouts. On mobile, the route should fall back to standard mode instead of forcing a cramped expanded canvas.
- Keep the player or preview visible above secondary metadata.
- Do not assume touch devices want side rails open.
- Use this mode only when there is enough width for a stable preview.
Browser clip planner
Mark clip boundaries in the browser before you commit to heavier editing.
Load a local video or direct URL, mark start and end points from the current playback position, then export a precise clip plan JSON for later execution.
This tool marks clip ranges in the browser. It does not export a re-encoded MP4 in this round.
Low-interference sponsor slotView ad policy
Sponsor cards stay after the execution surface instead of cutting across the main input or primary action.
Slot IDad-ws-sponsor-primary-clip-planner
Placementsponsor-card
Modeself-promo
Densitylight