Webflow Assets API lists no audio types: where a Sume track goes
Webflow's asset docs name image, document and Lottie types, not audio. Keep the Sume mp3 on its media.sume.com URL and store that link in a CMS Link field.

Do not plan on uploading a Sume music track to the Webflow asset library. The Webflow pages that I read list image, document and Lottie file types and give no audio type, so treat audio as not documented there. The safer pattern is to keep the mp3 on the media.sume.com URL that the job returns and save that link in a Link field of your CMS item.
What the Webflow docs say
Webflow's asset upload is a two-step call: POST /v2/sites/{site_id}/assets with a fileName and an MD5 fileHash, then an upload of the bytes to the storage target in the response. The guide lists the supported asset families and their size limits.
| Topic | Webflow documents |
|---|---|
| Create call | POST /v2/sites/{site_id}/assets, then an upload to the returned target |
| fileName | Under 100 characters |
| fileHash | MD5 of the file |
| Image limit | Up to 4 MB |
| Document limit | Up to 10 MB |
| Types listed | Image, document and Lottie; no audio type is listed |
What a Sume track looks like
A Music Router job returns the audio in result.artifacts[] with type audio, usually audio/mpeg, on media.sume.com. The router costs a fixed $0.125 per generation. Because the file already lives on a public HTTPS URL, you do not need to copy it into Webflow to play it.
Store the link, not the file
Add a Link or plain text field named track_url to the collection, then fill it from the finished job. In the page, bind an HTML embed or a custom code element to that field. Use the audio element of the browser; Webflow does not have to know that the file is audio.
<audio controls preload="none" src="{{wf {"path":"track-url","type":"Link"} }}"></audio>Limits
The link is only as durable as your copy of it. If the track is part of a paid product, download the file from the artifact URL into storage that you control and record the job id beside it. Do not assume that Webflow rejects audio; say that you could not find it documented, and test with a small file on a staging site before you build on it. A custom field binding also needs the site to be published, so check the live page and not only the Designer.
Before you ship
- Save the Sume job id in a hidden CMS field next to the link.
- Test the audio element on the published page, not only the Designer preview.
- Decide whether the track must outlive the source URL; if so, copy the file to storage you own.
- Do not describe audio as unsupported in Webflow; describe it as not listed in the pages you read.
Sources
Related posts
More in Integrations
- WordPress media_handle_sideload for a Sume music mp3 attachment
Download the Sume artifact URL with download_url(), then media_handle_sideload() it into the Media Library. It returns an attachment id or a WP_Error.
- X media upload APPEND: 5 MB chunks, and how to split a Sume MP4
The X API v2 APPEND step takes chunks of at most 5 MB. Count the segments for a Sume MP4 with a short script before you upload to the initialize endpoint.
- X media upload processing_info states: poll until succeeded
After FINALIZE on the X API v2, processing_info moves from pending to in_progress to succeeded or failed. Poll using check_after_secs, then post the Sume video.
- YouTube's Shorts help page says vertical, not 9:16: what to render
YouTube's Shorts help page states 3 minutes, vertical uploads and a 1080p maximum, but names no ratio. Render 1080x1920 with Sume Timeline 1.0 and probe it.
Written by Sume