Carrd video upload: 64 MB and H.264 only, how to prep a Sume clip

Carrd accepts uploaded video up to 64 MB on any Pro plan, and only as H.264 MP4. Make the clip with Sume and use exact trim to re-encode it as H.264.

4 min readSume
All posts

Carrd takes your own video, up to 64 MB, on Pro Lite, Pro Standard and Pro Plus, and the file has to be an MP4 encoded as H.264. A Sume clip cut with video trim in its default exact mode is re-encoded with libx264, so run the clip through trim once and check the size.

Carrd's troubleshooting page names the common failure: an .mp4 extension on a video that is not H.264.

What Carrd says

The rules below are from Carrd's documentation, read 2026-10-10. The Adding videos page says uploads need Pro Lite or higher, and the Pro plans page gives the size.

Carrd video upload rules, read 2026-10-10 from carrd.com/docs
RuleCarrd's wordingSource page
PlanUploading a video requires Pro Lite or higherAdding videos
ContainerThe video must be an MP4Adding videos
CodecThe video must be encoded in H.264Adding videos
SizeVideos up to 64MB (images and GIFs up to 16MB) on all three Pro plansPro plans
WhereThroughout the site, or as its backgroundPro plans
Embeds insteadBilibili, Bunny Stream, Cloudflare Stream, Facebook, Google Drive, Loom, TikTok, Twitch, Vidyard, Vimeo and YouTubeAdding videos
Common errorAn .mp4 file that is not encoded in H.264 is not acceptedTroubleshooting

Why the codec line matters for a generated clip

Sume's video trim page documents that precision exact is a frame-accurate re-encode with libx264 and yuv420p, and that keyframe precision is a stream copy. For Carrd, keep the default exact mode so the output is H.264 by construction, and avoid keyframe, which only copies the source stream. Do not send codec or crf fields: trim rejects them with ffmpeg_fields_rejected.

curl -X POST https://api.sume.com/v1/video-trim \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: carrd-trim-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/clip.mp4",
    "start": 0,
    "duration": 12,
    "precision": "exact",
    "audio": "keep"
  }'

Fit 64 MB

Sume cannot set a bitrate, so you shorten or shrink. Generate a 16:9 or 9:16 clip with the Video Router, where seedance-2.5 accepts 4 to 30 seconds at 480p, 720p or 1080p. Then use trim's output object (width and height 256 to 2160, fps 24, 25, 30 or 60) and drop the audio if the clip is a background.

For scale, 64 MB is 512 megabits if a megabyte is 1,000,000 bytes. Spread over a 20-second clip that is an average of about 25.6 megabits per second; over 60 seconds, about 8.5. Measure the actual download, since the encoder decides the real figure.

  • Generate at 720p first; go to 1080p only if the file still fits.
  • Keep the exact trim pass even when you do not need to cut anything, so the codec is known.
  • Do not delete the local file before you publish; Carrd's troubleshooting page warns that can cause issues with larger videos.
  • If the clip is too long, embed it from Vimeo, YouTube or Bunny Stream, which Carrd lists.

Sources

Related posts

More in Integrations

All Integrations posts

Written by Sume