Skip to content

Background transfers

Large copies, moves, deletes, and downloads don't have to hold up your work. Peach Commander can run them in the background and collect them all in one place: the Background Transfer Manager. From there you watch each job's progress and transfer speed, pause or resume it, cancel it, or line jobs up to start later. Because a background job runs on its own, it never stops you from browsing, opening files, or starting the next transfer.

How to

  1. Start a copy, move, delete, or download and choose to run it in the background. The job appears in the Background Transfer Manager.
  2. Open the manager any time from Commands ▸ Background Transfer Manager… (or press Cmd+Shift+B).
  3. Each job shows a title, a progress bar, and a live line with files done, bytes transferred, and current speed.
  4. Use the per-job buttons to Pause, Resume, or Cancel while a job is running.
  5. For jobs you added but haven't started yet (held jobs), click Start on the job, or Start All to launch the whole waiting list at once.
  6. When everything you care about has finished, click Clear Finished to tidy the list.

The Background Transfer Manager listing active and waiting jobs with progress bars and Pause, Resume, and Cancel buttons.

Each transfer is a row you can pause, resume, or cancel independently.

Shortcuts

Action Shortcut
Open the Background Transfer Manager Cmd+Shift+B

Tips

  • Limit the speed. To keep a big transfer from saturating your connection or disk, set a speed limit in the copy dialog before you start the job. The manager then shows the throttled rate live.
  • Queue for later. Held jobs sit in the list without running until you press Start (or Start All), so you can stage several transfers and kick them off together.
  • Run several at once. Jobs run independently, so you can pause one while another keeps going.

Notes

Because a background job runs without you watching, it can't stop to ask questions. If a file already exists at the destination, the background job overwrites it; if an individual item can't be transferred, that item is skipped and the job keeps going. When the job finishes, any skipped items are collected in an error log so you can review exactly what went wrong.