Systeme.io video hosting: 2 GB max, 100 MB recommended, fit a clip
Systeme.io lets you host video up to 2 GB but recommends 100 MB or less. Plan a Sume sales-page clip around that budget and trim what does not fit.

Systeme.io's help page says a hosted video cannot exceed 2 GB, and recommends videos no larger than 100 MB for the fastest loading time. For a sales page or funnel step, treat 100 MB as your target and let the 2 GB figure be a ceiling you never approach.
The page also says storage for media, including videos, is unlimited, so the constraint is page speed, not space.
What Systeme.io states
The numbers below are on Systeme.io's host-videos article, read 2026-10-10. The article gives no format, duration or per-plan limit, so this post does not either.
| Item | Systeme.io says |
|---|---|
| Maximum size | The file size for your videos cannot exceed 2GB |
| Recommended size | No larger than 100MB, for the fastest loading time |
| Storage | Unlimited storage for your media, including videos |
| Advice | Compress videos (for example with Handbrake) to improve loading speed |
A 100 MB budget
Sume has no bitrate setting, so the budget is spent on length and pixel size. One hundred megabytes is 800 megabits if a megabyte is 1,000,000 bytes. A 60-second clip would need to average about 13 megabits per second, and a 30-second clip about 27. That arithmetic is the ceiling; the file you download decides whether you meet it, so measure it.
| Clip length | Average Mbps at 100 MB |
|---|---|
| 15 s | 53.3 |
| 30 s | 26.7 |
| 60 s | 13.3 |
| 90 s | 8.9 |
Make it and cut it
Generate the opening hook with the Video Router: seedance-2.5 takes 4 to 30 seconds at 480p, 720p or 1080p. If you built several scenes, the Timeline 1.0 render joins them and takes an output length of 1 to 1800 seconds, with output width and height from 256 to 2160 and fps of 24, 25, 30 or 60. The default output is 1080 by 1920, so set a landscape width and height for a page video.
curl -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: systeme-trim-001" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/clip.mp4",
"start": 0,
"duration": 45,
"output": { "width": 1280, "height": 720, "fps": 30 }
}'Checklist
Run the order below and stop as soon as the file is under 100 MB.
- Render at 720p before 1080p.
- Cut the clip to the length the page needs; video trim costs $0.02 per job.
- Use fps 24 or 30 rather than 60 unless motion needs it.
- Re-read Systeme.io's article before you ship; it may change.
Sources
Related posts
More in Integrations
- ClickUp taskStatusUpdated webhook: start a Sume Format run
Start a Sume Format run when a ClickUp task changes status: verify X-Signature, derive the Idempotency-Key from the task, cap spend, and write the result back.
- Trello webhook HMAC-SHA1 vs Sume HMAC-SHA256 in one receiver
Can one server verify Trello and Sume webhooks? Yes, with two verifiers: Trello signs body plus callback URL with SHA-1, Sume signs timestamp.body with SHA-256.
- Vercel protection bypass in a Sume webhook URL
Sume cannot add a custom header to a webhook, but Vercel accepts the bypass secret as a query parameter. Check what Sume keeps and who can see the URL.
- Vercel Workflows: a hook that waits for a Sume run webhook
A Vercel Workflows hook pauses a workflow until an outside event resumes it. Use one to wait for Sume's run webhook with no polling.
Written by Sume