Move files to and from a server
4 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.
- Open directly from search
- Choose the transport and destination
- Transfer a small example first
- Keep file operations distinct
- Organize a transfer session
- Saved host form
- Browser and transfer buttons
Open directly from search
Use Vortex Search → FTP / SFTP to find a saved connection by name, host or protocol and open it directly from your project or chat. Saved SSH hosts with SFTP configuration appear here too. The Files tool opens over your existing work and retains its normal connection checks. See Vortex Search.
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.
Saved host form
| Field | Meaning |
|---|---|
| Protocol | FTP, FTPS or SFTP. SFTP uses SSH; it is not FTP with a different label. Use the protocol offered by the server. |
| Name / Tags | Labels used to find the saved connection. |
| Host / Port | Transfer server and its actual listening port. Protocol defaults are only starting values. |
| Username / Password | Credentials for the remote server, independent of Vortex login. |
| SSH key | SFTP key-based authentication when selected. |
| Key source | Private key path, pasted private-key content or a Vault key. |
| Passphrase (optional) | Unlocks an encrypted SSH private key. |
| Upload chunk size (MB) | Optional setting for supported server/file-size constraints. It is a transfer setting, not a total storage allowance. |
| Save / Cancel | Saves the configuration or leaves the unsubmitted form. A saved configuration still needs a successful connection. |
Browser and transfer buttons
| Control | Result |
|---|---|
| Back / Forward | Moves through the folder navigation history. |
| Up | Opens the parent directory. |
| Path | Double-click to edit the remote path directly. Check the resulting folder before uploading. |
| Refresh | Reloads the remote directory listing. |
| Search this folder / Clear search | Filters the current folder view, then clears the query. Do not assume it searches the whole server recursively. |
| Download | Transfers the selected remote item to the chosen local destination. |
| Upload / drop files | Transfers chosen local files to the current remote destination through the supported upload flow. Review replacement prompts. |
| Rename | Changes the selected remote item's name/path. Applications using the previous path may be affected. |
| Delete | Deletes the selected remote item after the applicable confirmation. It does not simply hide it from the list. |
| Properties | Opens available type, size, modification time and permission information. |
| Connection/session close | Closes that working connection. Deleting the saved host is a separate action. |
Inspect transfer completion and refresh the destination. For a critical upload, compare a downloaded copy or the application behavior with the original. See remote editing and permissions.