Fling is a file transfer software that can be used to transfer and backup files over a computer network and ftp. It’s two main uses are to backup files that are stored on a local computer system to computers in the network or to an ftp server located on the Internet.

The developers have added some other options that include backing up files between local hard drives, update a remote website over ftp or to automate transfers of files to an USB drive.

The program displays a wizard upon first start which will aid the user in setting up the first backup or transfer job. The user needs to enter some data after making the selection. The type of data depends largely on the selected job. Backing up data to a remote ftp server requires the ftp login credentials and IP while backing up files between two local hard drives requires only the selection of the folders involved.

The last step is included in every setup. It asks the user to select an update and scan option. Possibilities are manual updates, automatic updates when changes are detected (that means almost instantly), interval scans to check for changes occasionally and on demand folder scans.

It is possible to skip the wizard and configure the service manually. This adds a few additional option to the file transfer which could be interesting for experienced users.

It is for example possible to exclude files from being copied (using wildcards, e.g. *.exe), prevent the deletion of remotely hosted files or to delete local files after a successful file transfer.

Fling’s main advantage is that it is not complicated to setup. It takes roughly a minute to configure a backup or file transfer job in the software program. Fling is available for the Microsoft Windows operating system, more precisely for all major releases of the last years including Windows 2000, Windows XP, Windows Vista, Windows Server 2003, 2008 and Windows 7.

You might want to check out our article on Windows backup software to read about additional free programs that can be used to backup and transfer data.

A major difference between the two applications is the fact that Fast Copy does not hijack the original Windows copy, delete and move operations but comes only into play when the user selects the application to handle the transfers. This can be done by loading Fast Copy or adding Fast Copy entries to the right-click context menu. The option for the latter is provided in the program’s options.

Since the usage is not automatic using Fast Copy makes only sense in situations where the user has to copy many files and folders at once, for example when moving the contents of one hard drive to another. It simply takes about five to ten seconds to start the file transfer because the source and destination locations have to be added to the program manually.

The context menu entry is only adding the source location to the program but the destination would still have to be selected manually. Fast Copy uses parallel processing if the source and destination location are on different hard drives and a huge buffer if they are on the same. It comes with a lot of options that can be changed like the buffer size or actions to take if a file exists in the destination.

The command line options might make it usable for batch files that use file operations. It lacks a few of the features that TeraCopy comes with like a queue that offers options to skip files or pause the process.

Fast Copy in its current version can be used in batch files because of its command line parameters and to copy large amount of files. It does not work as a real transfer replacement for Windows and have to leave that field to Teracopy.