Uppbeat
Uppbeat (uppbeat.io) is a royalty-free music and SFX subscription platform
for content creators, run by the licensing company Music Vine. It is a website
with human-driven search and download — no npm package, no public API, no CLI.
A human browses, previews, downloads an audio file, and (on the free tier)
receives an attribution snippet. What you get is a license to use the track
in your content, never ownership of the file.
This skill owns two things: what the license actually permits per tier
(details and exact figures in references/licensing.md) and integration
restraint — what audio is allowed to do on a web page, and the asset
pipeline when it earns its place (references/pipeline.md).
Licensing in one honest paragraph
As of Aug 2026 (verify at uppbeat.io/pricing before anything invoiced): the
free tier gives 3 downloads/month from roughly a quarter of the catalog,
and every download requires pasting that track's unique Uppbeat Credit
into the description of the one video it clears — monetized personal YouTube
is fine, forgetting the credit means copyright claims. Premium
(~$6.99/month billed yearly) unlocks the catalog, drops attribution, and
safelists your connected channels against Content ID. Client work and paid
advertising are NOT covered by free or Premium — that requires the business
tier. No subscription covers broadcast TV/radio, cinema, or events, and
nothing ever permits redistributing the audio files themselves — which
includes committing raw downloads to a public repo or re-hosting tracks as a
site's downloadable assets. Full tier table, edge cases, and the credit
mechanics: references/licensing.md.
The restraint rules — audio on a launch page
Audio on the web is the autoplay-video problem with less tolerance. The rules,
parallel to how prefers-reduced-motion governs motion:
- Nothing autoplays with sound. Ever. Browsers block it, users hate it,
and it torpedoes the credibility a launch page exists to build.
- Sound is user-initiated and user-terminated. An explicit unmute/play
control, visible state, and it stops when the element leaves the viewport.
- Muted-by-default is the only default. A demo loop is
<video muted loop playsinline autoplay> — the soundtrack exists for the
users who opt in.
- Respect
prefers-reduced-motion as a proxy for sensory restraint — a
user asking for less motion should not get a pulsing equalizer either.
- Music is not polish. If a page "feels flat", the fix is motion,
typography, or content — see motion-primitives, frontend-design,
taste-skill — not a background track. There is no legitimate ambient
soundtrack for a marketing page.
Legitimate uses in a web/launch context
- Product demo videos — a track under a screen-capture walkthrough,
mixed low (dialog/VO −6 to −12 LUFS above music).
- Launch trailers — published to YouTube/socials, embedded on the page.
- Recorded walkthroughs and tutorials — consistent bed music across a
series reads as production value; pick one artist/mood and stay there.
- Podcast intros/beds — podcasts are a permitted medium.
- SFX in produced video — whooshes and UI clicks inside a video. Not
sitewide UI sounds on the page itself; the web stopped doing that for a
reason.
The pipeline for all of these — download, loudness-normalize, compress, mux
into the video, embed with the right attributes, weight budgets — is in
references/pipeline.md.
When not to use Uppbeat
- Paid ad campaigns or client deliverables on a personal tier — that's a
license breach with a client's name on it. Upgrade tier or use properly
licensed commissioned music.
- Broadcast, cinema, events — outside every Uppbeat subscription; Music
Vine sells those licenses separately.
- When silence works. Most launch pages ship zero audio and lose nothing.
- Music as a product feature (meditation app beds, game soundtracks
shipped in-app): "online games or applications" appear in permitted media,
but shipping extractable audio files inside an app edges into
redistribution — read
references/licensing.md and when in doubt ask
Uppbeat support in writing.
- AI training or audio remix/resale of any kind — redistribution, never
allowed.
Anti-patterns
- Committing downloaded
.wav/.mp3 masters to a git repo (public repo =
redistribution; any repo = bloat — keep sources in asset storage, ship only
the compressed, muxed output).
- Hotlinking Uppbeat's CDN URLs instead of self-hosting your licensed,
compressed derivative inside your content.
- Free-tier track in a video, credit line forgotten — the claim lands on the
client's channel, not yours.
- An unmuted
autoplay attribute anywhere. Browsers will block it and the
fallback behavior differs per engine; design for muted-first instead.
- Swapping tracks per section of one video/page: one bed, one mood — see
the selection notes in
references/pipeline.md.
1---2name: uppbeat3description: Uppbeat4---56# Uppbeat78Uppbeat (uppbeat.io) is a **royalty-free music and SFX subscription platform**9for content creators, run by the licensing company Music Vine. It is a website10with human-driven search and download — no npm package, no public API, no CLI.11A human browses, previews, downloads an audio file, and (on the free tier)12receives an attribution snippet. What you get is a **license to use the track13in your content**, never ownership of the file.1415This skill owns two things: **what the license actually permits per tier**16(details and exact figures in `references/licensing.md`) and **integration17restraint** — what audio is allowed to do on a web page, and the asset18pipeline when it earns its place (`references/pipeline.md`).1920## Licensing in one honest paragraph2122As of Aug 2026 (verify at uppbeat.io/pricing before anything invoiced): the23**free tier** gives 3 downloads/month from roughly a quarter of the catalog,24and every download requires pasting that track's unique **Uppbeat Credit**25into the description of the one video it clears — monetized personal YouTube26is fine, forgetting the credit means copyright claims. **Premium**27(~$6.99/month billed yearly) unlocks the catalog, drops attribution, and28safelists your connected channels against Content ID. **Client work and paid29advertising are NOT covered by free or Premium** — that requires the business30tier. **No subscription covers broadcast TV/radio, cinema, or events**, and31**nothing ever permits redistributing the audio files themselves** — which32includes committing raw downloads to a public repo or re-hosting tracks as a33site's downloadable assets. Full tier table, edge cases, and the credit34mechanics: `references/licensing.md`.3536## The restraint rules — audio on a launch page3738Audio on the web is the autoplay-video problem with less tolerance. The rules,39parallel to how `prefers-reduced-motion` governs motion:40411. **Nothing autoplays with sound. Ever.** Browsers block it, users hate it,42 and it torpedoes the credibility a launch page exists to build.432. **Sound is user-initiated and user-terminated.** An explicit unmute/play44 control, visible state, and it stops when the element leaves the viewport.453. **Muted-by-default is the only default.** A demo loop is46 `<video muted loop playsinline autoplay>` — the soundtrack exists for the47 users who opt in.484. **Respect `prefers-reduced-motion` as a proxy for sensory restraint** — a49 user asking for less motion should not get a pulsing equalizer either.505. **Music is not polish.** If a page "feels flat", the fix is motion,51 typography, or content — see **motion-primitives**, **frontend-design**,52 **taste-skill** — not a background track. There is no legitimate ambient53 soundtrack for a marketing page.5455## Legitimate uses in a web/launch context5657- **Product demo videos** — a track under a screen-capture walkthrough,58 mixed low (dialog/VO −6 to −12 LUFS above music).59- **Launch trailers** — published to YouTube/socials, embedded on the page.60- **Recorded walkthroughs and tutorials** — consistent bed music across a61 series reads as production value; pick one artist/mood and stay there.62- **Podcast intros/beds** — podcasts are a permitted medium.63- **SFX in produced video** — whooshes and UI clicks inside a *video*. Not64 sitewide UI sounds on the page itself; the web stopped doing that for a65 reason.6667The pipeline for all of these — download, loudness-normalize, compress, mux68into the video, embed with the right attributes, weight budgets — is in69`references/pipeline.md`.7071## When not to use Uppbeat7273- **Paid ad campaigns or client deliverables on a personal tier** — that's a74 license breach with a client's name on it. Upgrade tier or use properly75 licensed commissioned music.76- **Broadcast, cinema, events** — outside every Uppbeat subscription; Music77 Vine sells those licenses separately.78- **When silence works.** Most launch pages ship zero audio and lose nothing.79- **Music as a product feature** (meditation app beds, game soundtracks80 shipped in-app): "online games or applications" appear in permitted media,81 but shipping extractable audio files inside an app edges into82 redistribution — read `references/licensing.md` and when in doubt ask83 Uppbeat support in writing.84- **AI training or audio remix/resale of any kind** — redistribution, never85 allowed.8687## Anti-patterns8889- Committing downloaded `.wav`/`.mp3` masters to a git repo (public repo =90 redistribution; any repo = bloat — keep sources in asset storage, ship only91 the compressed, muxed output).92- Hotlinking Uppbeat's CDN URLs instead of self-hosting your licensed,93 compressed derivative inside your content.94- Free-tier track in a video, credit line forgotten — the claim lands on the95 client's channel, not yours.96- An unmuted `autoplay` attribute anywhere. Browsers will block it and the97 fallback behavior differs per engine; design for muted-first instead.98- Swapping tracks per section of one video/page: one bed, one mood — see99 the selection notes in `references/pipeline.md`.