FTP Error 213: File Status
FTP reply code 213 is returned in response to a SIZE command or a STAT command with a pathname argument. When responding to SIZE, it contains just the file size in bytes — clients use this to set up progress bars and verify transfers completed correctly. When responding to STAT with a path, it includes detailed file information similar to a directory listing (permissions, owner, size, modification date). The SIZE command response (213) is essential for transfer resumption — the client needs to know the current file size to calculate the byte offset for REST.
Status
213 File StatusExample
220 ftp.example.com FTP server ready
USER alice
331 Password required
PASS ****
230 User alice logged in
SIZE archive.zip
213 10485760
MDTM archive.zip
213 20260115142300How to Troubleshoot
Use SIZE to verify transfers
After a file transfer, send SIZE to compare the remote file size with the local file. If the sizes do not match, the transfer may have been interrupted or corrupted.
curl -v ftp://ftp.example.com/file.zip -Q 'SIZE file.zip'
Check MDTM for synchronization
When mirroring files, use MDTM to check modification times. Only download files that have changed since your last sync.
Common Causes
SIZE command response
highThe client sent SIZE to determine the file size before downloading. The 213 response contains the size in bytes as a decimal number. This is used for progress tracking and resume calculations.
MDTM command response
mediumThe client sent MDTM (Modification Time) to check when the file was last modified. The 213 response contains the timestamp in YYYYMMDDHHMMSS format. This is used for mirroring and synchronization.
STAT with pathname
lowThe client sent STAT /path/to/file to get detailed file status without initiating a data connection. The server returns file metadata inline on the control connection.
Related Error Codes
System Status
The server is reporting its system status or listing supported features.
File Status Okay, About to Open Data Connection
The server is ready to transfer the file and is about to open the data connection.
Requested File Action Okay
The file or directory operation was completed successfully.
References
| Specification | Section |
|---|---|
| RFC 959 | RFC 959 §4.2 |
Frequently Asked Questions
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.