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.

4 min readSume
All posts

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.

Webflow asset facts (Webflow Developers, read 2026-10-05)
TopicWebflow documents
Create callPOST /v2/sites/{site_id}/assets, then an upload to the returned target
fileNameUnder 100 characters
fileHashMD5 of the file
Image limitUp to 4 MB
Document limitUp to 10 MB
Types listedImage, 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 {&quot;path&quot;:&quot;track-url&quot;,&quot;type&quot;:&quot;Link&quot;} }}"></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

All Integrations posts

Written by Sume