Why Is My Exported Video Bigger Than the Original? 5 Fixes

Short answer: an export is not a copy. Your editor decodes the clip and builds a brand new video, and the size of that new file depends on the bitrate you chose, not on the size of the original. Phone videos are often squeezed hard by the camera app. If your export setting asks for more data per second than the original had, the file grows, and the picture does not get any better. Pick a lower bitrate, or use a quality-based setting (CRF) in a tool like HandBrake or ffmpeg, and the file shrinks.

This question comes up again and again on r/CapCut and the Blackmagic forum. A person cuts half the clip away, exports, and the file is three times bigger. The replies are mostly "lower the bitrate" with no number. Here I give numbers, and a small test I ran myself.

CapCut help page titled Why Does the Video Quality Change After Exporting
CapCut’s own help page treats export settings as the thing that decides what you get.

Why does the file grow?

Think of bitrate as the amount of data the file spends on each second of video. File size is roughly bitrate times length. So if you trim a 10 minute clip to 5 minutes and keep the same bitrate, the file should be half. It becomes bigger only when the new bitrate is higher than the old one.

Here is the part many beginners miss. A phone camera has to record in real time with a small chip, so it does not compress as cleverly as a computer can. Still, many phones record at a modest bitrate to save space, especially in 1080p. Then your editor, with its "Recommended" or "High" preset, may pick a bitrate that was chosen for safe quality on any footage. That number can be far above what your clip had. More data is written, but the extra data only describes the same pixels again. You pay in storage and get no gain.

What I tested

I made a 20 second 720p test clip with some noise, encoded it at a low quality so it was small, then re-encoded it five ways with ffmpeg. This is a synthetic clip, so treat the ratios as a picture of the idea, not as numbers for your own video.

Export settingFile sizeCompared with source
Source clip (CRF 31)3.2 MB1x
Fixed 20,000 kbps47.8 MBabout 15x bigger
Fixed 8,000 kbps20.7 MBabout 6.5x bigger
CRF 236.1 MBabout 1.9x bigger
CRF 303.4 MBabout the same
CRF 362.0 MBsmaller
Same clip, same audio copied, only the video setting changed.

Notice what happened. A fixed bitrate of 20,000 kbps made a file fifteen times bigger. That is the same effect people see when an editor uses a big preset on a lightly compressed phone clip. The CRF settings did not blow up, because CRF asks for a quality level, and the encoder decides how many bits it needs.

Rule of thumb

Before you export, check the bitrate of your original. If the original is 10 Mbps and you export at 40 Mbps, expect a file about four times bigger. Choose a number near the original, or a little lower, and test.

How to find out the original bitrate

You need one number from your source video. Any of these ways works.

  1. On a Windows PC, right click the video, choose Properties, open the Details tab and read Data rate.
  2. On an Android phone, open the file in your Files app or Gallery, tap the three dots, choose Details. Some gallery apps show size and resolution but not bitrate, so use the PC way or ffprobe if it is missing.
  3. With ffprobe, which comes with ffmpeg, run the command below. It prints the bitrate in bits per second.
BASH
ffprobe -v error -select_streams v:0 -show_entries stream=codec_name,width,height,r_frame_rate,bit_rate -of default=nw=1 input.mp4

Divide the number by 1,000 to get kbps. A value like 9000000 means 9,000 kbps, or 9 Mbps.

Fix 1: Lower the bitrate in your editor

This is the quickest fix and works in CapCut, Premiere Pro, DaVinci Resolve, Filmora and others. The menu names differ, but the idea is the same.

  1. Open the export screen of your editor.
  2. Find the video bitrate setting. In CapCut for PC it is Export, then Bit rate. The CapCut help page shows that you can switch it to Custom and type a value in Kbps.
  3. Type a value close to your original bitrate, not above it. If the source was 8,000 kbps, try 6,000 to 8,000.
  4. Export 20 seconds of a busy part first and check the size and the look.
  5. If it looks fine, export the whole video.

Why a busy part? Quiet shots such as a talking face need few bits. Fast motion, leaves, crowds and rain need many. If a busy part looks clean, the rest will too.

Fix 2: Use CRF with HandBrake or ffmpeg

Fixed bitrate asks "how many bits per second?" CRF asks "how good should it look?" For a single file that you will keep or upload, CRF is usually the better question. The ffmpeg wiki says CRF runs from 0 to 51, 23 is the default, and a lower number means better quality. It also says that adding 6 roughly halves the file and subtracting 6 roughly doubles it. That rule matched my test: CRF 30 gave about half the size of CRF 23 in my clip’s bitrate range.

Run this on your finished export. It keeps the audio as it is, and only re-encodes the video.

BASH
ffmpeg -i export.mp4 -c:v libx264 -preset slow -crf 23 -c:a copy -movflags +faststart smaller.mp4

If you use HandBrake, the same idea is the Constant Quality slider on the Video tab. Its RF number works like CRF. Start at 22 for 1080p, look at the result, and raise it by 1 or 2 if you want a smaller file.

Keep your master

Do not compress your only copy. Keep the big export as a master and make a small copy for WhatsApp, Telegram or Drive. Every extra re-encode costs a little quality.

Fix 3: Try HEVC (H.265), but test it

HEVC can give a similar look at a smaller size than H.264. Many people on forums say it should always be smaller. It is not guaranteed. In the r/CapCut thread the user set a fixed 60,000 kbps for both codecs, so both files landed near the same size. When you fix the bitrate yourself, the codec cannot save you. Choose HEVC and a sane bitrate together.

The catch is playback. Old phones, some TVs and a few Windows PCs without the HEVC add-on may not play it. If you share with relatives on older phones, H.264 is the safe choice.

Fix 4: Match resolution and frame rate

Bigger frames and more frames per second cost more data. Common cases I see with students and small creators:

SituationWhat happensWhat to do
Phone clip is 1080p 30 fps, project set to 4K 60 fpsEditor invents extra pixels and frames, size jumpsSet the project to 1080p 30 fps
Instagram or Shorts uploadThe app compresses again anywayExport 1080p, moderate bitrate, no need for 4K
Sending on WhatsAppWhatsApp compresses it againExport 720p or 1080p at a low bitrate
Editing for college project submissionPortal may have a size limitCheck the limit, then pick a bitrate to fit

Fix 5: Aim for a target size

Sometimes a portal says "maximum 100 MB" and you just need to fit. Then use size and length to find the bitrate. The ffmpeg wiki shows this method: bitrate equals file size divided by duration, then subtract the audio bitrate. Here is an example for a 5 minute video and a 100 MB limit.

TEXT
100 MB x 8,000 = 800,000 kilobits
800,000 / 300 seconds = about 2,666 kbps total
2,666 - 128 (audio) = about 2,500 kbps for video
Leave a small safety gap: use 2,300 kbps

For a clean fit use two-pass encoding. It is slower but hits the size closely. Replace 2300k with your own number.

BASH
ffmpeg -y -i export.mp4 -c:v libx264 -b:v 2300k -pass 1 -an -f null /dev/null && ffmpeg -i export.mp4 -c:v libx264 -b:v 2300k -pass 2 -c:a aac -b:a 128k fit.mp4

On Windows, use NUL in place of /dev/null. This is mentioned in the ffmpeg wiki too.

If the video looks worse after shrinking

  1. Raise the bitrate by about 20 percent, or lower CRF by 2.
  2. Check that you did not shrink the resolution by accident.
  3. Fast motion and dark scenes break first, so look at those parts.
  4. Compare the saved file, not the editor preview. CapCut’s help page says its preview and Proxy setting can make playback look softer than the real export.
  5. Do not compress an already compressed copy again. Go back to the master.

Common mistakes

  • Judging by quality labels. "High" in one editor is not the same number as "High" in another. Read the real bitrate.
  • Setting a huge bitrate to be safe. Past the source quality, extra bits add size, not detail.
  • Upscaling. Making 1080p into 4K only makes a bigger file with the same detail.
  • Exporting a screen recording like a camera video. Screen recordings with still frames need much less data.
  • Using a low bitrate for the master. Save space on the copy you share, not on your only backup.

FAQ

Why did my 2 minute video become bigger after I cut it?

Because the new bitrate was higher than the camera’s. Length went down, but data per second went up more.

Is a bigger file always better quality?

No. Quality is limited by the source. After a point the extra size only stores the same picture in more detail than it had.

Can I cut a video without any size growth?

Some tools can trim without re-encoding, which copies the video as it is. The cut points then snap to keyframes. In ffmpeg, I tested -c copy on my sample clip and a 10 second cut was half of the 20 second file, as expected.

What is a good bitrate for 1080p?

There is no single number. For 30 fps phone footage, 6 to 10 Mbps is a common range for a copy you share, and a lower number can be fine for calm scenes. Test with your own clip.

Is CRF 23 good enough for YouTube?

It is a good start for a copy you keep. For upload, YouTube re-encodes anyway, so give it a clean, higher quality file and let it do the final squeeze.

Sources & Documentation


Written & Verified by Sampath Anji

Sampath Anji is a technology researcher, systems developer, and digital creator based in Telangana, India. He specializes in on-device AI architectures, autonomous agent workflows, high-throughput inference engines, and digital media production. Every tutorial on ISMARTANJI CREATIONS is grounded in code reproducibility, verified documentation, and transparent test environments. Read our full testing methodology on our About Us page, or submit feedback and code updates via our Contact Desk.

Leave a Comment