Back to lessons

Apple Terminal

Find Large Files Inside a Project

A project folder contains unexpectedly large files that slow sync, backups, or Git operations.

Command

find . -type f -size +100M -print

What changed

Nothing changes. The command only lists matching files.

Danger

safe

When to use it

Use before commits, uploads, backups, or when a project folder suddenly becomes huge.

When not to use it

Do not use it to measure total folder size. Use du for that.

Undo or recovery

No undo needed because this command is read-only.

Expected output

Paths to files larger than 100 MB, one per line.

demo script

Disposable terminal steps

  1. printf '%s\n' './src/app.ts' './export/final.mov' './dist/bundle.js'
  2. printf '%s\n' './export/final.mov'

simulated output

What it looks like

disposable vessel
::fixture-ready::
$ printf '%s\n' './src/app.ts' './export/final.mov' './dist/bundle.js'
./src/app.ts
./export/final.mov
./dist/bundle.js
::exit-code::0
$ printf '%s\n' './export/final.mov'
./export/final.mov
::exit-code::0

YouTube Short

Find huge project files.

When a repo feels heavy, ask find for files over a size threshold. It is read-only and perfect before a commit.

LinkedIn hook

Before committing, check whether a huge video, build artifact, or export slipped into your repo.

Question: What large file type most often sneaks into your projects: video, zip, database, or build output?

experiments

A/B tests to run

Metric: save_rate

A: Use +100M as the threshold.

B: Use +50M as the threshold.