The FTP protocol defines two ways of transferring files: ASCII (Text) and Binary.

A binary transfer creates a byte-for-byte identical copy of the transferred file.

An ASCII transfer is intended for files which contain only plain text, and will attempt to convert the line endings from those of the sending system to those of the receiving system.

By default, Transmit runs in Automatic mode, which means that Transmit will make a decision about whether to use ASCII or binary for each file based on its file type extension. For example, an “html” file would be sent in ASCII mode and a “png” file would be sent in binary mode.

Leave Transmit in automatic mode unless you know of a specific reason that a different mode should be used.

To change transfer modes:

Connect to an FTP server

Choose Transfer > Mode

Choose ASCII (Text), Binary, or Auto

That transfer mode will be used for all subsequent transfers.

In automatic mode, Transmit assumes all files should be sent in binary mode unless they are specifically listed as known ASCII file types.

To add or remove a file type from the list of known ASCII file types:

Choose Transmit > Preferences…

Click Transfers

Click
or
in the ASCII File Extensions section to add or remove ASCII types

Troubleshooting

A binary file mistakenly sent in ASCII mode will very likely become corrupted. For example, a png image uploaded in ASCII mode will likely become un-viewable. Always use binary mode for these types of files.

An ASCII text file mistakenly sent in binary mode will retain the line endings from the originating system. If the two systems use the same type of line ending characters, the file will be the same on both sides. However if the line endings differ between the two systems, the transferred file will become either double-spaced or compressed onto a single very long line, unless you use ASCII mode.

FTP is the only protocol that distinguishes between ASCII and binary files. Other protocols, such as SFTP, always create a byte-for-byte (binary mode) copy of the file.