ASCII vs Binary and Encoding Corruption

Some transfer failures announce themselves. This family does not. The file arrives, the size looks plausible, and the job reports success. Somewhere downstream a program chokes on a character that was never in the original. ASCII mode mangled a binary, a line ending changed on the way through, or an encoding was assumed wrong. These are the silent corruptions that have bitten every administrator at least once.

This series makes once the limit. It covers the ASCII/binary trap and line endings across systems. It explains character encodings for administrators who would rather not become linguists, and filename encoding problems on transfer servers. It covers detecting corruption early instead of downstream. And it gives you the prevention checklist that turns a recurring mystery into a solved problem.

Articles in This Series

• The ASCII/Binary Trap: FTP's Classic Silent Mangler
  Learn what ASCII mode changes and why it exists, how a binary file gets corrupted by it, and the symptoms. See why binary-always is the rule, and where SFTP does and does not save you.
• Line Endings Across Systems: CRLF, LF, and the Files Between
  Learn the two conventions and what breaks when they mix - scripts, imports, checksums. See how to detect and convert with everyday tools, and the policy that settles it per flow.
• Character Encodings for Admins: UTF-8, Code Pages, and Mojibake
  Learn the concepts in plain words, byte-order marks, why contents garble, and how to detect an encoding. See the difference between what the transfer layer touches and what it never does.
• Filename Encoding Problems on Transfer Servers
  Non-ASCII names across FTP, SFTP, and shares, protocol and client support for UTF-8 names, normalization differences between systems, and the safe-name policy that avoids it all.
• Detecting Mode and Encoding Corruption Early
  Hashes that catch mode corruption, byte-count and magic-number sanity checks, reject patterns for malformed files, and alerting before the downstream system does.
• Never Get Bitten Again: A Prevention Checklist
  Client defaults, server settings, job templates, the encoding and line-ending clauses in partner agreements, and test files that prove the pipeline preserves bytes.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.