DV360 video creative specs: H.264, 20 Mbps, -24 LKFS audio

Google's Display & Video 360 video creative guidelines ask for H.264, 23.98 or 29.97 frames per second, a bitrate of at least 20 Mbps, and audio aligned to the IAB US spec of -24 LKFS plus or minus 2. Sume's tools do not list a bitrate, loudness or 23.98 control, so use Sume for the cut and the framing and finish the encode elsewhere.

What DV360 asks for

The page lists many container types and three shapes, and it supports VAST 2.0, 3.0 and 4.0. Hosted files can be up to 1 GB, and the maximum size for transcoded serving files is 10 MB.

What Sume covers

Video trim exact is a libx264 yuv420p re-encode and Timeline renders can be 256 to 2160 on each side, so every pixel size in the table, including 1920 by 1920 square, is inside range. Both accept an fps of 24, 25, 30 or 60.

That is where the match ends. The docs list no 23.98 or 29.97 option, no bitrate field (trim rejects codec and crf), and no loudness control. If DV360 rejects a 30 fps file, you need a conform step outside Sume.

A practical split

Use Sume to cut a master to one of DV360's durations and to frame it for the shape you need, then run the final encode through a tool that can set 29.97 and 20 Mbps and normalize audio. Check the result with Video inspect, whose probe-only call is free, to read the actual width, height and duration before you upload.

Treat the page as the source of truth. It is a Google help page with no date on it, so check it again before each campaign.