← CineCinch Home  /  Find & Shrink Oversized Videos

Guide · Windows video storage

How to Find and Shrink Oversized Video Files on Windows

File size alone is a misleading metric. Here's why MB/sec is the right way to find which videos are genuinely wasting space — and how to compress the worst offenders efficiently.

Why "sort by size" gives you the wrong list

The first instinct when cleaning up a video library is to open File Explorer, switch to Details view, and sort by Size descending. This puts the biggest files at the top — those must be the ones wasting the most space, right?

Not necessarily. Consider two files:

Bloated

Screen recording — 3.2 GB

Duration: 12 minutes (720 sec)

4.44 MB/sec

Over 20× more data per second than it needs. Will compress 75%+ with no visible quality change.

Efficient

Feature film — 8.5 GB

Duration: 2 hours 18 min (8,280 sec)

1.03 MB/sec

Reasonable for 1080p H.265 content. Compressing it would yield minimal savings at real quality cost.

A naive size-based sort puts the film at the top of the list and the screen recording further down — exactly backwards from a compression-priority standpoint. You'd waste time on a file that will barely shrink, and miss the easy wins.

MB/sec: the metric that actually works

MB/sec (megabytes per second of video) is a simple proxy for bitrate density. It answers the question: relative to how long this video is, how much storage is it consuming?

This metric is useful because it normalizes for length. A 10-minute clip and a 2-hour film can both be evaluated on the same scale — you don't need to mentally account for their different durations when comparing them.

📐 Formula: MB/sec = File size in megabytes ÷ Duration in seconds

Example: 3,200 MB ÷ 720 seconds = 4.44 MB/sec (very bloated)
Example: 8,704 MB ÷ 8,280 seconds = 1.05 MB/sec (reasonable for 1080p)

MB/sec is not a perfect measure of compression quality — it doesn't account for resolution, frame rate, or content complexity. But as a first-pass filter for identifying obvious waste in a large library, it's extremely effective in practice.

How to calculate MB/sec manually

You can calculate this yourself in Windows, but it's tedious for more than a handful of files:

  1. Right-click a video file in File Explorer → Properties → note the Size in MB.
  2. Open the file in Windows Media Player or VLC to find its duration in seconds.
  3. Divide size by duration: MB ÷ seconds = MB/sec.
  4. Compare against the thresholds for your library's resolution (see next section).
  5. Repeat for every file in the folder.

For a folder with 20 files, this takes 10–15 minutes. For a folder with 200 files, it becomes genuinely impractical. This is the exact problem CineCinch was built to automate — it probes every file with FFprobe and calculates MB/sec instantly for the entire folder.

What counts as bloated at each resolution

MB/sec thresholds vary by resolution because higher-resolution video legitimately requires more data per second to maintain quality. A 4K video that looks excellent at 2.0 MB/sec would be massively over-compressed at the same rate for a 480p recording.

The table below shows the MB/sec breakpoints used by CineCinch's three threshold levels:

ThresholdTarget resolutionEfficient (≤)AverageBloated (>)
Strict 720p and below 0.16 MB/sec 0.16–0.75 0.75 MB/sec
Medium 1080p HD 0.32 MB/sec 0.32–1.50 1.50 MB/sec
Generous 4K UHD 0.75 MB/sec 0.75–3.52 3.52 MB/sec

These thresholds reflect typical bitrates for well-encoded H.265 content at each resolution. A file classified as Bloated has meaningful compression headroom — it can be made significantly smaller with no perceptible quality loss on a normal display.

💡 Mixed libraries: If your folder contains a mix of resolutions, use the threshold that matches the majority. You can also run separate scans with different thresholds for different subfolders — e.g. Medium for a 1080p movies folder, Generous for a 4K folder.

Why automated scanning saves hours

Even knowing the formula, manually calculating MB/sec for a real library is unpleasant. Here's what's involved per file:

At 2–3 minutes per file, a 100-file folder takes 3–5 hours of manual work. CineCinch scans the same 100 files in under 2 minutes by running FFprobe in parallel across all files — and presents the results sorted by MB/sec descending, so the worst offenders are at the top automatically.

Finding and compressing oversized videos with CineCinch

  1. 01
    Download CineCinch from the Microsoft Store. A free 7-day trial is available with no payment required. FFprobe and FFmpeg are bundled — no separate installation needed.
  2. 02
    Select your video folder. Click the folder icon and navigate to the root of your library. CineCinch will walk all subfolders recursively.
  3. 03
    Set the quality threshold for your library. Choose Strict for 720p or lower, Medium for 1080p, or Generous for 4K content. This controls the MB/sec breakpoints for Efficient/Average/Bloated classification.
  4. 04
    Click Scan Videos. Results appear in real time as each file is probed. The table shows File path, Size (MB), Duration (sec), MB/sec, and Rating for every file — sorted highest MB/sec first.
  5. 05
    Filter to Bloated files only. Uncheck Average and Efficient in the Show filters. You're now looking at only your genuine space hogs. Uncheck specific files you want to exclude from compression.
  6. 06
    Configure output and start. Choose your output folder (or keep files alongside originals), select a quality mode, and click Start Compression. The Saved (MB) column updates in real time as each file completes.

Real-world examples of space savings

These are typical outcomes for common video types using CineCinch at Standard quality (CRF 25):

File typeBeforeAfterSavings
12-min OBS screen recording (H.264)3.2 GB620 MB~81%
45-min 1080p gameplay capture11.4 GB2.1 GB~82%
3-min GoPro clip (HEVC high bitrate)1.8 GB480 MB~73%
Premiere Pro export (H.264 50Mbps)8.7 GB1.4 GB~84%
2-hour movie (modern H.265 encode)6.2 GB5.1 GB~18%
TV episode (streaming H.264)1.4 GB1.1 GB~21%

The pattern is consistent: videos that were encoded with high-bitrate capture or export settings compress dramatically. Videos already encoded efficiently for streaming or archival see much smaller gains.

Frequently asked questions

What is MB/sec and why does it matter for video compression?

MB/sec measures how much storage a video uses per second of runtime. It normalizes file size by duration, making it a far better indicator of compression efficiency than raw file size. A 500 MB file that's 5 minutes long (1.67 MB/sec) is far more bloated than a 2 GB file that's 2 hours long (0.28 MB/sec).

How do I find oversized video files on Windows without special software?

You can open File Explorer in Details view and sort by Size — but this only shows raw file size, not efficiency. To find truly oversized files, you'd need to check each file's duration separately and calculate MB/sec manually. For any library with more than a handful of files, this is impractical — scanning tools like CineCinch automate it entirely.

What MB/sec value means a video is bloated?

It depends on resolution. For 720p, above 0.75 MB/sec is a strong compress candidate. For 1080p, above 1.5 MB/sec. For 4K, above 3.5 MB/sec. These reflect typical bitrates for well-encoded H.265 content — files above these thresholds have meaningful compression headroom.

Will I lose quality when shrinking oversized videos?

For genuinely oversized files — screen recordings, camera exports, editor outputs — re-encoding to H.265 at CRF 25 is visually lossless. The original had more data than any display could use. Well-encoded movies and streaming content are more sensitive, which is why the MB/sec analysis helps you skip those and focus only on the actual waste.

Does CineCinch modify my original files?

No. CineCinch creates new compressed output files without touching originals. You can optionally enable "Delete originals" to remove source files after verified compression, but this is disabled by default and is always your choice.