Automate this: the recording and ffmpeg legs are fully automatable — run this skill directly, or /mobile-release:screenshots for the still set alongside it. No command covers the whole video path because two of its steps are human-only: real-device footage for a submitted preview, and the poster frame (skills/release-automation/references/human-only.md §7).

The two stores are not doing the same thing. Getting this wrong wastes the most time.

	App Store app preview	Play promo video
Deliverable	A video file you upload	A YouTube URL you paste `[verified: Publishing API Listing.video is "URL of a promotional YouTube video for the app"]`
Constraints	15–30 s, exact upload resolution per device class, H.264 or ProRes 422 HQ, ≤ 500 MB, ≤ 30 fps `[verified]`	None on the file — YouTube's rules plus a short list of Play rules `[snippet]`
Source footage	Must be captured from the app itself, "using footage captured on device" `[verified]`	Anything you can put on YouTube
Count	Up to 3 per localization `[verified]`	One URL `[verified]`

There is no uploadable video asset for Play. If the task is "make a Play promo video", the deliverable is a YouTube link and the video behind it, not an .mp4 in a metadata folder.

Confidence marks used throughout this skill and its references: [verified] — read off a primary vendor source on 2026-08-05. [snippet] — secondary source only, plausible but unconfirmed. [unverified] — not confirmed anywhere; run the check given before relying on it.

store-preview-videos