250: Requested File Action OkayFTP reply code 250 is the general success response for file and directory operations. You will see it after CWD (change directory), DELE (delete file), RMD (remove directory), RNTO (rename to — the second half of a rename), MKD (make directory — though 257 is more common), and other file-system-level commands. Code 250 confirms the operation was performed on the server's filesystem. It is the file-operation equivalent of 200 (which confirms protocol-level commands). The response text usually includes a brief confirmation like '250 Directory successfully changed' or '250 Delete operation successful.'
250 Requested File Action Okay220 ftp.example.com FTP server ready
USER alice
331 Password required
PASS ****
230 User alice logged in
CWD /uploads/2026
250 Directory successfully changed
DELE old_report.pdf
250 Delete operation successfulCode 250 is a success response. The requested file or directory operation was completed. Continue with your next operation.
After CWD, send PWD to confirm the current directory. After DELE, send LIST to confirm the file was removed. After MKD/RMD, send LIST to confirm the directory change.
The client sent CWD /path/to/directory and the server confirmed the working directory was changed. Subsequent LIST and file operations will use the new directory.
The client sent DELE filename and the server removed the file from the filesystem. This operation is permanent and cannot be undone.
The client sent RNFR (rename from) followed by RNTO (rename to) and the server renamed the file. Code 250 appears after the RNTO command.
The client sent RMD to remove a directory. The server confirmed the directory was deleted. The directory must have been empty for RMD to succeed.
The FTP command was understood and executed successfully.
The directory was created or the current directory path is being returned.
The server is waiting for additional information to complete the requested action.
The file or directory operation failed. The path does not exist, or access is denied.
| Specification | Section |
|---|---|
| RFC 959 | RFC 959 §4.2 |
This reference was compiled from official RFCs, protocol specifications, and hands-on troubleshooting experience. AI tools were used primarily for formatting and organizing the content on the page.