Dropzone alternative: a radial menu for file actions on Mac

Dropzone, by Aptonic, is one of the longest-running utilities on the Mac. It has earned its place. The premise is simple and good: pick up a file, drag it to a grid that appears at the top of your screen, drop it on a destination — upload it to S3, post it to Imgur, copy it to a folder, AirDrop it to a phone, run a custom Ruby script over it. The grid is the action surface; dragging is the verb.

A radial menu uses the same verb. You hold a trigger, a ring of wedges appears, you drop a file on one. The geometry is the difference. Dropzone's grid lives at the screen edge. Swik's wedges open under your cursor. Same ergonomic — drag once to choose an action — but the throw is shorter.

This post is the honest split between the two. What Dropzone wins. What a radial menu wins. And how to tell which side of the line your daily drags fall on.

The geometry argument

Dropzone is a grid. Grids are good at one thing radial menus are not: they scale to dozens of items without losing labels. You can stack twenty actions in a Dropzone grid and read every name. A radial menu starts to suffer past about ten wedges because the angles get cramped. If your file workflow has a long tail of named destinations — three S3 buckets, two SFTP servers, four shared folders, a custom upload script, and a couple of share targets — a grid is the right shape for that list.

The cost of a grid is its location. Dropzone's grid appears at the top of your screen on demand. That is fine when your file is already near the top. It is a longer haul when your file is in a Finder window in the bottom-right corner and you have to drag it up and across to the menu bar before you can drop. A pie menu dodges that by appearing at your pointer. The drag never travels further than the radius of the menu.

Most people who use Dropzone heavily do not feel the distance because the muscle memory is a decade old. People who try to adopt it fresh in 2026 do feel it, and it is the most common reason they bounce.

What Dropzone is genuinely better at

Do not move off Dropzone for any of this. These are the things it does that no radial menu will, and they are not on the Swik roadmap because they are different products:

• Scripted upload destinations. Amazon S3, SFTP and FTP, Imgur — drop a file, get a URL on your clipboard. There is a progress UI, retry handling, and credentials management. This is real software, not a shortcut.
• Custom actions in Ruby and Python. Dropzone exposes a small SDK for writing your own destinations. If you have an internal tool that takes a file and does something with it, you can wrap it in a grid tile.
• The action library. Years of community-built actions — link shorteners, image resizers, video downloaders, share targets. The library is part of the value.
• DropBar / shelf. A holding area for files you are about to do something with. Drag files in, do another task, drag them out somewhere else. A radial menu is a verb, not a shelf, and does not try to be one.
• Multiple grids. Different grids for different jobs. Swik has profiles, but they swap whole menus, not workspace surfaces.
• Scale of named items. Twenty labelled tiles fit in a grid. Twenty labelled wedges do not fit in a circle.

If you ship screenshots to S3 every day, push assets over SFTP, or maintain custom Ruby actions, Dropzone is a tool you keep. None of the rest of this post is trying to talk you out of it.

What a radial menu is genuinely better at

Now the other half. Most Dropzone users I have watched in person use a small subset of the grid hundreds of times a day — usually three or four tiles — and the long tail of advanced destinations gets touched once a week. That hot subset is what a radial menu is shaped to handle.

• Drag-to-open at the cursor. Hold the trigger, the wedges appear where your hand already is, drop the file on the app you want to open it with. No long throw to the menu bar.
• "Open this file in that app" cases. Image to Photoshop. PDF to Preview. Markdown to your editor. Log file to a viewer. These are the everyday drags, and they happen everywhere on screen, not always near the top.
• One launcher for files and apps. Swik's wedges launch apps, run Apple Shortcuts, paste clipboard items, insert emoji, and accept dragged files. Dropzone is a file-action grid only — you still need a separate launcher for the rest.
• Mouse-hand triggering. Bind Swik to a mouse side button and the menu opens without leaving the mouse. Dropzone usually expects you to drag toward a fixed screen edge, which is a hand-and-arm motion.
• Context profiles. Different menus on home Wi-Fi versus office Wi-Fi, or with an external display attached. Dropzone's grids are static.
• Apple Shortcuts on a wedge. Anything you can build in Shortcuts.app — including file-receiving shortcuts — can sit on a wedge and run in one flick.

Side by side

Where the line actually falls

The clearest way to decide is to look at what your file drags do, not what the tool advertises. Two questions are usually enough.

First: do most of your drags end at a network destination? An S3 bucket, an SFTP server, Imgur, Dropbox, a custom upload endpoint. If yes, you need scripted destinations with credentials and progress. That is Dropzone, and a radial menu does not replace it.

Second: do most of your drags end at an app? Image into Photoshop. PDF into Preview. CSV into your spreadsheet. Log file into your editor. If yes, you are dragging into apps you already have on your Dock, and the only thing you actually need is a faster way to aim the drop. That is a wedge. The drag is shorter and the menu is local to your hand.

Most people are some of both. The split tends to be 80/20 in favour of "drop into apps" and 20/80 in favour of "upload to a service." If your split looks like the first number, a radial menu covers the bulk of your day; keep Dropzone in reserve for the upload work.

The "run both" setup

For people who genuinely use Dropzone's upload features, the cleanest setup is to keep both tools and let each handle the work it is shaped for:

• Dropzone for drag-to-network. S3, SFTP, Imgur, custom Ruby actions, link shorteners. Triggered by dragging toward the top of the screen, the way it has always worked.
• Swik on a mouse side button or function key. App launches, drag-to-open files into apps, clipboard ring, emoji, Apple Shortcuts. Triggered without moving your hand off the mouse.

There is no conflict because there is no overlap. Dropzone's strength is named scripted destinations. Swik's strength is reflex actions at your cursor. They are both legitimate drag-action tools — they just live at different distances.

When to stay on Dropzone alone

Stay on Dropzone as your only file-action tool if:

• You upload to S3, SFTP, or Imgur multiple times a day.
• You maintain custom Ruby or Python actions for internal tools.
• You rely on DropBar as a holding shelf between tasks.
• You have ten or more named destinations you genuinely use weekly.
• The throw distance to the menu bar is not something you notice.

When to add a radial menu

Add Swik alongside Dropzone — or instead of it, if your drags are mostly app-bound — when:

• Most of your drags end inside an app rather than at a network destination.
• You feel the distance from your file to the top of the screen.
• You want the same launcher to handle apps, files, clipboard, and Shortcuts.
• You work mouse-in-hand for long stretches and want a side-button trigger.
• You want one $9 one-time price for the reflex half of the job.

Dropzone's grid is a destination. A radial menu is an aim. If most of your day looks like the first, keep dragging upward. If most of it looks like the second, the wedges should come to you.