Merchant Center product video 720p minimum: what to request

Merchant Center video_link needs at least 720p (1280x720). Sume's generated video defaults to 720p; probe a file first, then conform with Video trim if needed.

4 min readSume
All posts

Google asks for product videos of at least 720p (1280x720) in video_link. On Sume's legacy video route resolution is 720p when omitted, with 1080p also accepted, so either value starts at the floor. Probe any file you did not generate before you submit it.

Google's number is from its Help page; Sume's from Video generation, read 2026-09-30.

What does the 720p floor mean for a vertical video?

The page states the minimum as 720p (1280x720) and does not say how a 9:16 file is measured, so this post does not guess. If you want a safe margin, 1080x1920 (vertical) or 1920x1080 (horizontal) clears 1280x720 on either reading of the rule.

Which Sume settings reach it?

Resolution settings from the Sume docs, read 2026-09-30.
ToolSettingNote
Video generation (legacy route)resolution: 720p or 1080p720p is the default when omitted; 4k is rejected on that URL
Video trim outputwidth and height 256–2160Exact precision only
Timeline outputeven integers 256–2160Default is 1080x1920

How do I check an existing file?

Sume does not warn you when a file is below Google's minimum, so probe it. Video inspect probes one Sume-hosted video for duration, size, rotation, fps, codecs, audio and HDR. Compare the reported size with 1280x720 before you add the URL to a feed.

Can Video trim raise a small clip to 720p?

It can set the output size: exact precision is a frame-accurate re-encode (libx264, yuv420p) at the width and height you give. The docs do not describe quality upscaling, so a small source stretched to a larger frame will not gain detail. Start from a source that is large enough; for larger sizes see 4K product video.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume