Pinterest Idea ad video: 100 MB on web, 2 GB in app, 5 minutes max

For a Pinterest Idea ad, the video limit is 100 MB if you upload on the web and 2 GB if you upload from iOS or Android, with a maximum length of 5 minutes. At the full 5 minutes, 100 MB allows an average of about 2.67 Mbps, so a web upload needs a lighter file than an app upload. Sume cannot set a bitrate, so you control the size through length, resolution and frame rate, then verify with a probe.

What Pinterest lists for Idea ads

The limits come from Pinterest's own ad spec page for Idea ads. The page also gives a recommended file size and says full-bleed media should be 1080x1920.

The bitrate each cap allows

Average bitrate is size in bits divided by seconds. This uses decimal units (1 MB = 8 megabits, 1 GB = 1,000 MB) and ignores container overhead, so treat the results as upper bounds.

Average bitrate at 300 seconds, computed 2026-10-09, as listed below.

• A shorter video raises the allowed bitrate in proportion. At 60 seconds, 100 MB allows 800 / 60 = 13.3 Mbps.
• 100 MB (web): megabits 100 x 8 = 800; divided by 300 s 2.67 Mbps
• 1 GB (recommended): megabits 1,000 x 8 = 8,000; divided by 300 s 26.7 Mbps
• 2 GB (app): megabits 2,000 x 8 = 16,000; divided by 300 s 53.3 Mbps

Rendering the file on Sume

Timeline 1.0 outputs an even width and height from 256 to 2160, with fps of 24, 25, 30 or 60, and defaults to 1080x1920 (Sume docs, read 2026-10-08). That default already matches the full-bleed size Pinterest recommends. The docs say the job rejects codec, crf and bitrate fields, so the levers are length, size and fps.

If a web upload is over 100 MB, shorten the cut with video trim, or render at a lower fps or a smaller size, then probe again. Video trim with precision exact re-encodes with libx264 and yuv420p, and exact accepts an output conform with width, height and fps.

• Timeline render: $0.10 per output minute, rounded up. A 300-second render is 5 minutes, so 5 x $0.10 = $0.50.
• Video trim: $0.02 per job.
• Video inspect with frames set to false returns size_bytes, duration_seconds, video_codec, width, height and fps; it is billed by Modal compute, not a fixed price.

A check before the web upload

Divide size_bytes by 1,000,000 and compare with 100. If the file is longer than 300 seconds, cut it first, because the 5-minute limit applies on both paths. If you upload in the app instead, the 2 GB cap is far above what a 5-minute ad needs at ordinary settings, so the 5-minute length is the limit that matters there.

Which path to plan for

If you do not know who will upload, plan for the web limit. A file that is under 100 MB uploads on both paths, while a larger file is limited to the app. For a team that uploads from a laptop, that means checking size_bytes on every export, not only on the ones that look long.