Squarespace background video size: 60 seconds, aim for 40
Squarespace caps an uploaded section background video at 60 seconds and advises under 40. Cut a longer clip to 40 seconds with Sume Video trim first.

Squarespace's help page (updated August 20, 2026) puts a limit of 60 seconds on an uploaded section background video and recommends keeping it under 40 seconds. To get there from a longer clip, cut it with Sume Video trim using start and duration: 40.
Squarespace's numbers are from its help page and Sume's from Video trim, both read 2026-09-30. For what a hero video is, see what is a hero video.
What does Squarespace recommend?
| Item | Guidance |
|---|---|
| Length limit | 60 seconds |
| Best performance | Under 40 seconds |
| Resolution and bitrate | 1080p, at least 3 Mbps |
| Frame rate | 60 fps, especially for slow motion |
| Aspect ratio | Landscape such as 16:9 to minimize cropping |
| Storage | 30 minutes of video per site |
How do I cut to 40 seconds?
Send video_url (a media.sume.com clip), start, and duration: 40, with an Idempotency-Key. Use end instead if you think in out-points; exactly one of the two is allowed. If the source is shorter than your range, the cut clamps and the result warns trim_clamped_to_source. The source can be up to 1800 seconds.
curl -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: squarespace-bg-001" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4",
"start": 0,
"duration": 40,
"mode": "sync"
}'Does the request wait for the result?
The default mode is async. Passing mode: "sync" waits up to 30 seconds for a finished job; otherwise you get a 202 and poll the job status and result routes. The result's video_url is a new MP4, and the source is untouched.
Does the trim fix frame rate or size?
Only if you ask. The optional output field sets width, height (256 to 2160) and fps (24, 25, 30 or 60) with exact precision. Omit it to inherit the source. Squarespace's 1080p and 60 fps advice is guidance rather than a limit, so conform only if your source differs.
Sources
Related posts
More in Use cases
- Suno mashup of two songs: what Sume's music API can do
Sume's music models take a text prompt and one optional image, not audio, so no mashup of two songs. You can generate two tracks and join them end to end.
- Text to speech add pause: Flux, HeyGen and Gemini markers vs Sume
Deepgram Flux, HeyGen and Gemini TTS each use their own pause marker. Sume TTS has none, so use punctuation, speed, or a declared silence in Timeline.
- TikTok 3-minute videos: cut a longer clip to 180 seconds via API
TikTok's page says all creators can post 3-minute videos, some 5 or 10. Sume video-trim writes a 180 s MP4 from a longer clip so any creator can post it.
- TikTok AI voiceover label: generic TTS vs a real person's voice
TikTok's 2026-H2 guidelines: generic text-to-speech narration needs no label, but AI audio that mimics a real person's voice does. How that maps to Sume voices.
Written by Sume