Cloudflare's 10-2000 px media transform vs Sume's 256-2160 trim output

Cloudflare's media transformation binding accepts a target width and height of 10 to 2000 pixels. Sume's video trim accepts an output of 256 to 2160 on each side, plus an fps of 24, 25, 30 or 60, and only with precision: "exact". If you need a 2160 pixel edge, Cloudflare's range stops short and Sume's covers it.

The Cloudflare numbers are from its binding page and Media Transformations page, read 2026-10-03. Sume's come from video trim.

The ranges in one table

The table sets the two services side by side. It covers frame size and the way each one resizes.

What the Cloudflare binding adds

The binding page says operations through it are billed per operation, not by how many unique requests there are, and that during the public open beta they will not be billed. It also says binding responses are not cached automatically, so you need the Cache API or R2 if you want to avoid repeated work.

That is a different cost model from Sume's flat job price. A repeat request to Sume is a new job unless you reuse the idempotency key.

Using the Sume output field

Send output: { width, height, fps } on the trim request. Omit the field to inherit the source. Sending it with precision: "keyframe" fails with video_trim_output_requires_exact, because a stream copy cannot be resized.

The conform does not choose a crop for you in the docs for trim, so match the aspect ratio of the source or accept the geometry you ask for. If you need a crop first, video filter has a crop op in fractions of the frame and a free check endpoint.

• Trim duration runs 0.2 s to 900 s.
• Source must already be on media.sume.com.
• Both sizes must fall inside 256 to 2160.

Choosing a size

For social video the common target sits inside both ranges. If you need a smaller thumbnail-sized frame below 256 pixels, Sume's trim will refuse it; video frames accepts max_edge from 16 to 2160 for stills instead.

Picking sizes that work on both

If you plan to use both services on the same clip, choose a frame between 256 and 2000 pixels on each side, which sits in both ranges. A 1080 by 1920 output meets that, and it is also Sume's timeline default.

Remember Cloudflare's dimension range starts at 10, so tiny thumbnails there are possible, while Sume's trim output will refuse anything under 256.

Frame rate on each side

Cloudflare's summary page lists no frame rate parameter, while Sume's trim accepts fps of 24, 25, 30 or 60 and nothing else. If your source runs at 29.97, Sume will resample to one of the four values, so choose the nearest and check the result for judder.

Omitting output inherits the source geometry and frame rate, which avoids resampling altogether.