Eventbrite event video: 24-hour review and a 2:1 cover image

Eventbrite reviews an uploaded event video for moderation, and its help page says approval can take up to 24 hours. It also says images work best at a 2:1 aspect ratio, and that you must own the images and videos you upload or have permission from the copyright holder. So make the clip and the cover a day before you need the page to look finished, not the hour you publish.

The Eventbrite facts below come from Add images and video to your event, read 2026-10-03. That page gives no file size, length, format or resolution for video, so this post does not either; check the upload screen. Sume's side comes from Image Router and Timeline 1.0.

What does Eventbrite say about the video review?

Three statements on that page affect a schedule and a sign-off:

• An uploaded video is reviewed for moderation purposes, and approval can take up to 24 hours.
• You must own the images and videos you upload or have permission from the copyright holder.
• Images are best at 2:1 (twice as wide as tall) for cropping, and focus points are used to create the square thumbnails shown in search results.

How do I plan the asset run around a 24-hour review?

Treat approval as a dependency, like a print proof. Work back from the date the page must be live: render the clip, upload it, and leave a full day before any announcement email or ad points at the page. If a sponsor must approve the video first, that approval belongs before the upload, not after.

Sume jobs are asynchronous. A timeline render takes a spine plus ordered clips and returns one MP4; you poll GET /v1/jobs/:id/status or use a webhook, and read the file from GET /v1/jobs/:id/result (see Jobs and results). Plan for a re-render if the review rejects the file, since a new render is a new job.

How do I make a 2:1 cover with Sume?

Image Router lists 2:1 among its normalized aspect ratios, but a model accepts only the values its catalog entry lists, so read supported_parameters from GET /v1/images/models before pinning one. For GPT image models the docs also allow custom pixels: both edges multiples of 16, max edge 3840, aspect ratio at most 3:1, and 655,360 to 8,294,400 pixels in total. 1920 by 960 is exactly 2:1 and passes those rules.

curl -X POST https://api.sume.com/v1/images \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: event-cover-001" \
  -d '{
    "model": "sume/auto",
    "prompt": "Wide rooftop dinner table at dusk, string lights, empty chairs, no text",
    "aspect_ratio": "2:1"
  }'

Where should the focus point sit?

Eventbrite uses a focus point to build the square thumbnail from a 2:1 image, so the subject needs to survive a square crop of the middle. Ask for the subject centered and the sides as breathing room, and avoid putting the date or the event name near the left and right edges, where a square crop removes them. Prompts that say "no text" keep dates and names out of the generated pixels, so you can add exact wording where it is controlled.

Sume does not set Eventbrite's focus point. That is a control in Eventbrite's editor.

What does Sume not do for Eventbrite?

Sume's docs describe no Eventbrite connector, so the files are uploaded by you. Nothing in Sume checks a video against Eventbrite's moderation, and a file that renders cleanly can still be rejected. If a long recording needs shortening before upload, video trim cuts a range into a new MP4 for $0.02 a job; the page itself does not state a length cap, so choose a length that fits the event page rather than a number from this post.