Transfers and files
Use a copy when you want the file in another location while keeping the source. First open the destination folder in the other pane, then select the files or folders you want to send.
On this page
Upload, download or copy
| From → to | Action in the source pane's right-click menu |
|---|---|
| Computer → server | Upload to other pane |
| Server → computer | Download to other pane |
| Server → another server | Copy to other pane |
Right-click the source selection. Upload to other pane sends it to the server folder open on the other side.
- Check the server or computer and the open path in both panes.
- Select the files or folders in the source pane. Choose the action above, or press F8 with that pane focused using the default shortcuts.
- If asked about existing files, decide whether those destination copies should be replaced. A matching name does not mean that the contents are the same.
- Follow the job in Transfers and check its final result before closing the connection or removing the source.
For a server-to-server copy, connect both panes and open the source folder on one and the destination folder on the other. Files and folders can be sent this way. For a first upload or download, follow Your first transfer.
Before sending files with names already at the destination, check Edit > Settings > Transfers > On name conflict: Ask requests your decision, Overwrite allows replacement without that question, and Skip leaves matching files alone. Start with Ask if you want to review replacements. See Everyday settings to change the policy.
For each existing file, Ask offers Overwrite, Create a copy and Skip.
Copies are named file (copy).txt, then file (copy 2).txt and so on, without
replacing existing files. For several conflicts, Apply to all remaining conflicts
reuses your choice; closing the question or pressing Escape skips only the current file.
Files without a conflict transfer without a question.
Pausing, stopping and resuming transfers
Example jobs with some columns hidden. Pause (two bars) and Stop (a square) are at the right of an active row.
Pause keeps what has arrived so far, and Resume carries the job on later in this session. Stop cancels the job; Retry on a stopped job starts it over.
If a transfer reports an error, read it before retrying: wrong permissions, insufficient space or a changed source need attention first. See Troubleshooting.
A paused FTP, FTPS or SFTP upload resumes when FTPeach confirms that neither the source nor the part already on the server has changed; otherwise it starts again. WebDAV uploads, including folder uploads, do not offer Pause because they cannot continue a partly uploaded file.
Resuming a paused transfer does not ask again whether to replace the file there: it keeps the answer given when the transfer started.
When the connection to a server is lost, the transfers it cut off can be retried once the pane is connected again to the same server with the same account. Until then their Retry button is unavailable.
Before a full exit or restart
If FTPeach is still in the system tray, reopen it and check Transfers before starting another copy of the same job. The instructions below concern a full application exit, not just a hidden window.
Finish important transfers before exiting FTPeach or restarting Windows. The transfer queue does not return in a fresh application process. A paused upload is not a saved job for the next launch: keep its server connection open if you want to resume it. After exiting, select the source again and start a new upload. A download can carry on after an exit; see Interrupted downloads.
When an upload is interrupted
Stopping an upload never deletes a file that was already on the server under the same name. The old file stays in place until the new one has fully arrived.
If another program saves over a file while it uploads, the upload ends with an error saying the file changed, and the file already on the server stays as it was; upload it again to send the new version.
Stopping a folder upload keeps the files that already reached the server. Cleanup targets only its own temporary upload file; a server that refuses cleanup or cannot be reached can leave that temporary file behind.
Transfer notifications
Enable Edit > Settings > Transfers > Notify when transfers finish to receive system notifications while the FTPeach window is not focused.
Errors are reported while other transfers continue; errors arriving close together share one notification. When the queue finishes, any successfully transferred files are counted in a separate notification. If errors remain, its title still indicates an error. Open Transfers to read the reason beside each failed job.
A retry replaces the previous attempt's result. If it succeeds, the final total counts that success without repeating the old error. Paused jobs hold the final total until they resume or are stopped; they do not hold back errors from other jobs.
If a folder transfer fails part way through, the successful total still includes the files it delivered. The error notification does not claim a number of files that failed.
Interrupted downloads
To finish an interrupted download, even after exiting FTPeach, reconnect, select the same server file and download it to the same local folder and filename. It carries on from where it stopped only when the server, account, path, size and version still match. A changed or unavailable size or version starts a new download. This compares the server's metadata, not the complete file contents: a same-size change with the same reported version can go unnoticed. See resume limits.
If a download does not finish, a file you already had under that name is kept unchanged.
Before a downloaded file takes its name, FTPeach asks the server again for its size and version. If they changed while the file was downloading, it reports that, keeps the file you had and starts the next try from the beginning. When the server gives no version, only the size is compared, and a change of the same size can go unnoticed. If the server does not answer the second time, the downloaded file is kept and the log says the check could not be made.
A download that fails before receiving anything, such as one of a file deleted on the server, leaves nothing beside the destination.
Downloaded files
On NTFS, FTPeach writes a Windows origin mark to downloaded files. It identifies local-network servers as intranet and other servers as internet. The mark records the server address without your user name or password and stays with the file when it is renamed. A drive formatted as FAT32 or exFAT, as many USB sticks are, cannot keep this mark. See download security limits.
Copying files and folders
To copy within your computer, keep both panes on Computer, open the source and destination folders, select the entries and press F8. You can also use Ctrl+C, open the destination and press Ctrl+V. To create a destination folder first, right-click empty space and choose New Folder, or press F7.
Local file copies appear in Transfers while running and keep their final result. A failed copy can be retried from its row.
With overwrite handling set to Ask, merging into an existing folder asks separately for permission to replace matching files inside it. Approving other files in the same selection does not approve the folder's contents.
A file cannot replace a folder, or a folder a file. The message identifies the skipped names; other selected files can still be copied.
Renaming and moving
To rename, select one entry, press F2, type the new name and press Enter. To move, right-click the selection and choose Move to folder…, then choose the destination folder. Alternatively, press Ctrl+X, open the destination on the same computer or server connection and press Ctrl+V.
When renaming or moving finds another file with the same name, FTPeach asks before replacing it. If several people are editing the same server folder, coordinate changes: FTP cannot guarantee that a new file created by another client during the rename will be preserved. See the file operation guarantees for details.
When a cut selection includes files you skip, it stays available to paste after the other files move.
Files can be moved only on your computer or within one server connection. Between your computer and a server, or between two servers, FTPeach refuses the move and changes nothing. Copy the files instead.
Delete files and folders
Select the entries, right-click and choose Delete. Read the confirmation and check the location and selection before approving it. Local files normally go to the Recycle Bin. If that location has no Recycle Bin, FTPeach asks again before permanently deleting them; cancelling keeps the files.



