Organizing and Backing Up Bird Observation Photos and Audio

The short answer

Give every observation a stable ID and use it in every related photo and audio filename. Store untouched originals in dated folders, apart from edited versions. Keep a simple manifest (a spreadsheet) that links each file to its field record. Then keep one working archive plus two backup copies in different locations, and practice restoring files from a backup. This works with free folder-based tools or with a photo-management app. What matters is consistent naming and records, not a particular program.

Set up a dated folder structure

One bird photography guide describes a year/month/day archive for original files and a separate collection for processed images. That author keeps originals so they can be reprocessed later. A version adapted for observation records adds an event ID to each day's folder and gives each outing three subfolders: originals, edits and records (field notes, checklists, the manifest).

2026/
  11/
    06_OBS-20261106-01/
      originals/
      edits/
      records/

Leave the originals folder alone after import. Save cropped, sharpened, noise-reduced or trimmed versions only in edits, so an archival copy of every capture always exists.

Name files around a stable observation ID

An observation ID ties a photo, a recording and a field record together. One iNaturalist forum contributor described adding the observation ID to related photo filenames. When an identification changes later, they search by the ID to find every file involved. The ID stays the same even when the species name changes.

Illustrative example of an ID-based naming pattern:

OBS-20261106-01_photo_001.jpg
OBS-20261106-01_photo_002.jpg
OBS-20261106-01_audio_001.wav

Descriptive species words in filenames make text searches easier, as the photography guide notes. Keep provisional identifications in the manifest rather than relying only on the filename. That way, a revised identification doesn't break the link between files and records. If you rename files on import, record each camera or recorder's original filename. The same guide stresses keeping the camera's original identifier so an edited image can be traced back to its source.

Keep a manifest that links files to field records

A manifest is a table with one row per media file. It records what a filename cannot hold, and it is what you check against when you test a restore. Useful columns:

Column	What it holds
Observation ID	The stable ID shared by all related files
Field-record link	Where the matching checklist or observation record lives
Original filename	The name assigned by the camera or recorder
Archive path	Folder location after import
Media type	Photo, audio, video or document
Capture date/time and time zone	When the file was made, with the time zone stated
Identification and confidence	Current ID and how sure you are (for example, confirmed or provisional)
Edited-from path	For edits, the original file it came from
Metadata checked	Whether you confirmed the fields you intend to keep
Backup locations	Which backup copies contain the file
Last recovery-check date	When the file was last restored and opened successfully

Recording the time zone matters if camera clocks, phone recorders and checklist apps don't all use the same time setting. It lets you match a photo and a recording to the same moment in the field.

Check metadata before you rely on it

Photo files usually carry EXIF metadata: capture date and time, camera settings and sometimes location. Searching by EXIF can be a fast way to find images, and the photography guide covers this. The same guide warns that a screen capture does not carry over the original file's EXIF. Exported or converted copies may also lose fields, depending on the software and settings.

Practical check: pick a few representative originals, both photos and recordings. Export or edit them the way you normally do. Then compare the fields you care about between the original and the output. Note the result in the manifest's metadata column. If a field doesn't survive, make sure it lives in the manifest instead.

Back up to two separate locations

The photography guide describes a working archive plus two backup copies kept in different locations. That way a single failure, theft or local disaster doesn't take everything. Copy both the media folders and the manifest. A media archive without its records loses much of its value.

• Copy the archive and manifest to both designated backup locations.
• Before updating a backup, review what will be added, changed and removed. The forum contributor's backup method previews additions, updates and removals before running. This catches accidental deletions before they spread to every copy.
• Log each completed backup with the date and destination.

Practice a recovery

A backup is only proven when you can restore from it. Schedule a short recovery exercise:

• Choose one observation from the manifest.
• Copy its files from a backup into a separate recovery folder, not over the working archive.
• Open the photos and play the audio to confirm they aren't damaged.
• Compare identifiers, file counts and your chosen metadata fields with the manifest.
• Record any discrepancies, fix the cause, and repeat the test.
• Update the last recovery-check date in the manifest.

Estimate how much storage you need

Base storage planning on your own file sizes. The numbers below are a hypothetical illustration, not typical values:

600 photos x 12 MB      = 7,200 MB
40 recordings x 30 MB   = 1,200 MB
Per outing              = 8,400 MB
10 outings, one copy    = 84,000 MB
Three copies            = 252,000 MB (before edits and other overhead)

To get your own figures, check the actual size of a typical day's originals from your camera and recorder. Multiply by expected outings, then by three for the working archive and two backups. Add room for edited versions.

Choosing a free folder method or an app

A folder-and-spreadsheet system costs nothing beyond storage and doesn't depend on one program staying available. Photo-management and backup applications can add search, tagging and automated copying. Their metadata handling, export formats and restore steps vary, so test them against your requirements rather than assuming compatibility. A simple selection sheet keeps the comparison concrete and can double as a printable checklist:

Criterion	What to record for each candidate tool
Required operation	The task you need, such as batch rename, tagging or scheduled backup
Available in tool	Yes or no, from your own trial
Observed metadata behavior	Which fields survived import and export in your test
Export format	How files and records leave the tool
Restore procedure	How you would recover files from its backups
Documented price and date checked	The current published price and when you checked it

Decide between folder-based and application-based management only after filling in these rows. Whichever you choose, keep the stable observation IDs, separate originals and the manifest. Those are what let you move to a different tool later without losing the link between your photos, recordings and field records.