I'm having an issue where my video looks smooth on my computer, but after uploading it to YouTube, it seems to have small stutters or dropped frames. It's subtle, but about every quarter of a second there's a slight hitch, which is really noticeable for the type of content I'm making.
The original exported file plays perfectly on my PC, so the issue only appears on YouTube.
I've read that it could be related to bitrate, frame rate, or file type, but I've tried different suggestions and nothing seems to fix it.
Here are my export settings:
- Frame rate: 60 FPS
- Bitrate: 40 Mbps
- Format: MP4
I'm also using the latest free version of CapCut for PC.
Is this a YouTube encoding issue, or is there something I should be changing in my export settings before uploading? Any advice would be appreciated.
Hi,
If the exported file is genuinely smooth on your computer, then the most likely culprit is YouTube's re-encoding, not CapCut itself.
However, there are a few things worth checking because subtle stutters can also come from frame rate mismatches.
Here are the most common causes:
1. Wait for YouTube's HD/VP9 or AV1 processing
When you first upload a video, YouTube serves a lower-quality encode that may have poorer motion quality. Even after the video becomes available in HD, higher-quality encodes (VP9 or AV1) can take much longer, especially for 1080p videos.
Check:
-
Wait several hours (or even overnight).
-
View the video at 1080p60.
-
Right-click the video → Stats for Nerds.
-
See what codec you're getting:
-
av01orvp09= generally better -
avc1= older codec that can show more compression artifacts
-
2. Make sure your timeline and export frame rates match
A common issue is editing on a 30 FPS timeline and exporting at 60 FPS. This creates duplicate frames that can look like a tiny hitch every few frames.
Verify:
-
Source footage frame rate
-
CapCut timeline frame rate
-
Export frame rate
These should ideally all be the same:
-
60 → 60 → 60
-
or 30 → 30 → 30
Avoid converting 30 FPS footage into 60 FPS unless you're using proper frame interpolation.
3. Check if your source footage is variable frame rate (VFR)
Many phones and screen recorders record using variable frame rate.
CapCut usually handles it reasonably well, but YouTube's encoder can expose timing inconsistencies.
If your source is VFR:
-
Convert it to constant frame rate (CFR) before editing, or
-
Export through a tool like HandBrake with Constant Framerate enabled before uploading.
4. 40 Mbps is already plenty
For 1080p60, 40 Mbps is more than enough.
Increasing bitrate beyond this usually won't reduce stutter because YouTube re-encodes everything.
5. Export with H.264 High Profile
Recommended settings:
-
Format: MP4
-
Codec: H.264
-
Profile: High
-
Frame rate: 60 FPS (constant)
-
Bitrate: 25–50 Mbps
-
Keyframe interval: 2 seconds (if adjustable)
-
Audio: AAC 48 kHz
6. Try uploading at 1440p or 4K
Many creators intentionally upscale:
-
1080p → 1440p
This often causes YouTube to use the VP9 codec instead of AVC, which generally preserves motion better.
It doesn't add detail, but it can noticeably improve the quality after YouTube's compression.
7. Make sure the stutter isn't your browser
Sometimes the issue is playback rather than the upload.
Test:
-
Chrome vs. Firefox vs. Edge
-
Hardware acceleration on/off
-
Another device (phone, tablet, TV)
If the stutter only appears in one browser, it's likely a playback issue rather than an encoding problem.
A few questions that would help narrow it down
-
Is your source footage 60 FPS, or are you converting 30 FPS footage to 60 FPS?
-
Is this a screen recording, gameplay, or camera footage?
-
Does the stutter appear in every browser and on your phone, or only on your PC?
-
What resolution are you uploading—1080p60, 1440p60, or 4K60?
-
When you check Stats for Nerds, what codec does it show (
avc1,vp09, orav01)?
The pattern you describe a tiny hitch roughly every quarter of a second is particularly suggestive of a frame rate mismatch (for example, 24→60 or 30→60 conversion) or a variable frame rate source, rather than bitrate alone.
If your source, timeline, and export are all true constant 60 FPS and the uploaded file is still smooth locally, then YouTube's initial encode or codec choice becomes the most likely explanation.