File Hierarchy

In my books I’ve been a strong proponent of saving images in a fixed file hierarchy pretty much since the first day I started using digital cameras (that would be back in the late 80’s). 

Products like Lightroom and Apple Photos have a tendency to mask where your images actually live. I don’t like this. I want to know where my images are and control how they’re organized, because that helps me find them faster. 

I note that Scott Kelby has a new course he’s teaching for Lightroom called SLIM (Simplified Lightroom Image Management), and the foundation of that is basically a fixed file hierarchy that he then maps directly into Lightroom. 

By fixed file hierarchy I mean that you have an organizing principle from which you create folders in which to put your images. Some logical organization that is suited to the way you shoot. For example, many people tend to group by date:

file heirarchy 1

Each year you create a new folder for the year, then all ingests for that year go into folders within that folder. In the simple example, above, we have only a few events that triggered a photo ingest, so just naming them directly like this is perfectly fine. But if you were repeating some of these things, then your folder structure might start to look something more like:

         Jan 5 Trip to Yosemite
         Jun 10 Trip to Yosemite
         Aug 8 Trip to Yosemite

Or better yet:

                     Jan 5
                     Jun 10
                     Aug 8

Thing is, you need some sort of plan, and some reasonable thinking about what might be coming down the pike to build a folder structure that works. 

Personally, since most of my early work was repeated product photography and trips to various places in the US and overseas, my structure looked something like this:

file heirarchy 2

Technically, I probably should have had just one Rocky Mountain National Park folder and then individual trips within that, but my trip schedule really didn’t get out of hand until recent years. Now I have a pile of folders that should be slightly better organized at the lower levels. Since I don’t have everything hooked into Lightroom, I very well may just reorganize my file structure next time I move my files to new RAID drives.

In my International Travel folder, you’ll find sub-folders by continent, then country, then place within the country. In US Travel you’ll find folders by state, then place within the state. I’ve been doing that now for almost 30 years, so all I need to remember is where I took a photo, even vaguely, and I can often find it very quickly just by browsing in Finder. 

The point that needs to be made here is simple: you need an organizing principle for creating folders to contain your images. Don’t just start slamming everything into the same folder. It doesn’t matter if you copy my structure or create your own. Actually, you should always create your own: only you know how you think about the places/events/people you shot and how you’d search for them.

Note that I can type “2013 Rocky Mountain” into Spotlight on my Macintosh and it’s going to pull up that folder. I don’t need Lightroom or another product to find where something is because I’ve been consistent in naming folders and files themselves (for example, in the 2013 Rocky Mountain folder you’ll find files named US_CO_Rocky Mountain_DATE_CAMERA_SEQUENCE#, so I’ll be finding files as well as folders). 

Most photographers seem to use date as the primary naming function for both folders and files. So you often see something like this on their drives:


and so on.

Note how that doesn’t really allow to do a quick “find” on the folders or files using the OS search options. If you’re going to go that route, add descriptive information:

     2016-08-11 Botswana Moremi
                2016-08-11_Botswana Moremi_1397.NEF
                2016-08-11_Botswana Moremi_1398.NEF
                2016-08-11_Botswana Moremi_1399.NEF

This is actually one of my longstanding tips on how you name things: how would you search for it using a search string? If you answered “Botswana Moremi 2016” then those things better be in the folder and file name hierarchy you create. 

And here are some of the primary organizing principles that you need to consider in creating your folder/file hierarchy:

  • Date — if you take only a few shots at a time, I’m not sure date helps you a lot. Date sometimes helps a lot when you have multiple similar events on different dates (e.g. sports).
  • Place — obviously travelers going to lots of places are going to gravitate towards this, but again think about how you remember something. If it’s by place, then place needs to be in your hierarchy and naming.
  • Event — I’d argue that most people should consider this one first and foremost. A lot of photography is event driven. And you’ll be searching for those photos later based upon the event (“hey, I never saw those photos you took at Grandpa’s 75th birthday party”). Date+Event is a common organization system.
  • Person or People — If you’re mostly photographing friends and family, this obviously is a potential organizing principle. Likewise if you’re a portrait photographer (but see next). 
  • Client — There’s a strong reason to organize by client if you’re a professional. If you do this right you can let them browse just their photos (and not those of other clients because you’ve set the permissions accordingly), or quickly clone and send them their photos.

Don’t let your images just start filling random file folders or sprawl across multiple hard drives. That’s a recipe for eventual disaster. Build a single drive with a folder hierarchy that makes sense, and put images into that structure logically and consistently. Back that drive up regularly (both on site and off site). You’ll be glad you did.

text and images © 2017 Thom Hogan
portions Copyright 1999-2016 Thom Hogan-- All Rights Reserved
Follow us on Twitter: @bythom, hashtags #bythom, #dslrbodies