How to organize Sony footage without losing a single C0001.MP4

Sony makes excellent cameras and one of the least helpful file structures in the industry. You come back from a shoot with a card that contains a folder called PRIVATE, inside it M4ROOT, inside that CLIP, and inside that forty files named C0001.MP4 through C0040.MP4. Nothing in that chain tells you anything about what you shot.

Worse: the second body did exactly the same thing, starting at C0001.MP4.

This is the workflow that fixes it, in the order that matters.

What is actually on the card

Before you copy anything, it helps to know what you are looking at. A modern Sony card, from an A7 IV, FX3, FX30, A7S III or ZV-E1, looks like this:

PRIVATE/
  M4ROOT/
    CLIP/        C0001.MP4      the real clips
                 C0001M01.XML   metadata sidecar per clip
    SUB/         C0001S01.MP4   proxies, if you enabled them
    THMBNL/      C0001T01.JPG   thumbnails for camera playback
    GENERAL/

If you shot AVCHD on an older body, the path is different and the files are .MTS:

PRIVATE/AVCHD/BDMV/STREAM/00000.MTS

Three things worth knowing:

• The .XML sidecar holds the camera model, creation date and recording settings. It is small. Keep it.
• SUB holds proxies. If you recorded them, they are the fastest way to review a shoot on a laptop before you touch the originals.
• THMBNL is for the camera’s own playback screen. You can drop it.

Copy the whole PRIVATE folder on the first pass. Sort out what you need afterwards, on the drive, not on the card. Cards are the one place where an unrecoverable mistake is a single keystroke away.

The C0001 collision, and how to stop it

This is the problem that eats real projects.

The clip counter lives in the camera, not on the card. Two bodies on the same job both produce C0001.MP4. When you drag both cards into one folder, macOS asks whether to replace, and somebody, eventually, at the end of a long day, clicks the wrong button.

Two fixes, and you want both:

In camera. Set file numbering to Series instead of Reset. The counter then keeps climbing across card formats instead of starting over. It does not solve two bodies, but it solves the same body across a week.

On import. Put the camera into the filename. A7SIII_C0001.MP4 and FX30_C0001.MP4 cannot collide, and six months later you know which body shot which take without opening anything.

If you do nothing else from this article, do this one. Every other problem here is annoying. This one loses footage.

A folder structure that holds up

The structure that survives contact with reality is boring, shallow and date first:

2026-08-14_ClientName_Project/
  01_Footage/
    A7SIII/
    FX30/
    Drone/
  02_Audio/
  03_Photos/
  04_Transcripts/
  05_Project/
  06_Exports/

Why this shape:

• Date first, in ISO order. 2026-08-14 sorts correctly in every file browser on earth. 14.08.2026 does not.
• Numbered folders. They stay in the order you meant, not alphabetical order.
• Camera as a subfolder, not as the top level. You look for a project first and a camera second. Never the other way round.
• Shallow. Every level of nesting is a level someone has to click through at 11pm.

Resist the urge to build folders for scenes or subjects at this stage. You do not yet know what you have. Scene structure belongs after the analysis pass, not before it.

Names that tell you what is inside

A filename is the only piece of metadata that is visible in Finder, in Premiere’s project panel, in Resolve’s media pool, in a terminal, and in an email to a client. It is worth the effort.

A pattern that works:

A7SIII_C0087_Rooftop-Interview-Marcus_16x9_4K_25FPS.mp4

Read from the left: camera, original camera number, what it actually is, then the technical facts. The original number stays because it is your route back to the card and to the camera’s own logs.

The rules that matter more than the exact pattern:

• Never lose the original name. Keep it in the filename or in a log file. A rename you cannot reverse is a rename you will regret.
• Hyphens between words, underscores between fields. It reads better and survives every operating system.
• No spaces, no umlauts, no slashes, no colons. They break command line tools, some NAS shares and the occasional render farm.
• Sortable prefix. If sequence matters, use 01_, 02_, with leading zeros. 10 sorts before 2 otherwise.

Doing this by hand for 300 clips is roughly two hours of your life per shoot. Which is why almost nobody keeps it up past the third project. Bulk renaming on a Mac covers the tooling options, from the Finder’s own batch rename to automated naming.

Finder tags: the part everyone skips

macOS has a tagging system built into the file system, and video people almost never use it. That is a mistake, because Finder tags are indexed by Spotlight, which means they are searchable from every open dialog in every application, not just from Finder.

A small, disciplined tag set beats a large one. Something like:

• Role: interview, broll, ambience
• Quality: select, review, reject
• Content: three to eight subject tags per project, no more

Then tag:select tag:interview in a Finder search gives you your string-outs in a second, from any application, without opening an NLE.

The discipline part is the hard part. Tags applied to 40 of 300 clips are worse than no tags, because you will trust them and they will lie to you. Either tag everything or tag nothing.

Where the analysis pass fits

Here is the order that actually works, and it is not the order most people use:

1. Copy the card. Verify. Do not touch the card again until there are two backups.
2. Analyze the flat folder. Before any filing, get a description, subject tags and a transcript for each file.
3. Rename from the analysis.
4. File into folders from the analysis.
5. Tag from the analysis.
6. Now open your NLE.

Steps 3 through 5 are all downstream of step 2, and step 2 is the one that used to be impossible without a person watching everything. It is not impossible any more, which is what changes the shape of the whole workflow. The wider version of this argument is in AI video asset management.

A note on S-Log3 and proxies

Two Sony-specific details that trip people up:

Log footage looks flat to a machine too. A model analyzing S-Log3 frames sees a washed out image. It still recognizes subjects and scenes perfectly well, but do not expect it to comment usefully on color or mood. If you have proxies with a LUT baked in, analyzing those instead can give slightly better descriptions.

Proxies and originals should carry the same name. If C0087 becomes A7SIII_C0087_Rooftop-Interview, the proxy should become A7SIII_C0087_Rooftop-Interview_proxy. Renaming only one half of the pair is how relinking breaks three weeks later.

What this looks like automated

Everything above is a set of rules a machine can follow. That is exactly what Cliptag does on macOS: you drop the copied card folder in, it reads each clip’s frames and audio, writes a descriptive filename with the technical suffixes you choose, applies Finder tags, files everything into folders by media type and date, and transcribes anything spoken.

For Sony material specifically, three things are worth knowing before you try it:

• XAVC-S and XAVC HS, including 10-bit, are read directly. No transcode needed.
• Camera RAW formats are not supported. If you shoot ProRes RAW or record externally to a RAW format, export a standard version first.
• The original file is never deleted or altered, and every rename and move is written to a log file so you can reconstruct what the card looked like.

The free plan covers 25 cloud analyses per month, and the on-device mode on Apple Silicon is free and unlimited, which is the right choice for client material that should not leave your Mac.