Square Online video section: 100 MB, one hour, loop and autoplay
Square Online's Video section takes your own file up to 100 MB and one hour, with loop and automatic playback. How to cut and size a product clip for it.

On Square Online you add your own product video through a Video section: choose Custom as the source and upload a file of up to 100 MB and one hour, then set loop and automatic playback. Square's help article says this works with all common video file types. A Sume video-trim result is an MP4, so a short cut meets the type rule; the size you have to check yourself.
What does Square's help page allow?
The page says that custom video upload, embedded external content and section backgrounds are available with a Square Online Plus or Premium subscription, and that you can add videos from the Square Dashboard under Channels, then Square Online, then Website, then Edit site.
| Way to add video | Limit or setting on the page |
|---|---|
| Upload your own file (Video section, Custom) | All common video file types, 100 MB per video, 1 hour; loop and automatic playback settings |
| YouTube (Video section, YouTube) | A YouTube URL; player controls and automatic playback settings |
| Other hosts (Embed code section) | Paste the video's embed code |
| Background video (main banner section) | Up to 10 GB of background video storage; adjustable playback speed |
Does this cover a video on each product?
The article describes sections you place on pages, not video attached to an item in your catalog. I found nothing in it about per-item product video, so treat the Video section as a page-level tool. A product gets its clip when the page that shows it has a Video section. If you need video on every item page, check Square's item editor separately; this post does not claim one exists.
For the editing side, the page lists loop and automatic playback as settings you adjust after uploading. It does not say anything about sound, so check how your published page behaves in a browser, especially on a phone.
How do you size a product clip for it?
The one-hour limit is not the constraint for a product clip; 100 MB is. Video trim cuts a short range with start and duration and can drop sound with audio: "drop" for a silent looping banner. Its output object conforms the frame to a width and height of 256 to 2160 and fps of 24, 25, 30 or 60. A smaller frame and a lower fps are the settings you control; the docs expose no bitrate. Cutting a 10-second range from a long source is the largest saving, and it costs $0.02 per job.
Check the size of the returned file before you upload, then place it. If the file is over 100 MB, shorten the range or lower the frame size and run the trim again with a new Idempotency-Key.
curl -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: square-section-clip-001" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4",
"start": 4,
"duration": 10,
"audio": "drop",
"output": { "width": 1280, "height": 720, "fps": 30 }
}'Which setting should a product page use?
For a clip that is the page's main visual, upload a short silent cut with loop on. For a longer demo with talking, keep sound and leave playback to the visitor, or host it on YouTube and use the YouTube source. If you want a still to use as the page's static image or a social preview, video frames returns a JPEG or PNG at the clip's own size.
Sources
Related posts
More in Integrations
- Stripe product images: build a set of 8 with the Sume image API
Stripe's product object holds up to 8 image URLs. Plan a set of eight shots with Sume, price it by model, and host copies you control before you set the field.
- stt_create in a read-only MCP session: insufficient_scope, not a bug
A read-only OAuth session on Sume's MCP server can list tools but paid calls such as stt_create and tts_create return insufficient_scope. What to switch on.
- Sume hosted MCP OAuth scopes: mcp:read, mcp:write, and no paid scope
What a client gets after OAuth consent on https://mcp.sume.com/mcp: mcp:read always, mcp:write opt-in, and an API key for the full tool set.
- Sume MCP with an API key versus OAuth: which tools your AI client sees
Why Claude, Cursor, Codex or Copilot may show fewer Sume tools: OAuth is read-only until consent includes write; an API key shows all.
Written by Sume