Organizing photos and videos: how to decide what you need

Feature lists do not separate photo and video tools. Almost every candidate will claim tagging, batch renaming, duplicate detection, smart albums and fast previews. The differences that matter on a Mac are not in that list. They are in how a tool touches the files, what it is allowed to reach, and what survives after it is uninstalled. Those four things can be checked in an afternoon, before any money changes hands.

What follows is the order in which to check them, and what each answer rules out.

The first decision is not a tool

Before comparing anything, decide where the original files are going to live. On macOS there are two answers, and they lead to different shortlists.

One is inside a Photos library. The other is in ordinary folders on disk, which a file manager, a terminal or any other application can open directly.

The decision has a consequence that is easy to miss until it has already happened. Apple limits what gets uploaded when iCloud Photos is on:

Important: If you use iCloud Photos, remember that only the photos and videos in your System Photo Library are uploaded to iCloud. Be sure to back up all of your photo libraries. Source: support.apple.com

More than one library can exist on a Mac, but only one at a time is the System Photo Library. Switching to another library turns iCloud Photos and Shared Albums off automatically, and Apple's own guidance notes that once the contents of a newly designated System Photo Library have been uploaded, the libraries cannot be unmerged.

So this is not a preference. It is a structural choice that decides which tools are even candidates. A tool built to read a Photos library will be inert against a folder of exported files, and a tool built around folders will only ever see what has been exported out of the library.

Two kinds of tools, and one question that separates them

Once the location is settled, ask where a tool writes the information it creates. Ratings, keywords, captions, colour labels, sort order. There are two designs.

The first writes into the file, or into a sidecar file that sits next to it. Move the file to another machine and another application, and the information moves with it, as long as the receiving application reads that field.

The second writes into the application's own index. The files are never modified. The application holds the association between a file and its keywords in a database of its own.

Neither is wrong. macOS itself uses both. Finder tags are stored as extended attributes on the file, so they travel with it across a disk that supports them. Albums and keywords inside Photos live in the library, not in the individual images.

	Written into the file	Held in the app's index
Survives moving to another app	Yes, if the field is read	Only through an export
Speed on large collections	Slower, each file is rewritten	Faster, nothing is rewritten
Risk to originals	The file is modified	Originals untouched
What remains if the app is gone	The metadata	Whatever was exported

The honest way to choose is by how long the information has to last. A shortlist that gets rebuilt every quarter is fine in an index. Capture keywords meant to still be readable in five years belong in the file. Test this before committing: tag one image, export it, and open the export somewhere else.

Permissions show what a tool intends to reach

macOS asks for consent per area, and media tools run into those boundaries constantly. The set of prompts a tool raises in its first ten minutes is a fair description of its scope.

Four areas are worth watching.

Access to the Photos library is its own permission, and it can be granted for selected items instead of the whole library. Desktop, Documents and Downloads are separate permissions from each other. Removable volumes are another. Full Disk Access is a broader grant that some indexing tools request, and it is worth knowing whether the tool degrades gracefully without it or simply stops.

The useful signal is not the number of prompts. It is whether the tool still does something useful when a prompt is declined. A tool that becomes an empty window unless everything is granted has made a design decision that will be felt again later, the first time a permission is revoked by a system update and features go quiet without an error message.

Network volumes deserve a separate note. When the share disconnects, the files vanish from the tool's point of view. Index based tools sometimes record that absence as a deletion. Anyone keeping media on a NAS should test exactly that: disconnect, reopen the tool, reconnect, and see what the library looks like afterwards.

Which date is being shown

Two applications can display different dates for the same file, and both can be correct. A single image carries a capture time written by the camera, plus a file creation date and a file modification date held by the filesystem, plus whatever import date the application recorded.

Copying, exporting or converting a file updates the filesystem dates. The capture time inside the image does not change. A tool that sorts by the filesystem date will scramble a collection the first time it is copied to an external drive.

The test takes one minute. Take an image whose capture date is known, let the candidate tool read it, and see which date appears. If it matches the capture time, the tool is reading the image. If it matches today, it is reading the file.

Time zones are the second half of this. A capture time recorded abroad may be stored in local time, which puts images out of order against everything shot at home. If travel is part of the work, the ability to shift capture times for a selection is a real requirement rather than a nicety.

Formats, and what quietly fails to read them

Apple introduced HEIF for photos and HEVC for video with iOS 11 and macOS High Sierra 10.13. Both compress better than JPEG and H.264 at similar visual quality, which is why an iPhone fills less space than it used to for the same number of shots. Capture is supported on iPhone 7 and later, iPad (6th generation) and later, and several other models.

Two practical consequences follow.

Older utilities may simply not list HEIF files. Nothing errors. The count is just lower than expected, which is a difficult thing to notice in a folder of several thousand items. Checking that a candidate displays a HEIF file, rather than skipping it, belongs in the first ten minutes of any trial.

The other consequence is that the format mix on a Mac is still changing. On supported Macs running macOS Tahoe 26 or later, screenshots are captured as HEIF and screen recordings as HEVC when the capture format is set to HDR. Any organising scheme written around PNG screenshots and MOV recordings has an assumption in it that no longer holds.

Setting a phone camera to Most Compatible produces JPEG and H.264 instead, at the cost of space. That is a valid answer, but it is a decision about the camera, made because of a limitation in the tool, and it should be recognised as such.

Price is three questions

The monthly or one time number is the least informative part of pricing. Three questions carry more weight.

Does the licence stop working when payments stop, or does it fall back to read only. Are major version upgrades included, or charged separately, which is what usually determines the cost of the next macOS release. And what comes out at the end: if all the organising work lives in an index, an export path is the only thing standing between that work and nothing.

There is one more cost that shows up only after something goes wrong. Files kept outside a Photos library are not covered by a library backup:

Important: If any of your image files are stored outside your photo library, those files (known as referenced files) aren't backed up when you back up your library. Be sure to back up those files separately. Source: support.apple.com

A tool that keeps originals in place, outside the library, is a reasonable choice. It just means a second backup route is now part of the setup, and that belongs in the cost of the decision.

Four checks that have nothing to do with features

Prices on a website can be current while the product behind them is not. Before paying, confirm four things.

Whether the product is still being developed. A release history that stopped two years ago is a prediction about the next macOS update. Whether new signups are still open, since some products continue serving existing customers only. Whether ownership has changed, because a change of owner is often followed by a change in pricing model. And whether a price change has already been announced for a date in the future.

None of these are reasons to avoid a product. They are simply facts that change what a purchase means, and all four are visible from a vendor's own release notes and pricing page in a few minutes.

Running a shortlist through the same six rows

What to check	Where to look	What it decides
Where originals live	Photos settings	Library based or folder based tools
Where metadata is written	Export options	Whether the work is portable
Permissions requested	First launch	How much access is required to be useful
Date shown	One known image	Capture time or filesystem time
HEIF handling	A HEIF file in the list	Whether the tool sees current formats
Exit path	Export formats	What remains after cancelling

Filling in six rows for three candidates takes about an hour and removes most of them. The last two rows are the ones that get skipped and then matter most, usually six months later.

There is also a structural answer worth considering. Sorting media involves three motions in sequence: look at a set, narrow it by a condition, then act on what is left. When those three live in separate applications, the narrowing happens in one window and the acting happens in another, and the rule that was just worked out gets lost in between. A file manager with a built in terminal collapses that into one place, which is a different kind of improvement from a longer feature list. The scope of that approach is set out on the Features page, and how it lines up against other options is on the Compared with other file managers page.

What to change first

Pick the location of the originals before anything else, then test exactly one candidate against the six rows above rather than installing four at once. Check the plan limits on Pricing and the permission details on the FAQ page before the trial ends, since those are the two answers that are expensive to discover late. If the folder based route fits, Atriens is one of the tools built around it.