Dropover: the setup order that holds up

Most people who look up how to set up Dropover are not stuck on the interface. They installed it, shook the pointer a few times, dragged something out, found the original file had moved rather than copied, and now want to know which settings decide that behaviour before building a habit on top of it. That is the right instinct. There are seven documented ways to open a shelf and two separate rules for what happens when items leave one, and neither is discoverable by clicking around.

What follows is an order to decide things in, based on what the maker's own pages state. The whole list takes about fifteen minutes to work through once, and going through it in this sequence avoids reopening Settings later.

Two facts that settle it before any setting

Two lines decide whether the rest of this applies.

The first is the system requirement. The Mac App Store listing states that Dropover requires macOS 13.0 or later. That matters for anyone keeping an older Mac in service for a specific job, because no amount of configuration gets around it. Apple documents which machines run which release on the Apple support site.

The second is where it comes from. The FAQ states plainly that Dropover is currently available exclusively through the Mac App Store. On a managed work Mac where App Store installs are restricted, that ends the conversation before any setting is touched. The same page adds that business license seats are not available yet, with a note that they are planned for later in the year. Anyone standardising a team on one shelf app should read that line first rather than last.

Display language belongs in this first pass too. The FAQ lists four languages: English, German, Dutch and Simplified Chinese. The App Store listing shows six, adding Italian and Spanish. Neither list includes Japanese, and the app follows the system's preferred language by default, so a Japanese system will show an English interface. macOS does allow a per app language override, which the maker links to from the same FAQ entry.

Seven ways to open a shelf, and the two worth learning

This is where the setup actually gets decided. Between the overview page and the Pro Tips page, the maker documents these routes:

How the shelf opens	Best suited to
Shake the pointer mid drag	Pulling files out of a browser or an editor
Drop onto the menu bar icon	Files already visible in a Finder window
Drop onto the notch on a MacBook that has one	The same, without aiming at a small icon
A global keyboard shortcut	Opening an empty shelf to fill deliberately
Press ⌥⇧A	Turning the current clipboard into a shelf
open -a Dropover -- /path/to/file	Output from scripts, builds and exports
Folder monitoring	Downloads and screenshots arriving on their own

Seven is too many to internalise at once, and nobody needs all of them. A working day usually contains two moments where the hands stop: dragging something out of an application, and dealing with files that a command just produced. The shake gesture covers the first. The terminal route covers the second. Learning those two and ignoring the rest until a real need appears is what makes the habit stick.

The shake gesture needs one companion setting on day one. Settings includes both a shake sensitivity control and an app exclusion list, and the exclusion list is the one that prevents an early bad impression. Drawing applications, notation software and anything else that involves small rapid pointer movements will open shelves that were never wanted. Filling in those exclusions before the first full day of work removes the single most common reason people conclude the app is not for them.

For files already selected in the Finder, the maker documents a Shortcuts route rather than a contextual menu item: create a shortcut, add the action that gets the selected Finder items, add the action that adds files to a shelf, then assign a keyboard shortcut in the shortcut's details. That is fewer steps in daily use than reaching for any menu.

What happens when a file lands, and when it leaves

This is the part that surprises people, and the FAQ separates it into two distinct events.

Dragging a file from the Finder onto a shelf neither copies nor moves it. The shelf holds a reference. The same page states that dragging files onto a shelf does not upload them either, and that uploads happen only when an upload or sharing action is chosen explicitly. Nothing has happened to the file yet.

The change happens on the way out, and it follows the Finder's rules rather than inventing new ones. Dragging an item off a shelf moves it by default. Holding Option forces a copy, and a plus sign appears over the dragged content to confirm it. The exception is worth memorising: items headed for a different volume or disk are copied by default, and forcing a move in that case means holding Command. An external drive that ends up holding a second copy of everything is this rule, not a bug.

For work where originals must never move, Settings has a switch for it. Under Shelf Interaction, in the advanced section, there is an option to always copy items when dragging out. Turning that on during setup is cheaper than remembering a modifier key several hundred times.

Two smaller behaviours belong to the same group. Holding Command while clicking items in an expanded shelf selects them individually, so only part of a shelf gets dragged out. Holding Shift while dragging items out keeps the shelf available afterwards, which is what makes delivering the same three files to three different places a single collection rather than three.

Add one action, not five

A shelf is built as a work surface rather than a waiting room. The overview page lists image resizing, text extraction, ZIP creation and sending through any app in the macOS Share menu, plus Instant Actions, where dropping files onto an action runs it immediately.

Custom work is supported as well. Scripts can be added from Settings as shell scripts or Automator workflows, they receive the shelf contents as input, and the maker notes that scripts can be tested before use and that a shell script can copy its output to the clipboard. Cloud destinations cover seven services: Dropover Cloud, iCloud Drive, Dropbox, Microsoft OneDrive, Google Drive, AWS S3 and S3 compatible providers, and Imgur. Uploads to Dropover Cloud require no account, and a title, a password, an expiry date and the link type can all be set.

Folder monitoring deserves a decision of its own, because it is the one route that opens shelves without anyone asking. Settings has a Folder Monitoring section where a folder is added and watched, and the documented example is the Downloads folder, with filtering rules so that only screenshots or only certain file types appear. Used on Downloads it removes a genuine chore, since a file that arrives in a browser normally has to be found again before it can be filed. Used on a folder that receives files in bulk it produces a stream of shelves nobody asked for. Adding one watched folder with a filter, rather than two without, is the version of this that survives a busy week.

The restraint matters more than the list. Registering five actions on day one produces five actions nobody remembers. Pick one task that recurs at least three times a week, wire that up, and let it become automatic before adding the second. Exploring every feature is a different activity from deciding a setup.

Shelves that stay, and shelves that go

Without a decision here, shelves accumulate on screen until the app starts to feel like clutter.

Closed shelves are recoverable: up to ten recent shelves can be reopened. That makes closing the safe default, because a shelf shut by mistake is one menu away.

Anything used across several days should be pinned instead. Pinned shelves accept custom titles and stay reachable from the menu bar, which turns them into named project workspaces rather than anonymous floating windows. A shelf that should stay nearby without hovering over the work can be docked to the screen edge by double clicking its edge, dragging it to the edge, or choosing it from the shelf menu.

To empty a shelf and keep using it, hold Option and click its close button. There is no need to drag everything out, close it and create a new one.

One behaviour explains nearly every report of shortcuts not working. Shelf shortcuts such as ⌘K, Space and Delete only fire while a shelf is active. When several shelves are visible, pressing ⌥⇧S numbers them so one can be given focus. Global shortcuts work anytime; shelf shortcuts do not, and that distinction is documented rather than accidental.

The trial decides routes, not payment

The cost model is stated in the maker's FAQ:

Dropover is free to download and includes a fully functional 14-day trial. After the trial ends, you can keep using Dropover with a small limitation: a 3-second wait before interacting with the shelf.

The same page adds that the Pro upgrade is a one time purchase rather than a subscription, and that nothing is charged automatically when the trial ends. The App Store listing prices that in app purchase at $7.99, and using it on several Macs means signing in with the same iCloud account and choosing Restore Purchases.

Because the app keeps working after fourteen days, the payment decision can wait. That makes the trial period useful for something else: deciding which two of the seven routes above are going to be used. A three second delay arriving before those routes are settled reads as friction in the app rather than as a limitation, and that is how a tool that fits gets uninstalled.

The order that gets this done in one sitting

Six decisions, in this sequence.

First, confirm the macOS version and whether the App Store is available. This is eligibility, not preference.

Second, choose two ways to open a shelf. The shake gesture plus the terminal route is a safe pair.

Third, if the shake gesture is one of them, fill in the app exclusion list, starting with anything that involves precise pointer work.

Fourth, decide whether dragging out should move or copy. Work built on shared originals wants the always copy setting.

Fifth, register exactly one custom action, for something already done three times a week.

Sixth, decide which shelves get pinned and which get closed. Closing is safe because the last ten come back.

The FAQ on this site covers the questions that follow the first week, and the comparison page sets shelf apps next to the dual pane and Finder replacement categories, which is the useful frame once the shelf itself is working.

What to change first

Fill in the app exclusion list, then decide the move or copy behaviour. Those two take four minutes and remove the two things most likely to make the shelf feel unreliable. If the count of shelves opened per day stays high, the distance being worked around is the gap between the folder window and the terminal, and closing that gap is what Atriens exists to do.