Batching files for a single upload on a Mac

An upload form wants five files, and they live in five different places. The invoice is in Documents, two photos are in a Photos export, a spreadsheet is in Downloads, and the last one is an attachment still sitting in Mail. You have to feed all of them into one file picker, and the picker only lets you browse one folder at a time.

Gathering scattered files into a single upload is a common chore that the Mac makes clumsier than it needs to be. The upload itself is one action. The collecting beforehand is where the time goes, and where files get missed.

Why one upload becomes many trips

Most upload buttons open a standard Open dialog. You can select several files at once, but only from inside the same folder. The moment your files are spread across different folders, that single selection breaks down, and you fall into one of two slow patterns.

The first is uploading in rounds. You add the files from Downloads, then click the button again and add the ones from Documents, then again for the Mail attachment you had to save first. Some forms allow this. Many do not, because they expect one selection and then a submit.

The second pattern is pre-collecting. You make a temporary folder, drag every file into it from all those places, then upload from that one folder and delete it afterward. It works, but it means creating and cleaning up a folder you did not really want, and it still involves visiting each source location to fetch its file.

The hidden step: saving things out first

Some of the files are not even loose yet. The Mail attachment has to be saved before you can upload it. A photo you want might still be inside the Photos library, which does not expose plain files in Finder. A capture you just took is on the desktop under a timestamped name. Before you can batch anything, you have to turn each source into a file sitting in a folder, which adds its own small errands to the front of the job.

By the time you have everything in one place, you have opened four or five apps, saved a couple of things out, and probably lost track of whether you got all of them. Missing one file means starting the upload over, or worse, sending an incomplete set without noticing.

Collect once, on a shelf

Ledge gives you a place to gather files as you find them, without a temporary folder. The shelf drops down from the notch at the top of the screen, and anything you drag up to the notch lands there and stays. So you collect over time, from wherever the files are, and they all pile up in the same visible spot.

Working through the sources, you drag the invoice up from Documents, the spreadsheet up from Downloads, the saved attachment up from wherever you put it, and each photo up as you export it. They can come from different apps and different folders. The shelf does not care where a file started. It just holds each one until the set is complete.

Because the shelf sits at the top centre of the screen and never gets covered by a window, you can see the collection growing. That visibility matters for batching, because the main failure is not knowing whether you have everything. Here the pile is in front of you, so you can count it before you commit.

Sending the whole set at once

When the shelf holds everything, open the upload form, click its button or focus the drop zone, and drag the files off the shelf together into it. One motion, one upload, the full set. You did not make a throwaway folder, and you did not upload in rounds hoping the form would accept a second batch.

If the form is the kind you drop files onto rather than browse for, the shelf suits it directly. Drag the group from the shelf into the drop zone and they upload as files, which is what the form expects. The hand-off matches the destination: an upload area receives an upload, the same way dropping a single file into a chat window uploads it there.

That matching is the quiet advantage. The same file, thrown at different destinations, arrives in the right form each time. Into an upload zone or a chat it uploads. Into a Finder folder it moves as a file. Onto a terminal it arrives as a path. You gather once and let each destination take the version it can use.

After the upload

Once the set is sent, clear the shelf and it is empty again, ready for the next batch. There was no temporary folder to delete and no leftover copies scattered around to tidy up. The files went from their scattered homes, through one visible holding spot, into the form, and that is the whole trail.

The shelf opens with a keyboard shortcut or a click on the notch and stays out of the way in the menu bar otherwise. Nothing leaves the Mac in the process. The files sit locally on the shelf, with no account and no cloud step, and the only upload that happens is the one you start yourself when you drop the set into the form.

Batching files for an upload is really two jobs stitched together: gather, then send. The sending was always quick. Give the gathering a single place to happen, where you can watch the set come together before you commit, and the whole chore shrinks to collecting as you go and dropping the finished pile in at the end.