Move files to and from a server
3 minute read · FTP / SFTP
Use the file-transfer workspace to browse a server and move selected files. Choose the protocol the server actually supports: FTP, FTPS or SFTP.
- Choose the transport and destination
- Transfer a small example first
- Keep file operations distinct
- Organize a transfer session
Choose the transport and destination
Select FTP, FTPS or SFTP according to the server. SFTP uses SSH authentication, including key/passphrase or Vault references. FTP/FTPS use their configured transport and credentials. A saved SSH host can also be used for SFTP. Reuse the saved host or transfer profile with the access permissions granted to that account.
Connect and confirm the remote path before uploading. Use breadcrumbs, path entry or the directory tree to navigate, then search/sort/select the intended files. Keep the local source and remote destination visible so similarly named folders are not confused.
Transfer a small example first
- Choose a harmless local sample file and a permitted remote test directory.
- Upload it through the supported file selection or drag-and-drop flow.
- Watch progress until completion, then refresh and inspect its remote size/name.
- Download that file to a separate local destination and inspect the contents.
- Remove the remote sample only when that cleanup is authorized.
The transfer being queued or started does not mean it finished. Background work can fail or be cancelled. For a large folder, inspect progress and errors before repeating the entire upload, since some files may already exist remotely.
Keep file operations distinct
Create directory, rename/move, copy, cut/paste and delete change remote state. Closing a tab only closes a session. Recursive deletion is destructive and must not be used merely to reset a file-browser view. Server/protocol capabilities can differ; a missing operation should be reported rather than silently emulated in a surprising way.
Saved credentials are resolved inside Vortex for an authorized operation. Remote file contents and downloaded exports can still contain private values. Remote editing and permissions covers the tracked save/upload path.
Organize a transfer session
Use a session for each destination you need to compare. Navigate with breadcrumbs, path entry or the directory tree; sort and select the intended files before a transfer. Confirm the target directory rather than relying on a similarly named folder in another session.
Try one harmless text file before transferring a whole directory. Watch progress, cancellation and errors, then refresh the destination and read the transferred file. Drag-and-drop uploads still write remote files; they are not merely opening a local preview. Avoid assuming that a cancelled multi-file transfer removed files already uploaded.
Copy, move, rename and delete have different effects. Check overwrite prompts and the selected remote path, particularly for recursive operations. Closing a session should not delete its saved connection or remote content. Keep temporary exports and downloaded credentials out of public repositories. Remote editing and permissions explains the save/upload round trip.
Related guides: editing a remote file, server identity.