Product recording
Prepare the browser and shot, let the user perform and record the interaction,
then bring the original capture into packages/brand. This is an internal
Remotion workflow; keep this skill in .agents/skills.
Prepare Studio and Chrome
Use canvas-capture-extension to build
and install the extension in its durable directory. Reload the installed
extension through chrome://extensions after rebuilding; a successful build
alone does not refresh Chrome's loaded extension.
Use an existing compatible Chrome with Canvas Draw Element enabled.
Preserve unrelated browser tabs and unfinished recordings.
Find the requested composition's registration and owning package. Follow
studio for dependency/build preparation and server
startup, but start in the owning package and open the recording in compatible
Chrome. Use bunx remotion studio --no-open and the exact URL printed by
that invocation, including when it reports an existing server. Do not assume
port 3000 belongs to this checkout.
Open the composition with studioPixelRatio=4 in the query string, preserving
any other URL parameters. For example, if Studio reports port 3001:
http://localhost:3001/RollerSkiRoughCut?studioPixelRatio=4
The parameter increases Studio's canvas backing resolution for sharp
timeline captures. It does not set the extension's output resolution.
RollerSkiRoughCut lives in packages/jonnys-videos; locate other requested
compositions rather than assuming they live in packages/example.
Verify the requested composition and current timeline are visible. Activate
Canvas Capture through its toolbar icon or Extensions menu.
Prepare an optional shot and hand off
- Arrange the viewport, timeline height/zoom, playhead, and sidebars as needed
for the requested demonstration. Do this before framing the shot.
- Use the extension's
setup_shot and get_shot WebMCP tools when available.
They are exposed after activating the extension. Choose the viewport, one
visible element, or a rectangle; inspect a still with get_shot and
preview: true. The crop stays fixed in viewport CSS pixels, so reframe after
changing the window or layout.
- If those tools are unavailable, use the extension's Entire page or
Select area controls and visually verify the selection. Output zoom and
dimensions are separate from
studioPixelRatio; set them for the intended
shot and check the displayed dimensions.
- Before handing off, note existing capture files and their modification times
in the user's Downloads folder so the new take can be identified later.
- Leave the shot ready without starting recording. Tell the user to click
Record, perform their interaction, stop, and choose Download recording.
The user controls the cursor and recording start/stop. Pause here until they
have recorded; do not substitute an older download or claim an import is done.
Import the downloaded take
After the user finishes, identify the new, fully downloaded capture in
~/Downloads by filename and modification time relative to the handoff.
Exclude incomplete .crdownload files. If several takes are plausible, ask
which one to use.
Keep the original MP4 or WebM with embedded REMOTION_CAPTURE_DATA metadata.
Do not transcode it before import; the metadata carries editable cursor data.
Use import-canvas-capture, targeting
packages/brand and its composition registration file (currently
src/Root.tsx). Choose an unused, descriptive composition ID. From
packages/brand, the local built CLI can be invoked as:
node ../cli/remotion-cli.js canvas-capture import \
/absolute/path/to/downloaded-capture.mp4 \
--root-file src/Root.tsx --composition TimelineRecording
Follow that skill's dimension, dependency, and conflict guidance. Inspect
the capture dimensions and pass --width and --height to match them when
importing the full shot: the default 1920×1080 composition can crop a larger
recording because the generated component retains native video dimensions.
Preserve the download and existing compositions/assets.
Review the generated component, registration, copied public asset, and any
dependency changes. Run the relevant brand validation before offloading.
For exports, follow remotion-render and use
Remotion's bundled browser. The Chrome instance used for recording does not
need to be passed to the renderer.
Offload the recording
Finish with offload-r2: upload the imported recording
to remotion.media, verify that the public object's SHA-256 matches the local
file, and replace the composition's local asset reference with the hosted URL.
Remove the repository-local media copy only after verification; preserve the
original download. Follow that skill's focused validation, then report the
composition ID, hosted URL, and changed files. Distinguish a browser ready for
recording from a completed, imported, and offloaded take.
1---2name: product-recording3description: Prepare Remotion Studio for a user-recorded product demo with Canvas Capture, then import the downloaded take into packages/brand as an editable composition. Use for recording Studio interactions, timeline demos, and product shots.4metadata:5 source: https://skillmd.com/skills/remotion-dev/product-recording6---78# Product recording910Prepare the browser and shot, let the user perform and record the interaction,11then bring the original capture into `packages/brand`. This is an internal12Remotion workflow; keep this skill in `.agents/skills`.1314## Prepare Studio and Chrome15161. Use [canvas-capture-extension](../canvas-capture-extension/SKILL.md) to build17 and install the extension in its durable directory. Reload the installed18 extension through `chrome://extensions` after rebuilding; a successful build19 alone does not refresh Chrome's loaded extension.202. Use an existing compatible Chrome with Canvas Draw Element enabled.21 Preserve unrelated browser tabs and unfinished recordings.223. Find the requested composition's registration and owning package. Follow23 [studio](../studio/SKILL.md) for dependency/build preparation and server24 startup, but start in the owning package and open the recording in compatible25 **Chrome**. Use `bunx remotion studio --no-open` and the exact URL printed by26 that invocation, including when it reports an existing server. Do not assume27 port 3000 belongs to this checkout.284. Open the composition with `studioPixelRatio=4` in the query string, preserving29 any other URL parameters. For example, if Studio reports port 3001:3031 ```text32 http://localhost:3001/RollerSkiRoughCut?studioPixelRatio=433 ```3435 The parameter increases Studio's canvas backing resolution for sharp36 timeline captures. It does not set the extension's output resolution.37 `RollerSkiRoughCut` lives in `packages/jonnys-videos`; locate other requested38 compositions rather than assuming they live in `packages/example`.39405. Verify the requested composition and current timeline are visible. Activate41 Canvas Capture through its toolbar icon or Extensions menu.4243## Prepare an optional shot and hand off4445- Arrange the viewport, timeline height/zoom, playhead, and sidebars as needed46 for the requested demonstration. Do this before framing the shot.47- Use the extension's `setup_shot` and `get_shot` WebMCP tools when available.48 They are exposed after activating the extension. Choose the viewport, one49 visible element, or a rectangle; inspect a still with `get_shot` and50 `preview: true`. The crop stays fixed in viewport CSS pixels, so reframe after51 changing the window or layout.52- If those tools are unavailable, use the extension's **Entire page** or53 **Select area** controls and visually verify the selection. Output zoom and54 dimensions are separate from `studioPixelRatio`; set them for the intended55 shot and check the displayed dimensions.56- Before handing off, note existing capture files and their modification times57 in the user's Downloads folder so the new take can be identified later.58- Leave the shot ready without starting recording. Tell the user to click59 **Record**, perform their interaction, stop, and choose **Download recording**.60 The user controls the cursor and recording start/stop. Pause here until they61 have recorded; do not substitute an older download or claim an import is done.6263## Import the downloaded take64651. After the user finishes, identify the new, fully downloaded capture in66 `~/Downloads` by filename and modification time relative to the handoff.67 Exclude incomplete `.crdownload` files. If several takes are plausible, ask68 which one to use.692. Keep the original MP4 or WebM with embedded `REMOTION_CAPTURE_DATA` metadata.70 Do not transcode it before import; the metadata carries editable cursor data.713. Use [import-canvas-capture](../import-canvas-capture/SKILL.md), targeting72 `packages/brand` and its composition registration file (currently73 `src/Root.tsx`). Choose an unused, descriptive composition ID. From74 `packages/brand`, the local built CLI can be invoked as:7576 ```bash77 node ../cli/remotion-cli.js canvas-capture import \78 /absolute/path/to/downloaded-capture.mp4 \79 --root-file src/Root.tsx --composition TimelineRecording80 ```8182 Follow that skill's dimension, dependency, and conflict guidance. Inspect83 the capture dimensions and pass `--width` and `--height` to match them when84 importing the full shot: the default 1920×1080 composition can crop a larger85 recording because the generated component retains native video dimensions.86 Preserve the download and existing compositions/assets.87884. Review the generated component, registration, copied public asset, and any89 dependency changes. Run the relevant brand validation before offloading.9091For exports, follow [remotion-render](../remotion-render/SKILL.md) and use92Remotion's bundled browser. The Chrome instance used for recording does not93need to be passed to the renderer.9495## Offload the recording9697Finish with [offload-r2](../offload-r2/SKILL.md): upload the imported recording98to `remotion.media`, verify that the public object's SHA-256 matches the local99file, and replace the composition's local asset reference with the hosted URL.100Remove the repository-local media copy only after verification; preserve the101original download. Follow that skill's focused validation, then report the102composition ID, hosted URL, and changed files. Distinguish a browser ready for103recording from a completed, imported, and offloaded take.