Practical storage guide

Disk analysis for video editors: media, proxies, and render caches

Video libraries can contain originals, proxies, render data, and external references. Measure first, then let the editing application manage its generated media where possible.

Where the space goes

Large libraries

A library’s total does not tell you which files are originals or generated output.

Missing originals

An exported movie is not a backup of the edit, raw footage, or project dependencies.

External storage

A disconnected source drive or cloud placeholder can hide dependencies from a local scan.

A practical cleanup workflow

STEP 1

Scan each media volume

Use the same scope for each scan and check that the relevant external drives are mounted.

STEP 2

Open the project

Check linked media and completion state in Final Cut, Premiere, Resolve, or the application that owns it.

STEP 3

Clear generated media through the editor

Use the editor’s cache/proxy/render management rather than deleting package internals by guesswork.

STEP 4

Keep a verified archive

Preserve originals and projects, verify the archive, then use the collector only for files you have identified. Trash retains storage until emptied.

Tools to compare

NullDisk offers native Mac maps, SSH/cloud sources, and development cleanup, plus a separate CLI. Match each tool’s platform and features to the job.

NullDisk features → · CLI and terminal workflows →

Common questions

Does the map identify safe-to-delete proxies?

No. It shows where storage is used. Confirm the role of each file in the editing application.

How can I track project growth?

Disk Graph exports snapshots; GrandPerspective saves scans. NullDisk’s CLI can save JSON reports. Keep matching scope and size semantics when comparing dates.