Default Folder X: the setup order that holds up

The reason for looking up Default Folder X is usually narrow and specific. Every Save dialog opens in Documents, the target folder is four levels down, and that descent happens dozens of times a day. Tools of this kind fix that by attaching themselves to the system Open and Save dialogs, which means the behaviour of every application changes at the same moment the tool starts. That is what makes the setup order matter. Turn on six features in the first hour and there is no way to tell which one produced the result, or which one caused the odd behaviour in the application that has its own file picker.

What a dialog tool changes, and what it leaves alone

On macOS, Open and Save dialogs are not built separately by each application. They are one system facility, which is why a single tool can improve them everywhere at once. What it improves is the moment a location gets chosen. Nothing on disk moves, no folder gets renamed, and removing the tool returns the dialogs to their stock behaviour.

That boundary is worth drawing early, because it separates three different products that all get recommended to the same person. A dialog enhancer shortens the act of picking a destination. A shelf app holds files during a drag so the pointer can be released while navigating. A rule engine moves files after the fact, on a schedule or on a folder event. The three do not overlap, and the right one depends on where the hand actually stops.

Picking the wrong category is the common failure. Someone whose real problem is a Downloads folder with four thousand items in it will not be helped by faster dialogs, because the files were already saved. Someone who saves into the same three folders all day, from twelve different applications, gets a measurable result on the first afternoon. Default Folder X belongs squarely in the first category, and the setup steps below assume that is the problem being solved.

Step one is the price and the licence shape

Both are knowable before installing anything. The product page lists version 6.3, support for macOS 10.13 through 27, native operation on Intel and Apple Silicon, and a 30 day trial. A single user licence is $39.95, and buying two or more brings the price to $34.95 each. Educational discounts are offered separately.

The part that surprises people is the upgrade fee. The FAQ states that licences purchased before March 1, 2023 require a paid upgrade to version 6.x: $9.95 for a licence bought after September 1, 2022, and $19.95 for anything older. Entering the old licence number in the General tab of the version 6 settings reports whether the upgrade applies.

Counting licences works differently from most Mac utilities. They are single user rather than single machine, so one person with a laptop and a desktop needs one licence, not two. A two person studio needs two.

Item	Value
Current version	6.3
macOS supported	10.13 through 27
Trial	30 days
Single user licence	$39.95
Two or more	$34.95 each
Upgrade to 6.x	$9.95 or $19.95
Counted per	person, not per machine

Older systems are handled by older builds. Version 5.6.6 covers macOS 10.10 through 10.12, and 5.7.8 is the final version 5 release, which does not support macOS 14 or later. Checking the installed macOS version first avoids downloading the wrong build.

Step two is deciding about the screen recording permission

The first prompt after installation asks for screen recording access, which reads alarmingly for a file utility. The stated reason is mechanical. In some situations the tool has to operate a menu inside a file dialog, and to keep that menu from flashing on screen it captures an image of the dialog and displays it in front for a fraction of a second. The same image is used to detect whether the dialog is in Dark Mode, since no system interface reports that. According to the FAQ, the capture is held in RAM, never written to a file, and destroyed immediately after use.

There are two ways forward. Granting the permission in System Settings under Privacy and Security is the straightforward one. Declining it and still running the application is also supported, through a command in Terminal:

defaults write com.stclairsoft.DefaultFolderX5 launchWithoutScreenRecordingPermission 1

With that set, the application launches and works, but the menus it operates stay visible and a yellow window appears in place of the concealing screenshot. Nothing breaks. The interface simply flickers at those moments.

This matters more on a managed Mac than on a personal one. If screen recording permissions are centrally restricted, that escape hatch decides whether the tool is usable at all, and it is cheaper to establish that before paying for a licence.

Step three is the default folders, before the favourites

The core of the product is memory of locations. A folder can be remembered per application, so that a Save dialog opens where the last file went, or an explicit default folder can be set so that every dialog in that application starts in one place. Recent folders, favourites, and currently open Finder windows are all reachable from hierarchical menus in the dialog toolbar and the menu bar icon.

Restraint pays here. Setting defaults for three applications and stopping is enough for a first week. The right three are the ones whose output location never changes: the screenshot utility, the invoicing application, the video exporter. Applications where the destination changes per project should be left alone, because a wrong default costs more attention than no default at all. Those are served well by the recent folders list instead.

Favourites come after defaults, not before. Done in the other order, the favourites list and the per application defaults disagree, and the dialog that opens somewhere unexpected cannot be traced to either one. Adding favourites only for the locations that the defaults failed to cover also keeps the list short enough to read, which is the whole point of a favourites list.

Step four is two keyboard shortcuts, not ten

Keyboard access is where this class of tool becomes habitual. Command Shift Space opens a quick search window, and typing a few characters of a file or folder name brings up recently used items. Favourite folders can each carry their own shortcut, and every binding is configurable.

The collision to plan for is with Spotlight, which occupies Command Space. Two searches one modifier apart will be confused unless each has a stated job. A workable split: the system search handles launching applications, calculations, and unit conversions, while the tool search handles files and folders whose names are already known. Written down once, that division survives; left implicit, both get tried at random.

Adding more bindings is better done after two weeks of normal work. Ten folder shortcuts created during the first enthusiastic hour will mostly be forgotten, and the forgotten ones still occupy key combinations that something else could have used. The bindings that stick are the ones added in response to an actual repeated annoyance.

Step five is how far to take the Finder side

The features extend past the dialog. A Finder window that is already open can be clicked to save into that location. Items dragged to a drawer below a Finder window stay within reach for later. Items dropped on the menu bar icon can be filed through a menu. Inside a dialog, existing files can be renamed, duplicated, inspected, or deleted, and recently closed Finder windows can be reopened. The filename field in Save dialogs is also given more room, which requires no setting at all.

Turning all of that on at once blurs which capability produced which result. A better approach is to enable the one that matches a known habit. Someone who always has the destination folder open in Finder before saving should start with click to save. Someone who renames files immediately after saving them should start with renaming inside the dialog. The rest can wait until the first two are automatic.

The features worth leaving switched off

Not every capability earns a place in a daily routine, and deciding in advance which ones to skip is part of the setup. Two are commonly enabled and rarely used well.

The first is deep favourite hierarchies. Nested favourites look tidy in a menu and then require the same mental navigation that browsing the folder tree required, with the added cost of remembering which branch of the menu holds which project. Keeping favourites flat, with at most eight entries, preserves the advantage that made the list worth having.

The second is remembering a folder for every application that ever saved a file. The per application memory is useful where output is predictable and actively harmful where it is not, because a stale default sends a file to last month's project folder without any visible warning. A file saved to the wrong place is harder to notice than a dialog that opened in the wrong place, since the second is visible at the time and the first is discovered a week later.

There is a third setting that deserves a deliberate choice rather than a default: whether the dialog reselects the last file that was opened. For a workflow that reopens the same document repeatedly this removes a step. For a workflow that opens a different file each time, a preselected name in the field is a small risk of overwriting, and the safer choice is to leave it off.

A reasonable rule for all three is to leave a feature off until its absence is noticed. Features enabled speculatively are indistinguishable from bugs when the behaviour turns out to be surprising, because nobody remembers switching them on.

Where the setup breaks, and how to tell quickly

Three situations account for most reports that the tool stopped working. Applications with strict sandboxing may show the enhanced dialog while failing to remember folders. Applications that draw their own file browser instead of using the system dialog offer nothing to attach to, so nothing changes. And a major macOS upgrade can alter dialog internals, which introduces a waiting period until a compatible build ships.

A two step check separates these without testing every application. Open a Save dialog in a stock application such as TextEdit. If folder memory works there, the problem belongs to the specific application, and no amount of settings will change it. If it fails there too, the cause is the permission grant or the build version, both of which are quick to verify. Comparisons of how different file tools behave under these constraints are collected on the Compared with other file managers page.

What to change first

Confirm the licence arithmetic, then install, grant or decline screen recording deliberately, set default folders for exactly three applications, and stop. Add favourites and shortcuts only where the first week produced a repeated annoyance, because that is the only evidence that distinguishes a useful setting from a forgotten one.

If the count of interruptions is dominated by switching between a file browser and a separate terminal rather than by picking destinations, a faster dialog will not reach it. What Atriens keeps in a single window is listed on the Features page, and the Pricing page covers the cost side.