A wedding film rarely goes wrong because of the footage. It goes wrong in the first hour of the edit, when an editor opens a drive and finds six folders called "Card 1", three clips named C0001 and a drone folder buried inside someone's desktop. Folder structure and file naming are the least glamorous part of wedding videography, and they quietly decide how fast your editor can start cutting, how reliably a project relinks after a crash, and whether a revision three months later is a ten-minute job or a two-day archaeology project.
This guide is for wedding videographers and studios who hand footage to an outside editor, and for anyone who plans to. It explains what cameras actually do to your file names, why duplicates appear, and how to build one folder structure and one naming convention that works for every wedding you shoot. It covers the traps that come from card formats and operating systems, and it ends with a handoff checklist and a short answer section. The goal is simple: when the drive or transfer link arrives, the editor should be able to understand what is on it without asking you a single question.
Why naming and folders decide how fast the edit starts
File naming matters because editing software finds media by path and file name. Premiere Pro and DaVinci Resolve link to your clips in place rather than storing copies of them, and Final Cut Pro can be set up to do the same. If a clip has the same name as another clip, sits in a folder that was renamed, or lives on a drive that was reorganised after the project was built, the software reports offline media and someone has to reconnect it by hand. On a wedding with several cameras and hundreds of clips, that manual work is where the hours disappear.
Good structure helps in three separate places. First, at ingest, the editor sees at a glance which clips belong to which camera, operator and part of the day. Second, during the edit, bins and sequences are built from your folders, so a clean structure produces clean bins with no extra effort. Third, in the long run, a project you archive today still opens next year because the paths inside it still make sense. Each of these saves minutes on a single wedding and days across a season.
There is also a business reason. An editor who receives a tidy drive trusts the rest of the handoff. An editor who receives chaos assumes the rest of the brief is equally loose, and either charges for the extra organising time or quietly cuts corners. A consistent structure is a cheap signal that you are a professional client, and it supports every other part of your footage handoff to an editor.
| Problem on the drive | What the editor sees | Typical result |
|---|---|---|
| Duplicate clip names from two cards | Two different clips with identical names in one bin | Wrong shot in the timeline, or one clip skipped on import |
| Folders renamed after the project was built | Offline media in the sequence | Manual relinking, delays on every revision |
| No camera or operator labels | Unlabelled footage with mixed looks | Slow grading, wrong camera matched to the wrong profile |
| Everything dumped in one folder | Thousands of clips in a single list | Longer ingest, no sense of the day's timeline |
| Spaces, symbols and very long names | Errors on transfer or on a different operating system | Failed copies and broken relinks |
What cameras actually name your files
Cameras name files automatically, they use counters that are easy to misunderstand, and they are designed for a single shooter on a single card rather than for a multi-camera wedding. Knowing the rules each system follows is the first step to controlling them.
Canon's support documentation describes the pattern clearly. Folders are named with a three-digit number followed by five characters, such as 100CANON, and the folder number runs from 100 to 999. Image files are numbered from 0001 to 9999, appearing on a computer as IMG_0001.JPG, while movies start with MVI_. Each folder holds up to 9999 files, and when it fills the camera creates a new folder with the next number. Canon also offers three numbering modes: Continuous keeps counting across card changes, Auto reset returns to 0001 when you replace the card or create a folder, but if the card already contains images, numbering may continue from the highest existing file number. Manual reset restarts the count and starts a new folder on demand.
Sony's XAVC S clips are stored in a fixed structure on the card: PRIVATE, then M4ROOT, then CLIP. MP4 video goes into numbered folders such as xxxANV01 that the camera names, and still images into DCIM. The camera fixes that folder structure, so plan your organisation around ingest rather than the card. Wolfcrow reports that on his Sony camera, clips deleted in the camera free their numbers for reuse, so numbering on a card does not always reflect shooting order.
DJI drones use DJI_0001 style names and place media in numbered folders such as 100MEDIA. DJI does not document this clearly and user reports conflict: behaviour varies by model and app, and some users report that numbering rolls into a new folder such as 101MEDIA after DJI_0999. Do not rely on the counter as proof of order.
| Source | Typical pattern | Where it lives on the card | What to watch for |
|---|---|---|---|
| Canon EOS and Cinema EOS | IMG_0001, MVI_0001, 100CANON folder | DCIM / 100CANON | Counter mode (Continuous, Auto reset, Manual reset) changes whether names repeat |
| Sony Alpha XAVC S | C0001 style clip names | PRIVATE / M4ROOT / CLIP | Fixed card structure, numbers may be reused after in-camera deletion |
| Sony MP4 | Sequential clip names in ANV folders | MP4 folders (xxxANV01) | Folder names are generated by the camera |
| DJI drones | DJI_0001 style | DCIM / 100MEDIA and similar | Counter behaviour depends on model and app, folders roll over |
| Audio recorders | Recorder-specific numbered files | Recorder folder | Names rarely match any camera clip |
The duplicate-name problem on multi-camera weddings
Two cameras with the same default counter will produce clips that share a name, and that is the single most common reason a wedding folder becomes unreliable. A wedding is a perfect storm for it: two or three bodies, several cards each, a second shooter with a camera of the same model, and a drone. Every card can start counting from the beginning, so a typical day produces many files with the same name in different folders.
The danger is not the duplicate itself. It is what happens when someone moves those files into one folder to make the drive look tidy. A copy operation either overwrites one of the clips, silently renames it, or stops and asks. If the person copying is tired at midnight after a fourteen-hour day, the answer they click may destroy footage that exists nowhere else. This is why the first rule of file organisation is to never merge cards into one flat folder before the names are unique.
Where duplicates come from.
Duplicates arise from four sources. Formatting a card resets the counter in many cameras. Auto reset modes restart numbering every time a card is changed. Two identical camera bodies produce identical patterns by design. And card readers that rename files on copy can create their own suffixes. In practice you cannot rely on a camera to give you unique names, so the uniqueness has to be created at ingest.
Three ways to get unique names.
The first approach is to set the camera numbering to Continuous where the camera allows it, so that names keep counting across cards from one operator. This helps but is not a guarantee, because it depends on every operator remembering the setting and on cards being formatted in the same camera. The second approach is to use folder separation: every card is copied to its own folder named for camera and card, so identical file names never meet. This is the minimum safe option. The third approach is to add a prefix at ingest through a batch rename, so each clip carries the camera and card identity in the name itself. The third approach is the strongest, and the next sections build it into a full convention.
Whichever you choose, keep the original camera file name inside the new name. Metadata and sidecar files sometimes refer to the original name, and an editor or a client years later may need to trace a clip back to the card. Adding a prefix is safe. Replacing the original name entirely is not.
A folder structure that survives the handoff
The best folder structure is the one you use on every wedding without thinking. It should be shallow enough to navigate quickly and specific enough that nobody needs to open a file to know what it is. A widely used approach in video production, described by film-industry guides such as Wolfcrow's file organisation article, is to build the drive in layers: date, then scene, then setup, with production or camera folders added above for multi-project or multi-camera shoots. For weddings the useful layers are slightly different, because the day is organised by time and by camera rather than by scripted scenes.
A practical wedding structure has these top-level folders inside a single project folder named for the couple and date: a footage folder, an audio folder, a drone folder, a graphics and music folder, a reference folder, and a documents folder for notes. Inside the footage folder you separate by camera and card, and optionally by part of the day.
| Folder | What goes in it | Example |
|---|---|---|
| 00_NOTES | Handoff brief, shot list, timeline, contact details, README | Brief.pdf, Timeline.txt, README.txt |
| 01_VIDEO | All camera footage, separated by camera and card | A-CAM_Card01, B-CAM_Card01 |
| 02_AUDIO | Recorder files, lavalier tracks, ambient audio | GROOM_LAV, CEREMONY_REC |
| 03_DRONE | Aerial clips and any flight notes | DRONE_Card01 |
| 04_MUSIC_AND_GRAPHICS | Licensed tracks, logo, titles, LUTs and presets | Music_Licensed, Logo, LUTs |
| 05_REFERENCE | Past films for style, photos of the couple, grade stills | Style_Reference_Links.txt |
Why the numbered prefixes help.
Numbers at the start of a folder name force every operating system to list the folders in the same order, which means the editor always opens the notes first and the footage second. They also make a verbal handoff easy: "the brief is in folder zero, zero". Use two digits so that folders keep their order if you ever add a tenth.
Keep the structure identical on every job.
Consistency across weddings is worth more than a perfect structure on any one. An editor who works on your films every month learns the layout once and then stops thinking about it. A template folder on your computer, copied at the start of each wedding, is the simplest way to guarantee it. Keep the template as a real empty folder tree so you create a new project by copying and renaming one folder.
A file naming convention you can apply in minutes
A good file name carries the date, the camera, the card and the original clip number in a fixed order, uses only safe characters, and sorts correctly in a plain alphabetical list. You do not need a complicated system. You need one pattern, written down, used every time.
The most useful pattern for weddings is: date, project, camera, card, original name. For example, 2026-06-14_SmithJones_A-CAM_C01_C0001.MP4 tells the editor the wedding day, the couple, that the clip comes from the main camera, that it was on the first card, and what the camera originally called it. Putting the date in year-month-day order means files sort chronologically in any file browser, which is the same reason many production guides recommend the YYYY-MM-DD format for date folders.
| Element | Example | Why it is there |
|---|---|---|
| Date (YYYY-MM-DD) | 2026-06-14 | Sorts chronologically, identifies the wedding |
| Couple or project code | SmithJones | Prevents mix-ups when several weddings share a drive |
| Camera and operator | A-CAM, B-CAM, SECOND | Tells the editor which look and angle to expect |
| Card number | C01, C02 | Makes duplicates impossible and speeds recovery |
| Original camera name | C0001 | Keeps the link to metadata and sidecar files |
Rules for characters.
Use letters, numbers, hyphens and underscores only. Avoid spaces, accents, ampersands, slashes and emoji. Some transfer tools, command-line scripts and older software handle spaces poorly, and a character that is fine on your computer can be illegal on another operating system. Underscores between the major elements and hyphens inside an element is a convention that reads well and breaks nothing.
When to rename: on the card or after copying.
Rename after copying, never on the card. Leave the card structure exactly as the camera wrote it until the footage is safely copied and verified in two places. Cameras may not recognise folders that do not match their expected format (Canon documents this for folders created on a computer), so altering names on the card is a risk with no upside. Copying first and renaming the copy keeps the original untouched until you are sure.
A bulk renamer saves hours here. Most operating systems and every professional ingest tool can add a prefix to hundreds of files in seconds. Test the pattern on a copy of one card before you apply it to a whole wedding.
Card handling rules that protect the structure
The card is where your folder structure begins, so a few habits at ingest prevent most of the problems described above. These rules cost nothing and apply to every camera.
First, copy the whole card, not just the clip folder. Sidecar files, thumbnails and metadata sit beside the video, and some software needs them to read timecode and clip information correctly. Sony cameras, for example, write XML sidecar files next to XAVC S clips, and although some editing software can read the same information from the video file itself, the cautious approach is to include the complete card structure in the handoff.
Second, verify the copy before you format anything. Use an ingest tool that compares checksums, or at minimum compare file counts and sizes between the card and each destination. The 3-2-1 approach covered in our guide to wedding footage backup should be complete before a single card is wiped.
Third, format cards in the camera that will use them, not in a computer. Camera formatting writes the correct folder structure and resets the card cleanly. Remember that the file system matters too: SDHC cards up to 32GB typically ship formatted FAT32, and SDXC cards (above 32GB, typically 64GB and up) as exFAT. FAT32 has a 4GB maximum file size, and a long high-bitrate clip may be split into several files or cut off, which explains why a ceremony clip sometimes arrives as several consecutive numbers. Lexar's guidance gives the example of a ten-minute clip at 100Mbps reaching roughly 7.5GB, which cannot fit as one FAT32 file. Both file systems work on Mac and Windows, but a drive you send to an editor should also be formatted exFAT or NTFS, never FAT32.
| File system | Maximum single file | Mac and Windows | Use for |
|---|---|---|---|
| FAT32 | 4GB | Both can read and write | Small cards, older cameras |
| exFAT | No practical limit | Both can read and write | Large cards, handoff drives |
| NTFS | Very large | Windows native, Mac read-only by default | Windows-only drives |
| APFS and Mac OS Extended | Very large | Mac native, Windows cannot read by default | Mac-only drives |
Fourth, label physical cards. A numbered card that matches the card number in your file names removes any doubt when a clip looks corrupted and someone needs to go back to the original.
Paths, length limits and operating system traps
The full path to a file, meaning every folder name plus the file name, has a length limit on some systems, and a deep structure with long names can break a transfer without any warning. Microsoft's documentation states that the traditional maximum path length in Windows is 260 characters, counting the drive letter, the separators and a terminating null character. Individual name components are usually limited to 255 characters. Windows 10 and later can opt in to much longer paths, but it requires a registry setting and an application that declares support, so you cannot assume that your editor's tools allow it.
This matters because wedding file names get long quickly. A path such as a drive letter, then a project folder with the couple's names, then a footage folder, then a camera folder, then a card folder, then a file name with date and couple repeated, can approach the limit faster than you expect. The practical fix is to keep names short and avoid repeating the same information at every level. Use the folder tree to carry the camera and card, and keep the file name to the elements that must travel with the clip.
Keep names short, not cryptic.
Aim for file names under about forty characters and folder names under about twenty-five. That leaves plenty of headroom for the editor to drop your project into a deeper tree on their own storage. Abbreviations are fine if you list them in your README, for example A-CAM for the main camera and B-CAM for the second.
Case sensitivity and hidden files.
Mac and Windows treat upper and lower case differently in some situations, and Linux-based servers are strictly case-sensitive. A file called Brief.pdf and one called brief.pdf may be the same file on your laptop and two different files on a cloud server. Choose one capitalisation style and stay with it. Also be aware that Mac systems create hidden metadata files that show up as clutter on Windows drives; a quick cleanup before you send a drive removes them.
Audio, drone and phone footage: the files that don't match
Audio recorders, drones and phones follow their own naming rules, and these are the files most likely to arrive without any context. Treat them as separate sources with their own subfolders and labels, never mixed into the camera folders.
Audio recorders usually number files by recording session rather than by clip, so a ceremony recording may be named something like a generic recorder number with no link to any video. Add a short prefix that names the person or position, such as GROOM_LAV or ALTAR_REC, and write down in your notes which recorder channel held which microphone. If you use a recorder that writes multichannel or polyphonic files, keep the original and mention it in the brief. For the full audio side of preparation, see our guide on preparing wedding audio before you outsource editing.
Drone files deserve their own folder and their own card label because their counters are the least predictable of the day. Add the flight location to the folder or a note, for example the venue exterior versus the ceremony site, so the editor can place the shot without watching all of it. Keep the original DJI numbering inside the name and rename only after copying.
Phone clips from guests or from a second shooter's personal device are often named by date and time or by app. They are valuable but unpredictable, and a consistent prefix such as GUEST or PHONE makes them easy to find and easy to exclude.
| Source | Folder | Prefix | Note for the editor |
|---|---|---|---|
| Main camera | 01_VIDEO/A-CAM_C01 | A-CAM | Primary profile and LUT |
| Second camera | 01_VIDEO/B-CAM_C01 | B-CAM | Different body, may need a different LUT |
| Second shooter | 01_VIDEO/SECOND_C01 | SECOND | Mention the operator by name |
| Audio recorder | 02_AUDIO/GROOM_LAV | GROOM_LAV | State which channel is which |
| Drone | 03_DRONE/DRONE_C01 | DRONE | Add the flight location |
| Phone or guest clips | 01_VIDEO/PHONE | PHONE | Lower quality, use sparingly |
If you shoot multiple cameras and your editor will synchronise them, matching structure also helps with the sync step. Our guide on how to sync multicam wedding footage before handoff explains why a clean camera-by-camera layout makes that process faster and more reliable.
Write the README and run a pre-send check
A short text file at the top of the project turns a folder structure into a briefing. The README is where you explain the abbreviations, list the cameras and operators, note any known problems and give the editor a person to contact. It takes five minutes to write and it replaces a dozen emails.
What the README should contain
Include the couple and date, the delivery deadline, a list of cameras with their operator and frame rate and profile, a list of audio sources and which person each microphone was on, a short timeline of the day, any clips you know are problematic, and the naming convention itself. Keep it plain text so it opens on any system. Link or point to the brief for style and music notes rather than repeating them.
The pre-send checklist
Before you transfer or ship, run through a short list. Check that every card has its own folder, that no two files share a name, that the total file count matches the cards, that nothing sits loose in the root of the drive, and that the README is present. Open a few clips from each folder to confirm they play. Then confirm the copy with a checksum comparison if your tool supports it, or at least with matching folder sizes.
| Check | How to do it | Pass condition |
|---|---|---|
| Unique names | Sort the whole footage tree by name or run a duplicate finder | No two clips share a name |
| Complete copy | Compare file counts and sizes against each card | Counts and sizes match |
| Playback test | Open at least one clip per card | Every sample plays with sound |
| Safe characters | Scan names for spaces and symbols | Only letters, numbers, hyphens and underscores |
| README present | Open the notes folder | Cameras, audio sources and timeline are listed |
| Backup in place | Confirm a second copy exists elsewhere | Two independent copies before sending |
Once the drive is ready, choose how it travels. Our guide to sending wedding footage to your editor compares transfer options, and the structure you built here works the same way on a shipped drive or a cloud link. If you would like an editor who works from a clean handoff like this and returns a finished film on a predictable schedule, you can get a quote from FrameFlow Edit and describe your workflow.
Frequently asked questions
Should I rename my wedding clips before sending them to an editor?
Yes, but only after you have copied and verified the footage, and only by adding a prefix. Keep the original camera file name inside the new name so that sidecar files and metadata still match, and never rename files on the card itself, because cameras may not recognise folders that do not match their expected format. A consistent prefix with date, camera and card makes every clip unique and traceable.
Why do two of my clips have the same name?
Cameras count from their own counter, and that counter often restarts when a card is formatted or replaced. Canon cameras, for example, offer Continuous, Auto reset and Manual reset numbering, and Auto reset returns to 0001 on a new card, although it may continue from existing files if the card is not freshly formatted. Two cameras of the same model will also produce the same pattern. The safe fix is to keep every card in its own folder and add a camera and card prefix at ingest.
What folder structure is best for a wedding project?
Use one project folder per wedding, named with the date and couple, containing numbered subfolders for notes, video, audio, drone, music and graphics, and reference material. Inside the video folder, create one subfolder per camera and card. The exact names matter less than using the same layout on every wedding, so that your editor learns it once.
Is it safe to use spaces and special characters in file names?
It is better to avoid them. Spaces, accents and symbols can cause problems with command-line tools, cloud services and different operating systems, and a character that works on one computer may be rejected on another. Stick to letters, numbers, hyphens and underscores, which work everywhere.
What happens if my file path is too long?
On Windows, the traditional limit is 260 characters for the whole path, and software that has not opted in to long paths may fail to copy or open files beyond it. Keep folder and file names short, avoid repeating the same information at every level, and test a copy on a different machine if you are unsure. Short, structured names also make relinking in the editing software more reliable.