Sony A7 IV Camera Workflow May 25, 2026 · 14 min read
You bought the A7 IV because it shoots everything — 33MP stills, 4K 60p video, 10fps bursts. Now you have 12,000 files across four SD cards and no idea where anything is. Here's the system that fixes it permanently.
Why this camera creates more file chaos than anything you've owned before
Every uncompressed ARW from the A7 IV's 33MP sensor weighs 50–60 MB. A single 2-hour portrait session at moderate shooting pace produces 30–40 GB of RAW data. Shoot RAW+JPEG and that doubles. Your 512 GB card fills faster than you think.
Many A7 IV shooters use RAW+JPEG for quick client previews or social media delivery. But now every shutter press generates two files — DSC09421.ARW and DSC09421.JPG — with identical filenames except the extension. Sorting them manually is a nightmare.
The A7 IV is a hybrid camera. You're shooting XAVC S/XAVC HS video clips between stills. Now your card dump contains ARW, JPEG, and MP4 files all mixed together with sequential numbering that tells you nothing about the content.
Sony names every file DSC0XXXX or _DSC0XXXX. After the counter rolls past 9999, it resets. You end up with DSC00001.ARW from three different shoots on three different cards. Good luck finding your daughter's birthday photos in 2 years.
The A7 IV's CFexpress + SD combo makes organization harder than it needs to be
The A7 IV's Slot 1 (CFexpress Type A / SD) and Slot 2 (SD only) support multiple recording modes. Most shooters use Simultaneous for backup redundancy or Sort to split RAW to Slot 1 and JPEG to Slot 2. Both create dual import headaches.
In Simultaneous (backup) mode, both cards contain byte-for-byte identical files with identical filenames. Import both cards without thinking and you have exact duplicates cluttering your drive — or worse, overwriting each other if imported to the same folder.
In Sort mode (RAW → Slot 1, JPEG → Slot 2), you import two cards that need to be merged into the same folder structure — matching DSC09421.ARW from card 1 with DSC09421.JPG from card 2. Manual merging is tedious and error-prone.
Don't format between shoots? Now your 256 GB card contains Friday's product shoot, Saturday's engagement session, and Sunday's family portraits — all under DCIM/ with sequential numbering. No folder separation. No visual cues.
The silent workflow killer that grows with every shoot
Sony's sequential numbering system (DSC00001 → DSC09999) resets after 9,999 frames. If you've been shooting the A7 IV for a year, you've likely cycled through this range multiple times. Import two different cards with overlapping ranges into one folder and you'll silently overwrite files — or your OS will append (1) suffixes that break your Lightroom catalog links.
The backup-mode trap: Shooting Simultaneous writes identical files to both slots. If you import both cards thinking "better safe," you now have DSC05230.ARW and DSC05230 (1).ARW — two copies of the same 55 MB file eating disk space. Across a 3,000-photo wedding, that's an extra 165 GB of waste.
How FolioSort handles this: FolioSort detects naming collisions during organization. It can automatically append a unique suffix based on the file's EXIF timestamp, ensuring no file is ever overwritten or silently duplicated. You define the rule once and forget about it.
Three proven structures for different shooting styles — pick one and commit
Best for photographers who shoot multiple genres and need a simple, universal system. Every file lands in a year → month → day hierarchy. Add an Extension subfolder to separate ARW from JPEG automatically.
FolioSort template: {YYYY}/{MM-Month}/{DD}/{Extension}/
Photos/ ├── 2026/ │ ├── 01-January/ │ │ ├── 15/ │ │ │ ├── ARW/ │ │ │ │ ├── DSC00142.ARW │ │ │ │ └── DSC00143.ARW │ │ │ └── JPG/ │ │ │ ├── DSC00142.JPG │ │ │ └── DSC00143.JPG │ │ └── 28/ │ │ └── ARW/ │ ├── 02-February/ │ └── 03-March/
If you shoot with the A7 IV alongside an A7R V or another body, separate files by camera model and lens. Ideal for second-shooter workflows where you need to know who shot what, instantly.
FolioSort template: {YYYY}/{MM}/{Camera}/{Lens}/
Photos/ ├── 2026/ │ ├── 05/ │ │ ├── ILCE-7M4/ │ │ │ ├── Sony-FE-24-70mm-F2.8-GM-II/ │ │ │ │ ├── DSC01200.ARW │ │ │ │ └── DSC01201.ARW │ │ │ └── Sony-FE-85mm-F1.4-GM/ │ │ │ └── DSC01250.ARW │ │ └── ILCE-7RM5/ │ │ └── Sony-FE-70-200mm-F2.8-GM-OSS-II/ │ │ └── DSC04500.ARW
Use FolioSort's Events feature to define time blocks. Files are sorted by when they were taken — not just by date, but by the specific moment within an event. The A7 IV's EXIF timestamps drive the entire process.
FolioSort Events configuration:
2026-06-14_Martinez-Wedding/
├── 01_Getting-Ready/
│ ├── DSC03001.ARW ← EXIF: 10:23 AM
│ └── DSC03002.ARW ← EXIF: 10:24 AM
├── 02_Ceremony/
│ ├── DSC03180.ARW ← EXIF: 2:05 PM
│ └── DSC03181.ARW ← EXIF: 2:06 PM
├── 03_Portraits/
│ └── DSC03400.ARW ← EXIF: 4:15 PM
├── 04_Reception/
│ ├── DSC03600.ARW ← EXIF: 6:30 PM
│ └── C0012.MP4 ← EXIF: 8:45 PM (first dance video)
└── 05_Video-Clips/
└── C0008.MP4 ← EXIF: 3:20 PM (ceremony highlight)
From SD card dump to clean folder structure in under 60 seconds
Copy both SD/CFexpress card contents into one staging folder. Don't sort, don't rename, don't think. Just dump. FolioSort handles the rest by reading each file's embedded EXIF metadata.
Choose a folder template — {YYYY}/{MM-Month}/{DD} for date-based, {Camera}/{Lens} for multi-body, or use Events for weddings. FolioSort's wizard suggests templates based on what it finds in your files.
Click Run. FolioSort reads EXIF from every ARW, JPEG, and MP4, then moves files into the correct folders. 4,000 files? Under 30 seconds. Naming collisions handled automatically. Open Lightroom and start culling.
DateTimeOriginal, Camera Model (ILCE-7M4), Lens Model, Focal Length, Aperture, ISO, GPS (if enabled), Color Space, Image Dimensions. All preserved during organization — FolioSort never modifies file contents.
Same EXIF fields as ARW, plus embedded thumbnails and color profiles. FolioSort can route JPEGs to a separate subfolder or keep them alongside their RAW pair — your choice.
Creation date, duration, resolution (4K/1080p), codec info. Video clips get organized into the same date/event structure as your stills — no separate video workflow needed.
The A7 IV writes full lens identification — even for third-party lenses (Sigma, Tamron, Samyang). Use {Lens} or {FocalLength} tokens to create subfolders by glass. Find every 85mm portrait shot instantly.
Stop fighting Lightroom's import dialog. Organize first, import second.
Lightroom Classic's import dialog wants to copy files into its own folder structure using a rigid date-based system. If you shoot RAW+JPEG, Lightroom imports both but gives you no clean way to separate them. If you import from two cards, duplicate filenames cause conflicts. And Lightroom's "Into Subfolder" option only supports basic date tokens — no camera body, no lens, no custom events.
Run FolioSort on your raw card dump. Files are moved into your chosen folder structure with EXIF-based naming. ARW and JPEG separated. Duplicates handled.
In Lightroom Classic, select the organized root folder and choose Add (not Copy or Move). Lightroom reads files in place and mirrors your folder structure exactly. No re-copying. No re-sorting.
Your Lightroom catalog now has folders named by date, camera, lens, or event. Navigate the folder panel to jump to any session instantly. Start culling — the organization is already done.
Bonus: Because you used Add instead of Copy, Lightroom doesn't duplicate your files. The organized folder structure on disk is the catalog structure. Move the folder to a NAS later? Just update the Lightroom folder location — all edits, keywords, and collections stay intact.
From 4 SD cards and 6,000 files to a delivery-ready structure in minutes
A typical A7 IV wedding generates 3,000–6,000 files across two shooters. Lead on the A7 IV with a 24-70mm GM II and 85mm f/1.4 GM. Second shooter on an A7C II or A7R V. Both shooting RAW+JPEG. Four SD cards at the end of the night. Here's the workflow:
Back at your workstation, copy all four cards into a single staging folder: ~/Staging/2026-06-14-Martinez/. Don't try to sort cards into subfolders manually — let EXIF handle it.
Open FolioSort, load the staging folder, and create Events with time blocks based on the day's timeline:
Getting Ready → 09:00 – 12:30 First Look → 12:30 – 13:00 Ceremony → 14:00 – 15:30 Family Formals → 15:30 – 16:00 Couple Portraits → 16:00 – 17:30 Cocktail Hour → 17:30 – 18:30 Reception → 18:30 – 23:59
FolioSort reads every file's EXIF timestamp and sorts into event folders. Files from both camera bodies end up in the same event folder, sorted chronologically. Import into Lightroom with Add. Cull by event — start with Ceremony (usually the most time-sensitive for the couple). Export directly from each event folder for partial delivery.
Organize 2 weeks of travel photography without internet or a laptop
Two weeks in Japan. A7 IV with a 24-70mm f/2.8 GM II and a Tamron 35-150mm f/2-2.8. Shooting RAW only. 400–600 frames per day. That's 6,000–8,000 ARW files across three SD cards — no folder separation between Tokyo, Kyoto, and Osaka.
Don't waste travel time organizing on a laptop. Shoot freely. Format cards only when they're full and after you've verified the backup copy. Every file's EXIF contains the date, time, GPS coordinates (if enabled on the A7 IV), and lens data. That metadata is your organizational safety net.
Dump all cards into a staging folder. Set FolioSort's template to {YYYY}/{MM-Month}/{DD}/{City}/. FolioSort reads EXIF GPS data and reverse-geocodes to city names. Every photo lands in the correct day and location folder:
Japan-2026/ ├── 2026/ │ ├── 03-March/ │ │ ├── 01/ │ │ │ └── Tokyo/ │ │ │ ├── DSC05001.ARW │ │ │ └── DSC05002.ARW │ │ ├── 02/ │ │ │ └── Tokyo/ │ │ ├── 05/ │ │ │ └── Kyoto/ │ │ └── 10/ │ │ └── Osaka/
No GPS on your A7 IV? No problem. Use date-only sorting ({YYYY}/{MM-Month}/{DD}/) and the photos still land in day-by-day folders. You can manually rename the day folders to add city names later — or use FolioSort's rename feature to batch-rename based on EXIF data.
How to cut 4,000 frames down to 400 deliverables — faster
The A7 IV's 10fps burst mode means you'll often have 8–12 nearly identical frames from a single sequence. Culling is where you reclaim time. But culling 4,000 unsorted files in a flat folder is masochistic. Here's how pre-organization makes culling 3x faster:
After FolioSort sorts by event time blocks, you cull Ceremony separately from Reception. Each event is 300–800 frames — digestible. You maintain focus and make faster keep/reject decisions.
If you shot RAW+JPEG, use FolioSort to route JPEGs to a Previews/ subfolder. Cull using the smaller JPEGs in Photo Mechanic or FastRawViewer, then match your picks back to the ARW files for editing.
Sort by lens to quickly review all 85mm portraits together, all 24-70mm wide shots together. This is especially useful for wedding formals — find every 35mm group shot in one folder.
Don't delete rejects immediately. After culling, move rejected files to an _Rejects/ folder within the event. Archive to a cold storage drive. Delete after 6 months if the client hasn't requested anything extra.
A folder structure only matters if it survives long-term
3 copies of every file. 2 different media types (SSD + NAS, or SSD + cloud). 1 offsite (cloud or a drive at a friend's house). The A7 IV produces large files — a single wedding can be 200+ GB of RAW. You need a system that scales.
Recommended archive structure:
Archive/ ├── 2026/ │ ├── 2026-01-15_ProductShoot-BrandX/ │ │ ├── RAW/ ← Original ARW files │ │ ├── Selects/ ← Edited TIFFs/PSDs │ │ ├── Delivery/ ← Final JPEGs for client │ │ └── Lightroom-Catalog/ ← .lrcat + previews │ ├── 2026-03-01_Japan-Travel/ │ │ ├── RAW/ │ │ ├── Selects/ │ │ └── Web-Export/ ← Resized for Instagram/blog │ └── 2026-06-14_Martinez-Wedding/ │ ├── 01_Getting-Ready/ │ ├── 02_Ceremony/ │ ├── 03_Portraits/ │ ├── 04_Reception/ │ ├── Delivery-Gallery/ ← Client-facing exports │ └── Lightroom-Catalog/
Because FolioSort creates a plain folder-and-file hierarchy — no database, no catalog file, no proprietary index — you can copy the entire structure to any NAS (Synology, QNAP, TrueNAS) and it's instantly browsable. No import step. No conversion. Works with Immich, Photoprism, or just SMB shares from any device.
Cold storage tip: After final delivery, move the RAW/ folder to a dedicated archive drive and keep only Selects/ and Delivery/ on your fast SSD. Your working drive stays lean. The archive drive has everything, organized identically, searchable by date and project name.
Print this. Tape it to your monitor. Follow it every time.
{YYYY}/{MM-Month}/{DD}/_Rejects/ folders quarterlyCommon questions about organizing Sony A7 IV photos
DateTimeOriginal field embedded in every ARW and JPEG the A7 IV produces. Set a folder template like {YYYY}/{MM-Month}/{DD}/ and FolioSort moves each file into the correct year, month and day folder automatically — no manual sorting required. The process handles thousands of files in seconds.
{Extension} in your folder template to automatically route ARW files into a RAW/ subfolder and JPEG files into a JPG/ subfolder within the same date hierarchy. This keeps your RAW editing files separate from quick-share JPEGs.
DSC00001.ARW on both cards. FolioSort handles naming collisions automatically — it can append a unique suffix or use EXIF timestamp renaming to guarantee unique filenames during organization. No silent overwrites, no manual intervention.
{Lens} or {FocalLength} tokens in folder templates, automatically creating subfolders like Sony-FE-24-70mm-F2.8-GM-II/ or 85mm/. This makes it easy to find every portrait or wide-angle shot from a session.
The multi-camera wedding folder hierarchy — Getting Ready, Ceremony, Reception — built automatically from EXIF timestamps.
What EXIF data is, which fields matter most, and how to use it to automate your file sorting workflow.
Deep dive into FolioSort's Events feature — define time blocks, sort thousands of files by moment, and organize multi-day events.
A real case study on EXIF-based organization at scale on macOS.
Download FolioSort free. Organize up to 100 files per operation with no account required.