Mux 1080p input ceiling of 8 Mbps and a Sume 1080x1920 Timeline render

Short answer

Mux's input guide treats a 1080p asset as standard when it is 1080p/2K or smaller (up to 2048x2048), at 8 Mbps or below, with a keyframe at least every 20 seconds, and frame rates from 5 to 120. Sume Timeline's default output is 1080x1920, which fits the size limit. The Sume docs do not state an output bitrate, so check it on a sample before you assume it passes.

Mux's page also uses the word non-standard for some inputs outside these limits (for example, frame rates above 60 fps at 4K), so read the current processing notes before you send renders that exceed the standard envelope.

Envelope table

Numbers from Mux's page sit beside the Sume Timeline values from its docs.

Where the 2160 setting bites

Sume allows width and height up to 2160. A 2160x3840 vertical render would exceed Mux's 2048x2048 standard envelope, and Mux's 4K tier has its own limits (up to 4096 pixels in any dimension, 20 Mbps or below). If your delivery is a Mux-hosted vertical video, 1080x1920 is the setting that stays in the standard band. Raise it only when the player and the audience need more pixels.

• Leave output.width and output.height at the 1080x1920 default for a vertical asset on a standard Mux tier.
• Do not set fps above 60 on Timeline; the doc only permits 24, 25, 30 and 60.
• Run a 10-second sample, measure bitrate with ffprobe, then render the full piece.

Measure instead of guess

The cheapest check is a short sample. A render of one or two slots costs the same $0.10 per output minute, so a sample is cents. Read the file's bit rate from the container, compare to 8 Mbps, and keep a margin. If a render lands above the ceiling, a Video Trim conform to a smaller size or lower fps is a $0.02 re-encode, though it does not set a bitrate directly.

The whole point is to avoid finding out at the end of a long job. A 30-minute master is 1,800 seconds and $3.00 at the public rate; failing after upload wastes both the render and the transfer time.

Related

For the cost side of long renders, read the 30-minute render cost. For short loops on a Mux-hosted page, read the animated GIF cap comparison.

A short test plan

Run three samples: a still-heavy slideshow, a talking head and a fast-motion montage. Bitrate depends on content, so the same settings produce different numbers. If the highest of the three is under 8 Mbps with some margin, the piece will pass the standard-input check for 1080p. If it is over, shrink the output size or fps and measure again.

Record the results next to the render settings you used. When you come back to the pipeline in six months, the log tells you why you picked 1080x1920 at 30 fps rather than a larger frame. Because Mux publishes these thresholds on its own page, recheck the page before relying on a figure from a note.