Vision Pro app preview 3840x2160: Sume trim stops at 2160 per edge

No: Sume's video trim cannot produce a 3840 x 2160 file, so it cannot resize a clip to Apple's Apple Vision Pro app preview size. Apple's App Store Connect page lists 3840 x 2160 (landscape, 16:9) for Vision Pro (read 2026-10-03), and the trim docs limit each output edge to 256 through 2160. A 3840-pixel edge is outside that range. The iPad and Mac sizes on the same page do fit.

That leaves you with two honest options: produce the Vision Pro file in a tool that can render 4K, or leave that device class out of this workflow. Here is what each device asks for and where Sume can help.

The sizes Apple lists beyond iPhone

Apple's iPad entries are 1200 x 1600 for the 13-inch, 11-inch and 10.5-inch classes and 900 x 1200 for the 9.7-inch class, each with a landscape twin (read 2026-10-03). Mac and Apple TV list 1920 x 1080 and are landscape only. Vision Pro lists 3840 x 2160. The general rules still apply: 15 to 30 seconds, 500 MB at most, 30 fps at most, and H.264 or ProRes 422 (HQ).

Cut the sizes that fit

For the fitting classes, video trim takes a hosted clip and an output object with width, height and fps. Frame rate is accepted only with the default exact precision, and Apple's ceiling is 30. The loop below makes the iPad 1200 x 1600 portrait file and the Mac or Apple TV 1920 x 1080 file from one source, using a different Idempotency-Key for each so the two jobs do not collide.

One thing to check by eye: the iPad size is 3:4 and the Mac size is 16:9, so the same source cannot fill both without cropping. The trim docs do not describe a crop mode for output, so decide what each class should show and, if needed, prepare a source for each (for example with Timeline 1.0 or a pixel crop through video filter) before trimming.

import os, time, requests
BASE = "https://api.sume.com"
H = {"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"}

def run(path, body, key):
    r = requests.post(BASE + path, headers={**H, "Idempotency-Key": key}, json=body)
    r.raise_for_status()
    job = r.json()["request_id"]
    while True:
        s = requests.get(f"{BASE}/v1/jobs/{job}/status", headers=H).json()["status"]
        if s in ("completed", "failed", "canceled"):
            break
        time.sleep(3)
    return s, (requests.get(f"{BASE}/v1/jobs/{job}/result", headers=H).json() if s == "completed" else None)

SRC = "https://media.sume.com/artifacts/artf_demo/app-demo.mp4"
for name, w, h in [("ipad", 1200, 1600), ("mac", 1920, 1080)]:
    status, res = run("/v1/video-trim", {
        "video_url": SRC, "start": 2, "duration": 22,
        "output": {"width": w, "height": h, "fps": 30}}, f"app-preview-{name}-001")
    print(name, status, res and res["video_url"])

A release checklist for the device matrix

Treat the device list as a matrix instead of a single export. For each class write down the size Apple lists, the orientation, the length you will use and the file you produced. Apple's page says portrait or landscape for iPhone and iPad, landscape only for Mac and Apple TV, and 3840 x 2160 landscape for Vision Pro, so a vertical master cannot be reused for the last two without a new composition.

Keep every cut inside the 15 to 30 second window, since that rule applies to all classes on the page. After each trim, read the probe with video inspect and compare the width, height and duration with your row. If a number is wrong, fix the request and run it again with a new key; if you retry the same request after a network timeout, reuse the old key so you are not billed twice for the same work.

What to do about the Vision Pro file

Do not try 2160 x 3840 or 2160 x 2160 as a stand-in. Apple's page says 3840 x 2160, and a smaller picture upscaled by someone else's tool is still a different file from what the page asks for. Render that class where the 4K master lives. Sume can still be useful upstream, for example to find the 15 to 30 second range you want from a longer capture: video inspect returns stills at timestamps you choose, so you can pick the start point before the 4K render.

Keep a small table in your release checklist with the device class, the Apple size, and the tool that makes it. A row that says Sume cannot do it is more useful than a file that App Store Connect refuses at upload.