How to use FTP with Files.fm: backups, camera uploads, and automated file transfers

FTP is one of the oldest ways to transfer files, but it is still useful whenever a device, application, or scheduled task needs to move files without opening a web browser. Files.fm accounts with a supported storage plan can use FTP access for automated uploads, large batches of files, and equipment that already includes an FTP client.

The best choice is FTPS with Explicit TLS. It keeps the familiar FTP workflow while encrypting the connection. Use unencrypted FTP only when an older camera or device cannot use FTPS, and isolate that workflow as much as possible.

Where FTP is still useful today

FTP remains practical because it is supported by many professional devices, NAS systems, backup tools, servers, and desktop clients. Common uses include:

• Scheduled computer and server backups: configure backup software or a script to upload selected folders, database exports, website copies, or configuration archives at a fixed time.
• NAS and office file-server copies: many network storage devices can send scheduled copies to a remote FTP or FTPS destination. This adds an off-site copy without requiring someone to upload files manually.
• Photo and video camera transfers: supported professional cameras can send photographs or recordings directly after capture. This is useful for event photographers, studios, newsrooms, and production teams that need material to reach colleagues quickly.
• Security and trail cameras: compatible cameras and recorders can upload snapshots or clips when motion is detected or on a schedule. Check whether the device supports FTPS; some older models offer only unencrypted FTP.
• Automated exports and reports: accounting, monitoring, industrial, and other systems can deliver regular CSV, PDF, log, or archive files to one central location.
• Large batch transfers and migration: an FTP client can queue many folders, retry interrupted items, and continue working in the background. This is convenient when moving a prepared archive or regularly exchanging production files.

FTP transfer is not automatically a backup

FTP is the transport method: it moves or copies files. A reliable backup process also defines what is copied, how often it runs, how long older copies are kept, who can delete them, and how data will be restored.

A synchronisation or mirror job may also copy an accidental deletion or damaged file. For important data, keep independent copies, monitor failed jobs, and regularly restore a small sample. The 3-2-1 principle is a useful starting point: keep three copies of important data, on two types of storage, with one copy off-site.

Create a separate FTP key

1. Sign in to Files.fm and open Account → API keys.
2. Select Create a new key and choose the FTP type. The account also has a dedicated FTP access section with a shortcut for creating an FTP key.
3. Give the key a clear name, such as “Office NAS backup” or “Studio camera”, so you can identify it later. Set an expiry date when the workflow is temporary.
4. Copy the new key when it is displayed and store it in the device or application that will use it. For security, the value is not displayed again.

Create separate keys for unrelated devices or jobs. If one device is replaced or a key is exposed, you can disable or delete only that key without changing your Files.fm account password or interrupting other connections.

FTP client settings

• Server: ftp.failiem.lv
• Port: 21
• Protocol: FTPS with Explicit TLS whenever supported
• Transfer mode: passive
• Username: your Files.fm username
• Password: the FTP key you created — not your account password

Enter these details in the camera, NAS, backup application, automation tool, or desktop FTP client. Start with a small test file, confirm that it appears in the intended Files.fm folder, then test downloading or restoring it before enabling a large scheduled job.

A safer setup checklist

• Prefer FTPS and avoid plain FTP when the device supports encryption.
• Use one clearly named FTP key per device or automated process.
• Limit access to the people who configure the transfer; do not send keys by email or chat.
• Review the API key list periodically and disable keys that are no longer used.
• Check storage capacity and job logs so a failed upload does not go unnoticed.
• Test recovery instead of treating a successful upload as proof that the backup works.

To get started, open Files.fm API keys, create a key of type FTP, and test an encrypted connection with one non-sensitive file.