Why background music decides how long people watch
Most viewers now meet your video in a hostile environment: a phone held at an angle, sound off, competing with a group chat and a passing bus. The visuals have to earn the first three seconds on their own. But the moment someone taps the speaker icon, the music takes over the job of holding them there. It sets the emotional frame, tells the viewer what kind of story this is, and smooths the small imperfections of a cut that would otherwise feel jumpy.
Editors notice this in retention graphs constantly. The drop-offs cluster around moments where the audio stops changing — a long talking-head stretch with a single looping bed, a transition where the music cuts abruptly instead of resolving, a section where the track's energy contradicts what is happening on screen. The picture is usually fine. The sound is what quietly lost the audience.
That is why treating background music as an afterthought — a file you drop in at the end and nudge until it "feels okay" — costs you more than it saves. A deliberate sound workflow, whether you are pulling from a library, commissioning a composer, or generating tracks with an AI music tool, produces a video that feels intentional. This guide walks through that full workflow: sourcing, briefing, prompting, editing to picture, mixing, and keeping the legal side clean.
Three ways to source music, and when each one wins
Before you open any tool, decide which sourcing model fits the project. Each has a different cost structure, timeline, and ceiling on quality.
Licensed music libraries
Libraries are the default for most creators. You search by mood, genre, tempo, and duration, preview a few candidates, and download. The advantages are speed and predictability: the track exists, the license terms are written down, and you know what you are getting before you commit.
The limitation is that everyone else is searching the same catalog. If a track is the obvious choice for a product launch montage, thousands of other videos have already made the same choice. You also inherit the track's structure. A library cue might be three minutes long with a two-minute build, while your video is 48 seconds and needs the payoff immediately.
Use libraries when you need volume, when the music is genuinely background, or when a client requires a documented license from an established catalog.
Commissioned or custom composition
A composer writes something for your specific edit. This is the highest-ceiling option: the track can hit your exact duration, land a musical accent on the exact frame where the logo appears, and use instrumentation that matches your brand. It is also the slowest and most expensive, and it introduces a revision cycle into your timeline.
Use custom composition for brand films, title sequences, trailers, and anything where the music is the point rather than the backdrop.
AI music generation
AI music tools sit between the two. You describe what you want in text, get candidate tracks in seconds to minutes, and iterate. The practical advantages are speed, specificity, and the ability to generate variants until something fits — a luxuries libraries cannot offer, because you are not limited to what already exists.
The trade-off is that you must be specific in your prompt and ruthless in your selection. Vague input produces generic output, which is the same problem as picking the obvious library track. Used well, generation lets you build a track shaped around your edit rather than bending your edit around a track.
A sensible rule: generate for specificity, license for speed, commission for prestige.
Write a sound brief before you touch a tool
Every weak soundtrack traces back to a vague brief. "Something upbeat and inspiring" describes half the music ever recorded. Spend five minutes answering these questions and your search or prompt gets dramatically better.
Mood, era, and instrumentation
Name the emotional target in one sentence: curious and calm, tense but hopeful, playful and slightly retro. Then specify instrumentation. Piano and muted strings read differently from synth pads and fingerpicked guitar, even at the same tempo and energy level. If your video has a period setting, say so — an analog synth will break a scene set decades before it existed.
Reference tracks
Pick two references: one commercial track that captures the feeling you want, and one track you have used before that worked. Describe what you like about each without naming it in your prompt — "a sparse, slowly arpeggiating synth bed with almost no percussion and a warm low end" is usable instruction. A bare song title usually is not.
Hard constraints
Write down the things that are not negotiable:
- Target duration, plus how long you can tolerate a tail
- Whether the track must loop seamlessly
- Whether you need stems (separated drums, bass, melody, and pads) or a finished stereo mix
- Whether vocals are allowed, and if not, whether vocal-like textures are acceptable
- Loudness expectations for the destination platform
Stems are the single most underrated item on this list. Having separate elements means you can drop the drums during dialogue and bring them back for the payoff, which is the difference between "music playing under a video" and "a soundtrack"
Prompting an AI music generator like an editor
The best prompts read like notes from a director, not like a genre tag. Compare these two:
Weak: "upbeat corporate background music"
Strong: "warm minimal electronic bed, 92 BPM, soft analog pad, light shaker, no drums in the first 20 seconds, gentle build from 20 to 45 seconds, clean ending, no vocals, sparse enough for voiceover"
The second version tells the tool about tempo, arrangement over time, energy curve, and mix density. That last part matters most: background music fails when it is too busy, not when it is too simple.
Describe structure, not just style
Music has an arc. If you want a track that works under a 60-second explainer, describe the arc explicitly — a quiet opening, a lift at the point where you introduce the problem, a fuller middle, and a resolved ending. Many tools respond well to time-based language.
Generate in small batches and compare blind
Generate four to six candidates, then listen without looking at which prompt produced which. Judge on three criteria only: does it leave room for the voice, does the energy match the edit, and does the ending resolve cleanly. Delete the rest immediately so you do not waste time relitigating.
Ask for stems on the finalist
Once you have a winner, regenerate or export with stems if the tool supports it. Even if you end up using the stereo mix, having the separated elements lets you fix problems later without going back to the generator.
Matching music to the cut: tempo, key, and hit points
A track that sounds great on its own can fall flat against picture. The fix is usually structural, not musical.
Map the beat and place your markers
Find the tempo of your track and mark the downbeats on your timeline. Then look at where your visual cuts fall. If your cuts land consistently between beats, the edit will feel like it is fighting the music. Nudging a cut by two frames onto a downbeat usually fixes the whole sequence. You do not have to cut on every beat — that gets monotonous — but the important cuts, the ones that change location or subject, should relate to the pulse.
Use transitions as musical events
Risers, sweeps, and brief silences are your punctuation. A quick swell under a scene change, or half a second of near-silence before a reveal, does more for perceived production value than any visual effect. If your generated track lacks these moments, build them: layer a short whoosh under a transition, or simply automate the volume down and back up across a cut.
Treat silence as an instrument
The most common beginner mistake is running music for 100% of the runtime. Drop it out entirely for a key line of dialogue or a striking visual. When the music returns, it feels new again. Even a two-second gap resets the viewer's attention.
Respect the loop points
If you are using a shorter track under a longer video, loop it at a natural phrase boundary rather than wherever the audio file happens to end. Looping mid-phrase produces an audible hiccup that viewers may not name but will feel as amateurish.
Mixing music under dialogue and voiceover
This is where most videos are won or lost. Speech intelligibility beats musical impact every time — nobody has ever abandoned a video because the music was too quiet, but plenty have abandoned one because they could not hear the narrator.
Levels and ducking
Start conservative: dialogue around -12 to -6 dBFS on peaks, music sitting 15 to 20 dB below that in the same frequency range. Use sidechain ducking or manual volume automation so the music dips 3 to 6 dB under speech and recovers smoothly, with attack around 10 to 30 ms and release between 200 and 500 ms. Slow releases sound natural; fast ones sound like the music is being yanked.
Carve the frequency range
Even at correct levels, music and voice compete because they share the midrange. A gentle EQ cut of 2 to 4 dB in the music track between roughly 1 kHz and 4 kHz makes the vocal sit forward without turning the music down further. If your voice track sounds thin or harsh, high-pass it around 80 to 100 Hz and use a light de-esser rather than boosting the high end.
Watch the low end
Bass eats headroom fast, especially on phone speakers where it is barely reproduced but still triggers limiting. If the mix sounds muddy on earbuds, high-pass the music around 30 to 40 Hz and check that kick and bass are not fighting the narrator's chest tone.
Hit sensible loudness targets
Most social platforms normalize playback. Aim for roughly -14 LUFS integrated for streaming destinations and around -16 to -14 LUFS for short-form vertical video, with true peaks below -1 dBTP. If you deliver far louder, the platform turns you down and your carefully built dynamics get squashed anyway.
Check on real devices
Mix on headphones, then verify on a phone speaker and a laptop. Three passes across those three outputs catch more problems than an hour of staring at meters.
Copyright, licensing, and monetization hygiene
Audio claims are one of the fastest ways to lose revenue on a video you spent days producing. A little hygiene prevents almost all of it.
Understand what your license actually permits
"Royalty-free" describes a payment model, not a permission set. Read the specific terms and check three things: whether commercial use is allowed, whether you can use the track in paid advertising, and whether monetized distribution on video platforms is covered. Some catalogs restrict one or more of these, and the restriction often applies per project or per channel.
Know how AI-generated audio is treated
Rules vary by platform and by the tool you used. Many generators grant broad usage rights to output, but some require attribution or restrict redistribution of the audio as a standalone product. Keep a short note per track: which tool produced it, the date, the prompt, and a link to the terms at the time. If a claim ever lands on your video, that note resolves it in minutes instead of weeks.
Avoid the obvious traps
Do not pull a commercial song from a video platform and use it as a bed, even for a private client draft. Do not use a track you found in a free download folder that came with no documentation. And be careful with tracks that imitate a well-known song too closely — that is a different kind of risk than a straightforward license problem.
Keep a consistent naming convention
Name audio files with the project, the source, and the track identifier: project-name_source_trackid_v2.wav. When you revisit a project months later, you will know exactly where the music came from.
A repeatable end-to-end workflow
Here is a sequence that works for explainers, product videos, documentaries, and short-form vertical content with only minor adjustments.
- Lock the picture first. Edit the visuals to a rough length before you choose music. Cutting to a track you have not chosen yet is how you end up with a video that only works with one specific song.
- Write the sound brief. One paragraph covering mood, instrumentation, tempo, duration, stems, and vocal policy.
- Shortlist three options. One library track, one generated track, one wildcard. Listen to all three against a muted playback of your video.
- Pick on fit, not taste. The track that lets the voice breathe and resolves cleanly at the end usually beats the more interesting track that fights the edit.
- Lay the bed and mark the beats. Place the track, mark downbeats, and adjust key cuts so the important ones land on the pulse.
- Automate the drama. Duck under speech, drop out for the key line, and build a swell into the turning point.
- Mix, then check on three playback systems. Headphones, phone speaker, laptop. Fix what breaks.
- Export with the correct loudness target and log the license. Two minutes of paperwork now prevents a claim later.
Common mistakes that make a soundtrack feel amateur
- Music that never stops. Constant beds fatigue the ear. Plan gaps.
- Energy that contradicts the picture. High-energy music under a somber sequence reads as a mistake, not a creative choice.
- Abrupt endings. Fading out in the middle of a phrase sounds unfinished. Fade on a phrase boundary, or better, end on a resolved chord.
- Ignoring the first three seconds. If the music starts at full intensity, there is nowhere to go. Start smaller than you think you should.
- Mixing only on headphones. Phone speakers reveal problems that headphones hide.
- Using the first result. The first generated track is rarely the best one; the third or fourth usually is.
- No license record. This one only hurts once, and it hurts badly.
Frequently asked questions
How do I find the tempo of a track?
Use a tap-tempo tool in your editor, or count beats over 15 seconds and multiply by four. Once you have the number, convert it to frames per beat at your project frame rate so you can place markers precisely.
Should I use one track or several?
For videos under 90 seconds, one track with automation is usually stronger because it feels continuous. For longer content, two or three tracks with clear transitions between sections help reset attention — but keep the instrumentation related so it still feels like one world.
Can I use AI-generated music in client work?
Usually yes, but confirm two things: that the tool's terms permit commercial use, and that your client's contract does not require a specific provenance. When in doubt, disclose the source of the audio in your delivery notes.
What if my track is the right mood but too busy?
Ask for stems and remove the percussion, or high-pass and low-pass the track to thin it out, cutting above roughly 8 kHz and below 120 Hz before applying your ducking. A thinner bed is almost always more usable.
How loud should the music be relative to the voice?
Quiet enough that every word is clear on a phone speaker with the volume at 50%. If you have to concentrate to follow speech, the bed is too loud — regardless of how good it sounds on headphones.
Do I need to worry about music in silent-autoplay feeds?
You should still plan for it. Many viewers watch muted at first, so your on-screen text and visual pacing must carry the opening. Music becomes the payoff for the people who turn sound on, not the load-bearing element for everyone.
Where to start today
The fastest improvement most creators can make is not a better tool — it is a better process. Pick the next video on your list and run it through the eight-step sequence above. Write the brief before you listen to anything. Generate or shortlist candidates against a muted playback. Duck under the voice, drop out for the key line, and check the mix on a phone speaker before you export.
Do that twice and it stops feeling like extra work. The music stops being a file you tolerate and starts being the part of the video that tells viewers how to feel — which is exactly the job it was hired to do.


