CapCut Auto Velocity “No Beats Detected”? How to Fix It

You pick an Auto Velocity style, CapCut starts looking for the music, and then it tells you “No beats detected.” Your edit is stuck even though the song clearly has a steady rhythm.

Here is the honest starting point: CapCut does not appear to publish a dedicated help article explaining the exact “No beats detected” message. Its official velocity guidance explains the basic workflow and says that sound is required for the effect, but it does not identify every reason beat analysis can fail.

Instead of guessing at a magic fix, this guide gives you a simple way to find out what is actually failing in your project: the song, the way it was added, the app, or the feature itself. If Auto Velocity still will not cooperate, you can also build a similar beat-synced effect by hand, which may give you better control.

First, what Auto Velocity actually needs

This part trips up a lot of people. In CapCut’s mobile app, select the video clip and look for Style, Velocity, or a similar speed-effect option. The exact label and location can vary by app version, region, and account.

CapCut’s official velocity guide describes Velocity as a mobile editing workflow and notes that sound is required for the effect. Depending on your version, you may be able to choose a velocity style and wait for CapCut to analyse the music.

This tells us two useful things:

Auto Velocity depends on sound in your project. No music, or music that CapCut cannot analyse, means there may be no beats available for the effect.
CapCut’s official velocity guide documents the manual Speed > Curve workflow for desktop and web rather than confirming the same Auto Velocity control there. If Auto Velocity is missing on your computer, use a custom speed curve or check whether your version provides the feature.

Four tools that people mix up

Tool	What it does	Why it matters here
Auto Velocity	Applies a styled speed effect that may be timed to the music.	This is the feature showing the error.
Beat detection or Auto Beat	Places beat markers on your audio.	It can be used as a practical test, although it may not use exactly the same analysis system as Auto Velocity.
Speed Curve	Lets you set speed changes yourself, point by point.	It is your manual backup option.
Auto Cut	Automatically arranges or cuts clips to music.	It is a separate feature, so an Auto Cut error does not necessarily indicate the same problem as a “No beats detected” Velocity error.

Why CapCut might not find beats

CapCut does not appear to document every cause of this message. The points below are realistic suspects based on how the feature is used and what editors commonly encounter. Treat them as things to test, not as proven CapCut requirements.

The audio is missing, silent, or not really music. Voiceovers, ambient sound, and muted clips may not provide a clear rhythm for beat analysis.
The track has a weak or unclear beat. Soft intros, slow sections, ambient parts, or heavy vocals can be harder to analyse. Songs with clear rhythmic accents are generally easier to test because the beat is easier to hear and mark manually. This is a practical troubleshooting assumption, not a published CapCut requirement.
You trimmed the song to a quiet section. If your project only covers an intro or breakdown, there may be few strong rhythmic moments in that section.
The file was added in an unusual way. Extracted audio, converted files, and other imported versions may behave differently from a regular playable audio file.
The app version or feature rollout is involved. Features can vary by app version, account, and region. An option may also behave differently during a phased rollout.
A temporary project or analysis glitch is involved. The feature may fail in one project but work in a new project with the same or similar audio.

Step 1: Find out whether it is one track or every track

This is one of the most useful tests, and it takes about two minutes.

Open a new, blank project.
Add one short video clip.
Add a song from CapCut’s own music library with clear rhythmic accents, such as a punchy pop or hip-hop track.
Look for Auto Velocity through the available Style, Velocity, or speed-effect controls.
Try applying the effect again.

Now read your result:

What happens	What it probably means	Next move
It works with the library song but fails with your song.	Your song or the way it was imported may be the problem.	Go to Step 2 and check the audio.
It fails with every song, including library music.	The app, version, account, region, project, or feature may be involved.	Check the app version and test again in a fresh project.
It works in the new project but not in your old one.	Something in the old project may be interfering with the feature.	Rebuild the edit in a fresh project or copy the clips into a new project.
It works on one song section but not another.	The beat in the failing section may be too weak or unclear for this test.	Move the audio to a section with stronger rhythmic accents.

Step 2: Check the audio import and your CapCut version

Check the audio

Make sure the song is on the timeline as its own audio layer. Do not rely only on audio embedded inside a video clip. A separate audio track makes the music easier to check, move, and test, although CapCut’s exact analysis behaviour may vary by version.
Play the audio and check the volume. A silent or nearly silent track may not provide useful information for beat analysis.
Choose a section with a clear rhythm. If your clip sits over a soft intro, move the song so the edit covers a stronger drum or rhythm section.
Try another version of the song. A full studio version may be easier to test than a slowed, sped-up, reverb, or heavily edited remix.
Re-import the file. Delete the audio from the timeline, import it again, and retry.
Test a standard playable file if necessary. If the original audio came from a screen recording, conversion tool, or extraction process, try a standard MP3 or M4A file. This is a troubleshooting test, not a guarantee that every file in that format will work.

Check the app

Update CapCut from the App Store or Google Play, then reopen the app.
Confirm which preset you selected. Some velocity styles may be paid, unavailable, or restricted in your version. A locked or unavailable style can fail for reasons unrelated to your music.
Confirm the clip type. Test with a normal video clip. Still images, templates, and other special items may show different controls.
Test your connection if CapCut is loading an online asset, template, or account-based feature. Switch between Wi-Fi and mobile data and retry. A network change can help identify whether the problem is local connectivity or the project itself.

One more thing: if the message you see is “Too many people are using this feature” rather than “No beats detected,” that is a different problem with a different fix. See our guide on the CapCut “too many people are using this feature” error.

Step 3: Test after every single change

The reason people often fail to identify the cause is that they change five things at once. Do this instead:

Change one thing, such as updating the app.
Test Auto Velocity immediately.
Write down the result.
Only then change the next thing.

A useful order is:

Test a CapCut library song in a new project.
Re-import your own song.
Move the song to a stronger rhythmic section.
Update the app.
Test again in a new project.

Save heavier options, such as clearing app data or reinstalling CapCut, for last.

Before clearing app data or reinstalling CapCut: export important videos and back up any drafts you cannot recreate. Projects saved only on your device may not be recoverable after app data is deleted.

The smart shortcut: test beat detection on its own

CapCut may provide a separate beat tool that lets you check or mark the rhythm of an audio track. Depending on your version and platform, select the audio track and look for options such as Beats, Auto Beat, Add beat, or Beats detection.

Some versions may show an option for adding a marker at the playhead and another option for detecting beats automatically. The exact menu name and icon can vary by CapCut version.

If Auto Beat finds beats but Auto Velocity does not: your audio may be usable, and the problem may be related to the velocity feature, the selected style, your project, or your app version.
If Auto Beat also fails on the same track: the audio becomes a stronger suspect. However, the two tools may not use exactly the same analysis system, so this test is a clue, not proof.

Plan B: Mark the beats yourself

Manual beat markers do not depend on CapCut detecting the beats for you, so they are a useful fallback when Auto Beat or Auto Velocity fails. Their exact menu name may vary by CapCut version.

Add your song and select the audio track.
Play the song and place the playhead where a strong beat or musical moment lands.
Tap Add beat, or use the equivalent manual marker option in your version.
Repeat for the beats you care about. You do not need every beat; mark the moments that will start or end a speed change.

Tips that save time

Zoom in on the timeline so you can inspect the audio waveform more easily.
Waveform peaks can help you locate strong musical moments, but they do not always represent the exact beat. A loud vocal or sound effect can create a peak too.
Use your ears and playback to fine-tune each marker.
Mark the big moments first, such as a drop, snare hit, transition, or strong action.
Play the edit back with sound on. If a marker feels late, move it slightly.

Plan C: Build the velocity edit manually with Speed Curve

Even if Auto Velocity never works for you, a manual speed curve can create a similar beat-synced velocity effect while giving you more control over exactly where the slowdowns and speed-ups occur. It may not reproduce the exact preset styling, transitions, or automated timing of Auto Velocity.

On the phone

Tap your video clip.
Go to Edit > Speed > Curve > Custom, or look for the equivalent curve controls in your version.
Tap the curve to add points.
Drag a point up to speed up and down to slow down.
Preview the result, adjust the points, and confirm.

On desktop

Click the clip, open the Speed tab, and choose Curve.
Pick a preset such as Montage, or choose Customized to edit the curve yourself.
In the speed-curve graph, points above the normal-speed line make the clip faster and points below it make the clip slower.
The available speed range can vary by platform and app version.
Use Smooth slow mo if the slowed section looks choppy and the option is available.

On CapCut Web

Select the clip, then open Speed > Curve > Custom, or use the equivalent curve option shown in your version.

How to line the curve up with your beats

Find the moment in your clip that deserves attention, such as a jump, hit, turn, or camera movement.
Place a curve point so the slowest moment lands on that action.
Use the nearest beat marker to start the speed-up or end the slow-down.
Spread the points apart slightly. Points placed too close together can create a jerky snap instead of a smooth ramp.

CapCut’s speed-curve guidance recommends placing speed changes in relation to the rhythm of the music. In practice, the best result is often achieved when the action lands on the beat rather than forcing every cut or speed change to snap exactly to it. A small offset can feel more natural.

Common mistakes that make a manual velocity edit look bad

Too many points. Four or five purposeful points usually work better than a row of tiny adjustments.
Slowing down footage with too few frames. Extreme slow motion on ordinary footage can look choppy. Use a smaller slowdown or enable Smooth slow mo if available.
Putting the slow point on the wrong thing. The slowest moment should highlight the action, not simply the nearest drum hit.
Ignoring the rhythm of the action. A speed change can be close to the beat without landing directly on it.
Judging only by the preview. Phone previews can stutter. Export a short test before rebuilding a curve that may already be acceptable.

Does this depend on my phone?

The basic workflow is similar on iPhone and Android, but button names and menu placement can differ between versions.

CapCut’s available controls can also vary by app version, account, and region. If someone else has an option that you do not see, the feature may not have reached your account or version yet. Nothing in the available CapCut guidance establishes a specific phone-model requirement for this error.

Frequently asked questions

Why does CapCut say “No beats detected”?

CapCut does not appear to publish a dedicated explanation for this exact message. Possible causes include missing or quiet audio, a track with an unclear rhythm, a trimmed section with few strong beats, an unusual file, a project issue, or an app or feature problem. The tests above help you narrow down which category is most likely.

Why does it work with one song but not another?

Songs with clear rhythmic accents are generally easier to test than ambient, slow, or vocal-heavy tracks. A slowed, sped-up, reverb, or heavily edited version may also have a less obvious rhythm than the original.

Can I make a velocity edit without automatic beat detection?

Yes. Add beat markers manually if the option is available, then build a custom speed curve. It takes a little longer but gives you control over where the slowdowns and speed-ups occur.

Does Auto Velocity work on PC and web?

CapCut’s official velocity guidance documents the manual Speed Curve workflow for desktop and web rather than confirming the same Auto Velocity control there. If Auto Velocity is missing on your computer, use a custom speed curve or check whether your version provides the feature.

Do beat markers change my clip’s speed automatically?

No. Beat markers only show where you believe the beats or musical moments occur. You still need to set the speed changes yourself.

Will reinstalling CapCut fix it?

Sometimes, but it should be your last step. Reinstalling will not help if the problem is caused by your audio, the selected style, or a project issue. Before clearing app data or reinstalling, export important videos and back up drafts that you cannot recreate.

Can CapCut detect beats from a voice recording?

A voice recording may not have a steady musical rhythm, so automatic beat detection may not produce useful results. Use music with clearer rhythmic accents or place markers manually if the feature is available.

The short version

Do not start by reinstalling CapCut. First, test a clear library song in a new project to see whether the problem is your audio, project, or app. Then check the audio import, move the song to a stronger rhythmic section, update CapCut, and retest after each change.

You can also try Auto Beat as a diagnostic clue, while remembering that it may not use the same analysis system as Auto Velocity. If automatic tools still fail, mark the important beats yourself and build a custom speed curve. That will not necessarily reproduce the exact Auto Velocity preset, but it can create a similar effect with more control over the final edit.

CapCut Auto Velocity “No Beats Detected”: How to Fix It and Finish Your Edit Anyway