A workflow for handing off design assets on a Mac

Design hand-off is the moment a finished screen leaves your hands and becomes someone else’s problem to build. On a Mac that moment usually involves a pile of exported files, a chat window, a shared folder, and a short walk across three or four apps that do not talk to each other. The assets are ready; the friction is entirely in moving them.

This post is about that last stretch: getting a clean set of design assets from your export folder to the person or place that needs them, without losing track of what went where.

What a hand-off actually contains

A single hand-off is rarely one file. A button might ship as a set of PNGs at one, two, and three times scale. An icon goes out as an SVG for the web and a PDF for print. A screen mockup travels as a flat image for review and a layered source for anyone who wants to edit it. Add a font file, a colour reference, and a short note, and one quick hand-off is already eight or nine separate things.

Those things do not all live in the same folder. Exports land in Downloads or in a per-project export folder. The source file sits in your documents. The font came from somewhere else entirely. Gathering them is the first tax you pay, and it is the one most likely to go wrong, because a hand-off that is missing the retina asset looks complete right up until the developer opens it.

The scattered-source problem

The usual approach is to open a Finder window, make a new folder, and drag each asset into it one at a time, switching windows as you go. It works, but it is slow and it breaks your attention. Every switch between the export folder, the source folder, and the chat window is a chance to forget the file you were about to grab.

Drag and drop is supposed to help here, and it does inside a single window. Across windows it asks too much: you hold the file, hunt for the target behind other windows, and keep the mouse button pressed the whole way. If the target is not open yet, the drag fails and you start over. There is nowhere to set an asset down while you go and find the next one.

That missing halfway point is the whole problem. You need a place to stage the set: somewhere to drop the retina PNG, then the SVG, then the source file, gathering them from wherever they happen to live, before you decide where the whole batch is going.

A staging spot at the top of the screen

Ledge gives you that spot by turning the notch, or the top centre of any Mac screen, into a shelf. You drag an asset up toward the notch and let go, and it lands there and stays. You do this once per file, from whichever folder or app it lives in. The export folder, the source document, the font: each one goes up to the same shelf, and none of it needs a target window open yet.

Once the set is gathered, you send it where it belongs. This is where the useful part shows up. When you drag the batch onto a chat app, the files upload as attachments, which is what a developer waiting in a channel actually wants. When you drop the same batch into a Finder folder, the files move there. When you drop a single asset onto a text field, its path or name arrives as plain text. You assemble the set once and then hand it to each destination in the form that destination can use.

Because the shelf sits at a fixed point you already glance at for the clock, your hand learns where it is. Gathering nine files becomes nine short drags to one known spot, rather than nine round trips between windows.

Keeping versions straight

The other failure in design hand-off is sending last week’s asset. Files named button.png, button-final.png, and button-final-2.png all look plausible in a list, and the wrong one uploads without complaint.

Staging helps here in a quiet way. When the assets sit together on the shelf before they go anywhere, you get one last look at the set as a set. It is easier to notice that you grabbed the flat mockup but not the layered source when both are meant to be there and only one is present. The shelf is a checkpoint, not a filing system, and that is the right size for a hand-off: hold the batch for a minute, confirm it, send it, clear it.

A repeatable order of operations

A hand-off goes smoother when it follows the same shape every time:

1. Export everything first, so the assets exist before you start moving them.
2. Gather the full set onto the shelf, pulling from the export folder, the source folder, and anywhere else, one drag each.
3. Look at the set and confirm nothing is missing.
4. Send it to its destination in one motion, letting each app receive the version it can use.
5. Clear the shelf so the next hand-off starts empty.

None of this requires a new file format or a shared service. The assets stay on your Mac the entire time; nothing is uploaded except the moment you choose to send it to a chat app or a folder. What changes is that the scattered middle of the process, the part where files go missing and windows pile up, gets a single, steady place to happen.

Design work is judged on the final pixels, but it is delivered through this unglamorous last step. Giving the hand-off a staging spot does not make the assets better. It makes them arrive complete, in the right form, the first time.