Kevin MacLeod attribution: credit text and Sume's BGM field
Kevin MacLeod tracks need a CC BY 4.0 credit that is easy to find. Sume's BGM featured beds are his tracks; keep track.attribution with any public use.

Credit a Kevin MacLeod track with the line Incompetech specifies: the title, "Kevin MacLeod (incompetech.com)", "Licensed under Creative Commons: By Attribution 4.0", and the CC BY 4.0 link. Sume's BGM catalog says its featured beds are his tracks and to keep track.attribution with any public use.
Credit wording is from the Incompetech FAQ; the catalog behavior from the Sume OpenAPI description of the BGM catalog, both read 2026-09-30. This is not legal advice.
What credit text does Incompetech require?
The FAQ gives this format, replacing "Title" with the actual title of the piece:
Title Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 4.0
https://creativecommons.org/licenses/by/4.0/Where should the credit go?
The FAQ's test is that "a person who wants to know where the music came from should have no difficulty in finding it." Put it where a viewer would look, such as the description or end card, not buried.
Where does Sume put this?
The BGM catalog returns first-party Sume loops and featured Kevin MacLeod / Incompetech tracks (CC BY 4.0) at their official URLs. The description says to keep track.attribution with any public use. The catalog supports optional category, mood, genre and energy filters, and POST /v1/bgm/pick ties are broken deterministically among top scores. I did not verify the exact content of track.attribution; compare it to the Incompetech format above before you publish.
| Question | Answer | Source |
|---|---|---|
| License | CC BY 4.0 | Incompetech FAQ; Sume catalog text |
| Credit format | Title, name, license line, license URL | Incompetech FAQ |
| Field to keep | track.attribution | Sume catalog text |
What if the pick is a first-party loop?
The Sume text ties the attribution rule to the featured Kevin MacLeod beds. Check each track's track.attribution rather than assuming. For the catalog tour, see the free BGM catalog.
Sources
Related posts
More in Use cases
- Korea AI Basic Act Article 31: labeling an exported AI video
MSIT's guidelines ask for a human-recognizable label when AI video leaves the service. Here is how to burn a visible Korean label onto a clip with cues.
- LinkedIn 30-minute video: build 1800 s with Timeline
LinkedIn's Videos API lists three seconds to 30 minutes. Sume Timeline 1.0 renders up to 1800 s in one MP4 at $0.10 per output minute: 30 minutes is the cap.
- LinkedIn Videos API: 500MB or 5GB? Plan for the lower number
LinkedIn's Videos API page lists a 75kb to 500MB file size and a 5GB maximum. Sume states no output file size, so measure the MP4 first.
- LinkedIn video captions: English SRT only vs burned-in text
LinkedIn's Videos API takes one English caption file, shown with SRT. Sume video-captions burns your cues text into the video and does not accept SRT uploads.
Written by Sume