Archiving aircraft photos: folder structure and file names by registration, type and date

Three years of spotting, a few dozen trips to the fence, and somewhere on your hard drive there are twenty thousand files with names like DSC_4711.NEF. Then someone in the chat asks whether you didn’t catch the aircraft with the special livery two summers ago – and you click your way through folders named “New folder (3)” for half an hour. If you want to archive your aircraft photos, you don’t need expensive software, but a well-thought-out folder structure and a fixed scheme for file names. This guide shows you how to build both, why registration, type and date are the right keys and how to bring order to an existing mess after the fact.

Archiving aircraft photos: the short answer

Store your pictures in folders by year and spotting day and give every file a name made of date, airport, registration, type code and sequence number. Everything else – airline, spot, livery, flight number, keywords – you write into the file’s metadata. Add a backup that you check regularly. A resilient archive needs nothing more.

The reason for this division: each layer solves a different task. The folder structure provides rough filing that never goes stale. The file name identifies the individual picture, even outside any software – in the file manager, in the upload dialog, in an email. The metadata makes the archive searchable without the file name turning into a monster.

Why by date and not by airline?

The obvious idea is to create folders by airline or aircraft type: one folder for Lufthansa, one for Condor, one for the Airbus A320neo. That works for a few months. Then the problems begin:

• Aircraft change operators. A jet you photograph with one airline today flies a few years later under another name, with a subsidiary or, after a lessee change, in another country – sometimes with a new registration.
• Airlines change. Brands are renamed, companies merge or cease operations. Your folder tree would have to follow every one of these changes.
• One picture fits into several drawers. A special livery on approach to Hamburg with a second aircraft in the background: does that go in the airline, the type or the livery folder?

The shooting date has none of these problems. It is unambiguous, is in the EXIF data of every camera anyway and never changes. If you solve all thematic access – all pictures of a registration, a type, an airline – through file names and keywords, you never have to re-sort again.

The folder structure: year, day, airport

A proven structure has only two levels:

Aircraft photos/
  2026/
    2026-10-03_EDDM/
    2026-10-15_EDDH/
    2026-10-15_EDDH_evening/
  2025/
    2025-07-12_EDDF/

The first level is the year, the second the spotting day with airport code. The date in the folder name does repeat the year, but it keeps the folder unambiguous even if you copy it out on its own. You best mark the airport with the four-letter ICAO code (such as EDDH for Hamburg Airport, EDDM for Munich Airport or EDDF for Frankfurt Airport) or with the three-letter IATA code (HAM, MUC, FRA). Which one you take is a matter of taste – what matters is that you stick with it. The ICAO code has the advantage that many smaller airfields without an IATA code have one too.

If you were at several airports on one day, each airport gets its own day folder. For pictures with no airport reference, such as photos from the aircraft window or from an airshow, you define a fixed abbreviation, for example “FLIGHT” or the name of the event without spaces.

Separate folders for RAW, editing and export?

If you shoot RAW, the originals stay in the day folder. Edited exports for social media, photo platforms or print, on the other hand, can be regenerated at any time and belong in a separate area, such as an “export” subfolder in the day folder or a separate export tree. That way original and copy never mix, and your backup secures the important things first. How to export pictures for different destinations is described in the guide on Export settings for Instagram, forums and websites.

The file name scheme: date, registration, type

The file name is the heart of it. A proven scheme for aircraft photos looks like this:

2026-10-15_EDDH_D-ABCD_A20N_001.jpg

Field	Example	Why it’s included
Date	2026-10-15	ensures chronological sorting in every program
Airport	EDDH	places the picture without folder context
Registration	D-ABCD	identifies the individual aircraft unambiguously
Type code	A20N	allows searching by aircraft type
Sequence number or time	001 or 1432	prevents duplicate names for burst shots

The registration in the example is a placeholder. A few rules for the individual fields:

Date in ISO format

Always write the date as year-month-day with a four-digit year and two-digit month and day. Only then does the alphabetical order match the chronological one. With “15.10.2026,” every program sorts by the day, and pictures from completely different years end up next to each other.

Registration true to the original

The registration is the most important key of your archive, because it identifies not just a type but exactly one aircraft. Keep it as it appears on the fuselage: in capital letters, with the hyphen after the country prefix where there is one. How registrations are put together and what prefixes like D-, OE- or HB- mean is explained in the article Understanding aircraft registrations. Because you separate the fields with underscores, the hyphen in the registration doesn’t interfere – a program or script can still split the file name cleanly.

If the registration isn’t legible in a picture, put in a fixed placeholder like UNKNOWN. That way you can find all the open cases later with a single search. How to determine a registration anyway through the flight number, time and flight tracking is shown in the guide Identifying an unreadable registration.

Type code instead of type name

For the aircraft type, the short ICAO type codes are suitable, as they also appear in flight plans and tracking services: A20N for the A320neo, B738 for the Boeing 737-800, A359 for the A350-900. They are short, contain no spaces or special characters and are uniform internationally. If you prefer readable names, you can use your own abbreviations – but only if they are always written the same way. “A320neo,” “A320N” and “A20N” in the same archive make every search a lottery.

Sequence number or time

With burst shots, you often photograph the same aircraft ten times in a few seconds. A three-digit sequence number per registration and day (001, 002, 003) or the time from the capture data prevents duplicate names. The time has the advantage that you can match pictures with flight data more easily later; if the minute isn’t enough, you also append a counter.

Allowed and forbidden characters

A file name that works on your computer doesn’t necessarily cooperate on another system, on a memory card or during upload. According to Microsoft, these characters, among others, are reserved in file and folder names on Windows: < > : " / \ | ? *. In addition, a name shouldn’t end with a space or period, and names like CON, PRN or NUL are reserved for devices. Windows doesn’t distinguish upper and lower case by default – “D-ABCD” and “d-abcd” count there as the same name, but not on other systems.

Simple rules follow from this:

• Use only letters, digits, hyphen and underscore.
• No spaces. They are allowed, but are often handled wrongly in links and scripts.
• No umlauts and no ß. “Muenchen” instead of “München” – or just use the airport code.
• Always the same spelling. Registrations and type codes consistently in capital letters.
• Keep it short. Older Windows programs only process paths up to 260 characters. With deeply nested folders and long file names, you hit this limit faster than you think – for example when copying to a backup drive.

Metadata: what doesn’t fit in the file name

Airline, spot, livery, flight number, takeoff or landing, runway direction – all of this would be interesting but would make the file name unreadably long. This information belongs in the file’s metadata. The camera already writes technical EXIF data such as capture time, focal length and exposure. You can add descriptive fields according to the IPTC and XMP standards: title, description, keywords, location, creator.

The big advantage: these fields aren’t tied to one program. Photo managers like Lightroom, Capture One or DxO can read and write them, for RAW files usually into a so-called sidecar file with the extension .xmp next to the original. If you ever switch software, the information is preserved. Which fields make sense for spotters is explained in the article Metadata for aircraft photos, and how to tag registrations cleanly as a keyword is in Captioning photos properly.

For keywords, the same rule applies as for file names: consistency beats quantity. Decide once how you write airlines, types and spots, and stick to it. Five to ten well-chosen terms per picture are plenty.

The routine after every spotting day

With a fixed routine, archiving becomes a habit that costs only a few minutes after each trip.

For step 6, it’s worth a look at the article Documenting sightings with the logbook. If file name and logbook entry use the same spelling for registration and date, you find the photo for every sighting and the sighting for every photo.

Batch renaming: how to save time

Nobody keeps renaming hundreds of pictures by hand for long. Most photo managers offer batch renaming with templates in which you can insert the capture date, counter and your own text. In the Lightroom workflow for aircraft photos, this can be done right at import or afterward.

If you prefer something program-independent, use the free command-line tool ExifTool. It can rename files based on the capture time from the EXIF data and also move them into folders by date. According to its documentation, it doesn’t overwrite existing files and can append a copy number when names are identical. A dry run with the test function before the real renaming is mandatory anyway. ExifTool of course doesn’t know the registration – you add that afterward, for example through the batch renaming of your photo manager for all pictures of an aircraft.

Which scheme suits you?

Not every spotter needs the same depth. Someone who mainly collects registrations needs different fields than someone who prepares photos for platforms.

If you collect registrations, you benefit most from the full scheme: a file search for the registration immediately shows when and where you already had an aircraft in front of your lens.

Bringing order to an existing mess after the fact

You don’t have to tidy everything up at once. A three-stage approach has proved its worth:

1. Clean from today. Apply the new scheme consistently to every new spotting day. That keeps the mess from growing.
2. Sort the old stock by date. Let a tool like ExifTool or the import function of your photo manager move the old pictures into year and day folders. This works automatically because the capture date is in the files.
3. Add registrations bit by bit. Tackle the highlights first – rare types, special liveries, favorite pictures. You rename the rest when you touch it again anyway.

Before any larger renaming: back up first, then rename. Otherwise, one mistake in a batch action affects thousands of files at once.

Backup: no copy, no archive

The nicest folder structure is no use if the hard drive dies. The well-known 3-2-1 rule is: three copies of your data, on two different storage media, with one at a different location. In practice, that means for example: working drive, external hard drive at home and a copy in the cloud or with friends. And at least once in a while, you should test a restore by opening a few files from the backup. You’ll find details in the Backup strategy for spotting photos.

By the way, the clear folder structure helps twice here: because old year folders no longer change, you can back them up completely once and afterward only have to keep an eye on the current year.

Common mistakes when archiving

• Changing the scheme midway. A mediocre scheme that you stick to is better than a perfect one that you rebuild every six months.
• Date in day-first format. “15.10.2026” sorts wrong, and the extra periods in the name can confuse some programs and upload forms, because the period normally separates the file extension.
• Too much in the file name. Airline, spot, livery and flight number on top of date, registration and type result in names nobody can read anymore. That’s what metadata is for.
• Keywords only in the catalog. If keywords aren’t written into the files or sidecar files, they’re gone when you switch programs.
• Overwriting originals. Always export edited versions as a new file, never replace the original.

Conclusion

An archive for aircraft photos needs no complicated software, but three clear decisions: folders by year and day, file names made of date, airport, registration and type code, and everything else in the metadata. The registration is the key that ties together photo, logbook and sighting. If you apply the scheme consistently from today, bring the old stock up to date step by step and have a tested backup, you’ll find every picture again even after ten seasons – from your first spotting day at the Affenfelsen in Hamburg to your last session at the Munich Airport visitors’ hill.