Organizing photos and videos not working: what to check, in order

The expensive mistake when photo and video organising goes wrong is changing several settings at once. After four changes, whatever fixed it is indistinguishable from whatever did nothing, and the same problem returns next month with no record of what worked. A fixed order of checks avoids that. Most cases resolve in the first two steps.

The sequence below moves from the cheapest check to the most disruptive one. Work down it and stop at the first place where the answer changes.

Name the symptom before touching anything

Three symptoms get described with the same sentence and have entirely different causes.

Something is missing. A file that should appear in a list or a search result does not.

Something will not open. It appears in the list, but opening it either stalls or fails.

Something looks wrong. It opens, but the date is off, the sort order is scrambled, or one item appears twice.

Missing points at the file or the search index. Will not open points at where the original is stored, or at permissions. Looks wrong points at which value is being read. Deciding which of the three applies takes ten seconds and removes two thirds of the checks below.

Symptom	Check first	Check second
Missing from a list	Is the volume mounted	Is the location indexed
Missing from search only	Index status for that volume	The search term itself
Stalls on open	Originals stored in iCloud	Network volume latency
Wrong date	Which date is displayed	Time zone of capture
Duplicate appears	Live Photo or RAW pair	Byte level comparison
Nothing happens at all	Permission for that area	The library package

Step 1: confirm the file is on this Mac

A file that lists instantly and opens slowly is usually not stored locally. With iCloud Photos set to optimise storage, the Mac keeps smaller versions and the full resolution originals stay in iCloud, retrieved on demand. For a photo the delay is small. For a long video on a weak connection it is not.

Two checks settle it. Open the iCloud section of the Photos settings and see which of the two options is selected. Then export a single item and time it. An export that completes immediately means the original is already here.

For files kept in ordinary folders, check the volume rather than the file. A disconnected external drive can leave a stale listing on screen while nothing behind it is reachable. Confirm in the Finder sidebar or Disk Utility that the volume is actually mounted, and confirm the path rather than trusting a recent items list.

One more case belongs here, and it accounts for a lot of partially restored collections. Images stored outside a Photos library are referenced files, and they are not included when the library is backed up. If a restore brought back most of a collection but not all of it, this is the most likely explanation, and no amount of repairing the library will produce the missing items.

Step 2: when search returns nothing

Search on macOS reads an index rather than walking the disk. In a location that was never indexed, a correct query returns nothing at all, which looks identical to the files being absent.

Three things are worth checking, in this order. Whether indexing is enabled for that volume, which mdutil -s will report for a given path. Whether the location has been added to the list of places excluded from search, in which case it will never return results. And whether the index is damaged, in which case rebuilding it is the fix, though the rebuild leaves search unreliable while it runs and is better started outside working hours.

There is a fourth cause that has nothing to do with indexing. The names shown in the Finder sidebar are not always the names on disk. A Mac running in Japanese displays ピクチャ and 書類, while the directories are Pictures and Documents. Searching from a terminal or a script using the displayed name finds nothing, because that name exists only in the interface. Anyone switching interface languages runs into this repeatedly, and the mapping between displayed names and real ones is worth knowing before writing any script that walks a home folder. How interface language affects what appears on screen is covered on the Languages page.

Step 3: when the date is wrong

A file carries a capture time written when the shot was taken, plus creation and modification dates maintained by the filesystem, plus an import date if an application recorded one. Applications differ in which one they show, which is why the same video can appear with two different dates on the same machine.

Three causes cover almost every case.

The file was copied or exported, so the filesystem dates were rewritten to the time of that operation while the capture time inside the image stayed as it was. This is why an archive copied to an external drive often sorts as though everything was shot on one day.

The capture time was recorded in a different time zone, so material shot abroad interleaves incorrectly with material shot at home.

There is no capture time at all. Screenshots and images produced by other applications frequently have no capture field, and no tool can sort them by a value that was never written. For those, either the filename or the import date has to stand in.

To tell which case applies, inspect one file rather than the whole collection. mdls lists the metadata attributes for a single path, including the content creation date, which is enough to see whether a capture time exists and what it says.

Step 4: when duplicates are not duplicates

Automatic duplicate removal is the step most likely to destroy something, because several legitimate pairs look exactly like duplication.

A still image and a short video sharing the same base name are usually the two halves of a Live Photo. Deleting the video half does not free much space and does remove the motion permanently. A RAW file next to a JPEG of the same frame is a deliberate pair, one for editing and one for sending.

A less obvious source is a camera format change. Setting an iPhone or iPad camera to Most Compatible makes new captures JPEG and H.264 rather than HEIF and HEVC. Switching that setting partway through a period leaves the same subject recorded in two formats on different dates, and both files are originals.

Exported copies are the hardest case, since they often keep the original filename in a different folder. Name matching cannot resolve them. Comparing content can: running shasum against two candidates produces values that match only if the bytes are identical, regardless of name, date or location. Treat anything that does not match as a pair to review by eye, not as a duplicate.

Step 5: when permissions are the cause

An operation that produces no error and no result is usually a permissions problem. macOS gates access per area, and a denied area often produces silence rather than a message.

Reading a Photos library from another application requires the Photos permission, and that permission can be limited to selected items, in which case everything else is invisible to the tool. Desktop, Documents, Downloads and removable volumes are each separate grants, so allowing one does not open the others. Full Disk Access is broader still, and some tools stop entirely without it.

The Photos library itself deserves care. It is a package, so it can be opened like a folder, but it is not designed to have files moved or rewritten inside it by hand. Scripts that modify its contents directly tend to produce exactly the class of problem this article is about, where what the application shows and what is on disk no longer agree.

The Privacy and Security section of System Settings lists what has been granted. Rather than enabling everything, work out which area the failing operation is reaching for and grant only that one. If the operation starts working, the cause is confirmed rather than guessed at.

Step 6: rebuilding the library, last

If the file exists, the index is healthy, the dates are explained and permissions are correct, and the Photos interface still shows something wrong, the library itself can be rebuilt. Apple documents the procedure:

If you experience problems with photos in a library, you can try to repair it. Important: Make sure to back up your photo library before repairing it. Source: support.apple.com

The steps are to quit Photos, hold Option and Command while clicking the Photos icon, then choose Repair in the window that appears. If that does not resolve it, restoring from a Time Machine backup is the remaining option.

Where that backup lives matters. Apple warns against using Time Machine to store a backup on the same external drive that holds the photo library, because the permissions on the library can conflict with those on the backup. Confirm that a usable copy exists somewhere else before starting a repair, not after.

When only video is affected

Sometimes every check above comes back clean, stills behave normally, and only video misbehaves. That narrows the cause to three places.

Size is the first. A single clip can be hundreds of times larger than a photo, so a location that feels fine for images becomes slow for video. On an external drive or a network share, reading a large file can look identical to a hang. Copying one clip to the internal disk and opening it there separates a storage problem from a file problem in about a minute.

Codec is the second. Video recorded as HEVC can be viewed and edited on macOS High Sierra 10.13 and later. If a clip refuses to play in one application but opens in the system preview, the limitation belongs to that application's own playback, not to the operating system, and the fix is a setting or a different tool rather than a conversion of the file.

Thumbnails are the third. Video that appears as a grey tile in a list usually means thumbnail generation has not finished or has failed for that item. The file itself is generally intact, which is easy to confirm by opening it. In a folder holding hundreds of clips, generation can take several minutes, and interrupting it repeatedly by reopening the folder is what keeps it unfinished.

If none of the three explains it, move one clip to an empty folder and repeat the test. A symptom that follows the file points at the file. A symptom that stays behind points at the folder or the volume.

What to change first

Write down the three lines that matter before closing the issue: which symptom it was, which step found it, and what changed. That note is what stops the next occurrence from restarting at step one. Keeping the listing, the terminal and the notes in a single window makes the sequence above repeatable rather than improvised, which is what the Features page describes; the permission boundaries that cause step five are listed on the FAQ page. For a folder based workflow where those checks happen in one place, Atriens is built around that shape.