Turn a file into a link, a path, or an upload on demand

A file on a Mac is not one thing. It looks like a single icon, but the moment you try to move it somewhere, it has to become a specific kind of object: a path, a link, an upload, or plain text. The same document is all of these at different moments, and which one you need depends entirely on where it is going. Getting the right one on demand, without a pile of manual steps, is the whole trick to moving files quickly.

Here is what those forms are, why you keep needing to switch between them, and how to make the switch happen at the moment of the drop instead of before it.

The forms a file can take

Start with the file itself. On disk it is bytes in a folder, and it has a location, which is its path. When you copy a file in Finder, you are working with the file. When you copy its path, you are working with a string that says where the file lives. These are not the same, and different destinations want different ones.

A terminal wants the path. Commands operate on locations, so pasting a path lets you run something against the file without navigating to it. A chat app or an email wants the file uploaded, so the bytes travel to the other person. A note or a plain text field often wants text: the name, the path, or a link written out as characters. A browser bookmark or a saved shortcut wants a link, which on a Mac can be stored as a webloc, a saved shortcut file you can double-click to reopen.

One document, four jobs. The reason moving files feels fiddly is that you are constantly converting the document from one of these forms into another, by hand, before you send it.

The manual way to convert, and why it wears on you

Each conversion has a known trick, and none of them is hard on its own.

To get a path, you right-click the file, hold Option, and choose copy as pathname, then paste it wherever you need the location. To get a file into a chat, you often save an attachment to the desktop first so there is a concrete file to drag in. To turn a web address into plain text, you paste it and then use paste-and-match-style to strip the link. To save a link as something you can reopen later, you drag the address bar icon to the desktop and get a webloc.

Every one of these works. The cost is that you have to remember which trick matches which destination, and you have to do it before you send, while you are still holding the idea of where the file is headed. Multiply that by every file you touch in a day and it becomes a low background hum of small chores.

The better model is to defer the conversion until the last possible moment, the drop itself, and let the destination decide the form.

Converting at the moment of the drop

This is what Ledge does with the hand-off. You drag a file, folder, image, or link up to a shelf at the top of the screen and let go. It waits there in one neutral state. The conversion does not happen when you put it on the shelf; it happens when you take it off, based on where it lands.

Drop it on a terminal and it becomes the path, pasted as text a command can use. Drop it on a chat app and it becomes an upload, the actual bytes sent. Drop it on a Finder window and it stays the file, moved to that folder. Drop it on a text field and it becomes plain text. Drag a link off the shelf into a place that saves shortcuts and it becomes a webloc. The same item on the shelf turns into whatever the target needs, on demand, without you choosing a representation up front.

That phrase, on demand, is the point. You do not decide that this file is a path or a link while it is sitting on the shelf. You keep it as a file, and its form is resolved at the instant it lands somewhere, which means one thing on the shelf can serve four destinations across an afternoon.

Where this saves the most time

The switching is worth the most when the same file goes to several places in a row. Say you have a build artefact you need to reference on the command line, share in a channel, and file in a folder. Put it on the shelf once. Drag it to the terminal and you get the path. Drag it to the chat and it uploads. Drag it to the folder and it moves. Three forms, one source, no right-click menus in between.

It also removes a class of quiet mistakes. You stop pasting a file reference into a terminal that wanted a path. You stop posting a link to a location only you can open when you meant to share the file. The destination is what decides, so the mismatch has fewer ways to happen.

None of this touches the network. The conversions are local, there is no account, and the file does not leave the Mac at any point in the hand-off. The shelf lives in the menu bar with no Dock icon, opens with Option and Space or a click at the top of the screen, and works the same on Macs with a notch and without one.

Treated this way, a file stops being a fixed object you have to prepare and becomes something closer to raw material. You set it down once, and it takes the shape of a path, a link, an upload, or plain text only when it arrives somewhere that needs that shape.