FlashFXP is a Windows file-transfer client for moving files between a computer and remote servers. It works with FTP, FTP over TLS and SFTP, and it can keep several server profiles in a Site Manager. The two-pane window places local files beside a remote directory so uploads and downloads behave much like copying through a file manager. FlashFXP does not host files or create a server account; the user still needs a reachable server, a protocol, a port and valid credentials.
+
Protocols do not mix
+FTP, FTPS and SFTP can all move the same file, but they establish different connections. SFTP runs through SSH. FTPS keeps the FTP command model and adds TLS, either when the connection begins or after an explicit request. A server configured for SFTP will not accept an FTPS profile merely because both encrypt traffic.
+The Site Manager stores the host, port, login method, initial directory and protocol-specific settings. Saving one profile per endpoint avoids retyping those details, although copying a profile without checking its protocol can preserve the wrong assumptions. A certificate warning in FTPS concerns the TLS identity; an SFTP host-key prompt concerns the SSH server. FlashFXP can remember either decision, so the first fingerprint or certificate should be checked before it becomes trusted.
+
Queues survive pauses
+Dragging several items builds a transfer queue rather than forcing the user to supervise each file. Queue controls can pause work, change order and retry a failed item. Transfer rules can skip selected names, restrict speed or decide what happens when a destination file already exists. Those rules deserve review before a large synchronization because a broad skip pattern can quietly omit files.
+Interrupted transfers may resume when both the server and protocol support the required operation. Resume does not verify that two files with the same size contain the same bytes, and a server can reject it for permissions or policy reasons. FlashFXP reports that failure in the transfer log; repeatedly pressing retry cannot override a remote quota or a read-only directory.
+
FXP skips the PC
+The name comes from FXP, an FTP method that asks one server to send data directly to another. The Windows computer coordinates the commands but does not have to receive and upload the entire payload. This can save local bandwidth when moving a large archive between hosting accounts.
+Both FTP servers must permit site-to-site work. Many administrators disable it because a server could otherwise send data to an unrelated address. Firewalls, NAT devices and FTP-aware proxies can also rewrite the commands or force the data through an unexpected route. A normal upload that works from the PC therefore does not prove that FXP will work between the same two hosts. SFTP is not FXP, so an SSH file server cannot join this particular server-to-server path.
+
Sync needs a boundary
+Directory comparison and synchronization help maintain a website or mirror a folder, but the direction controls what may be replaced or deleted. A local-to-remote job is different from a two-way reconciliation. Time stamps can also differ because servers apply another time zone or preserve modification times differently.
+Before the first automated run, a small test directory exposes permission, case-sensitivity and overwrite behavior. Windows treats many letter-case differences as the same name, while a remote Unix server can treat them as separate files. Scheduled transfers also need saved credentials and a running environment at the scheduled time. FlashFXP can automate the client work, but it cannot repair a sleeping computer, an expired password or a server that no longer accepts the stored encryption method.
