[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-en-photo-file-organization-guide":3},{"code":4,"message":5,"data":6},200,"ok",{"id":7,"slug":8,"title":9,"description":10,"content":11,"cover":12,"keywords":13,"tool":14,"tool_label":15,"reading_time":16,"status":17,"published_at":18,"created_at":18,"updated_at":18,"locale":19},546,"photo-file-organization-guide","The Photographer's File Organization System — Folder Structure, Naming, and Backup That Scales","A disorganized photo library becomes unusable at scale. Here's a folder structure, naming convention, and backup strategy that works whether you have 10,000 or 500,000 files.","Photo organization problems rarely appear immediately. They appear at the worst possible time: when a client wants a specific shot from a shoot two years ago, when a hard drive fails, or when you're trying to clear space and can't identify which files are originals and which are exported copies.\n\nA system that works is mostly a matter of deciding on conventions early and applying them consistently. Here's one that scales.\n\n## The Core Principle: Date-Based Folder Structure\n\nThe foundation of any photo organization system that doesn't collapse under volume is **date-based folders**. Dates are permanent, unambiguous, and sort naturally.\n\nThe top-level structure:\n\n```\nPhotos\u002F\n  2024\u002F\n    2024-03\u002F\n    2024-06\u002F\n    2024-09\u002F\n    2024-12\u002F\n  2025\u002F\n    2025-01\u002F\n    2025-04\u002F\n    ...\n```\n\nWithin each month folder, individual shoot folders:\n\n```\n2025-04\u002F\n  2025-04-12_johnson-wedding\u002F\n  2025-04-18_product-shoot-blueray\u002F\n  2025-04-25_headshots-campbell\u002F\n```\n\nThe folder naming convention is `YYYY-MM-DD_descriptive-name` in lowercase with hyphens. This sorts chronologically, identifies the content, and avoids ambiguity.\n\n**Why not subject-based organization?** Subject folders (Weddings\u002F, Portraits\u002F, Landscapes\u002F) seem logical but fail at scale: the categories multiply, cross-category shoots need to be in multiple places, and the folder structure requires ongoing decisions about where new content belongs. Date-based folders require no decisions—every new shoot goes to today's folder.\n\n## Inside a Shoot Folder\n\nWithin each shoot folder, a consistent structure:\n\n```\n2025-04-12_johnson-wedding\u002F\n  RAW\u002F\n    DSC_0001.NEF\n    DSC_0002.NEF\n    ...\n  EDITED\u002F\n    2025-04-12_johnson-wedding_001.tif\n    2025-04-12_johnson-wedding_002.tif\n    ...\n  EXPORTS\u002F\n    WEB\u002F\n    PRINT\u002F\n    CLIENT-DELIVERY\u002F\n  SELECTS.txt (or a Lightroom catalog reference)\n```\n\n**RAW\u002F**: Original files from the camera. Never modified, never deleted. These are your negatives.\n\n**EDITED\u002F**: Full-resolution edited versions (TIFF or PSD) that preserve all edit information. Used for high-quality re-exports.\n\n**EXPORTS\u002F**: Derivative files—JPEGs for web, print-optimized files for the lab, compressed versions for client delivery. Organized by output destination. These are expendable—they can be regenerated from EDITED files.\n\nThe critical rule: **never modify RAW files**. Never rename them. Never overwrite them. They should exist on the drive exactly as the camera created them.\n\n## File Naming Convention\n\nCamera default names (IMG_4821.jpg, DSC_0032.NEF) are meaningless outside the camera's context. But wholesale renaming RAW files creates risks—you lose the original sequence information and can't match camera file numbers to log entries.\n\nRecommended approach: rename files only in the EXPORTS\u002F and EDITED\u002F folders. Keep RAW files with original camera names.\n\nFor exported files, the naming convention:\n\n`YYYYMMDD_shoot-description_NNNN.jpg`\n\nExamples:\n- `20250412_johnson-wedding_0042.jpg`\n- `20250418_blueray-product_chair-hero_v2.jpg`\n- `20250425_campbell-headshots_sarah-001.jpg`\n\nThe date prefix ensures alphabetical sort equals chronological sort. The shoot description identifies context without opening the file. A sequence number or descriptive suffix distinguishes images within a shoot.\n\nFor clients receiving a gallery, you may want more descriptive names: `johnson-wedding-ceremony-0042.jpg` strips the date and gives them something more readable.\n\n## Version Control\n\nEdited files need version tracking. Two approaches:\n\n**Date-stamped exports:** The export filename includes the date: `20250415_campbell-sarah-headshot_001.jpg`. If you re-export a week later with different settings, the date changes and both versions coexist.\n\n**Version suffixes:** Append `_v1`, `_v2` to edited files. Simple and explicit.\n\nNever overwrite a delivered file with a newer version under the same name. Clients may have already shared, embedded, or published the original.\n\n## The 3-2-1 Backup Strategy\n\nAn unbackup photography library is an accident waiting to happen. Hard drives fail. Laptops are stolen. Apartments flood. The 3-2-1 strategy is the professional standard:\n\n**3 copies** of every file\n**2 different media types** (e.g., internal SSD + external HDD + cloud)\n**1 off-site** copy\n\nIn practice, for a working photographer:\n\n- **Primary drive:** Working SSD or RAID NAS in your home\u002Foffice\n- **Local backup:** External hard drive updated nightly (Carbon Copy Cloner on Mac, Macrium Reflect on Windows)\n- **Off-site backup:** Cloud storage (Backblaze B2, AWS S3, Google Cloud Storage) or a physical drive stored at a different location (updated weekly or monthly)\n\nFor active shoots, the off-site backup matters most. A fire or theft that destroys your office takes your primary and local backup simultaneously. Only an off-site copy survives.\n\n## Catalog Software vs File System\n\nLightroom, Capture One, and similar DAM (Digital Asset Management) software add a catalog layer on top of your file system: ratings, color labels, collections, keyword tags, and face\u002Flocation recognition.\n\nCatalog software is valuable for managing large libraries, but treat the catalog as supplemental to—not a replacement for—a clean underlying file system. If Lightroom's catalog is corrupted or lost, your files remain organized by the folder and naming system you built. If you relied on Lightroom's organization for everything, you lose your organization structure too.\n\nKeep the folder and naming system clean regardless of what catalog software you use.\n\n## Culling Workflow\n\nCulling—selecting the keepers from a shoot—should happen before you invest editing time. A shoot of 500 frames typically yields 50–80 selects worth editing.\n\n1. Import to RAW\u002F folder, keeping camera-assigned names\n2. Open in Lightroom (or Capture One, or a dedicated culling app like Photo Mechanic)\n3. First pass: mark obvious rejects (out of focus, blinking, severe motion blur)\n4. Second pass: rate survivors (1 star = maybe, 2 stars = probably use, 3 stars = hero images)\n5. Third pass: narrow 2-star and 3-star ratings to your final edit list\n\nThis process gets faster with practice. A 300-image event shoot should take 20–45 minutes to cull.\n\n## Archiving Old Projects\n\nProjects older than two years that are unlikely to need re-editing can be archived:\n\n- Move to a dedicated archive drive\n- Compress the EXPORTS\u002F folder to save space (the originals stay intact)\n- Remove from active Lightroom catalog but keep on the archive drive\n\nReview annually. The archive drive becomes your long-term insurance policy.\n\n---\n\nBefore archiving or delivering, compress your export JPEGs to manageable sizes with the free [Image Compressor](\u002Fcompress).","","photo file organization,photography folder structure,image naming convention,photo backup strategy,organize digital photos,photo library management","compress","Image Compressor",7,"published","2026-05-11 17:48:20","en"]