Backup Destinations
Back Up to Local Folders, FTP, S3 Cloud, Email and WebDAV — All from One Task
A single AnyFileBackup task can write to any combination of supported destinations simultaneously. Five target types cover local infrastructure, FTP/SFTP/FTPS/TFTP servers, email delivery, cloud object storage, and WebDAV. Each destination independently controls which files it accepts and how they arrive — on Windows 10 and Windows 11.
The fastest, simplest backup target — any drive or network share already accessible from your machine.
Local Folder, Removable Drive and Windows LAN Share
AnyFileBackup can back up files to any folder on a local internal drive, a removable drive such as a USB stick or external hard disk, or a network drive mounted as a drive letter. Windows network shares addressed by UNC path (\\server\share) are also supported using domain or workgroup credentials. LAN account profiles are managed centrally in Configuration → Accounts and can be reused across any number of tasks without re-entering credentials.
Local folder and LAN share targets work with all four backup modes — All Files, Incremental, Decremental, and Mirroring — and support the full range of conflict resolution options, making them a natural fit for on-site backup and for intermediate staging copies within a multi-target task.
Four protocols — plain FTP, encrypted FTPS, SSH-based SFTP, and lightweight TFTP — one account type covers them all.
FTP, FTPS, SFTP and TFTP Server
AnyFileBackup transfers backup files to FTP servers in four protocol modes. FTP is plain unencrypted transfer. FTPS (Implicit SSL) wraps the connection in TLS/SSL for encrypted transit. SFTP operates over SSH and is suitable when the server exposes an SSH endpoint rather than a traditional FTP port. TFTP (Trivial FTP) is a lightweight protocol with no authentication — rare in general use, but well suited to local closed networks where encryption is not a concern and simplicity matters, such as firmware or configuration file environments.
For FTP and FTPS, both active and passive transfer modes are available; passive mode is recommended when active mode is blocked by a firewall. Authentication supports username and password, OTP/TOTP one-time passwords, and client certificate authentication for FTPS and SFTP using a private key stored in a Certificate account. Multiple account profiles can be created for the same server to accommodate different credentials or directory roots across tasks. FTP, FTPS, and SFTP are also available as backup sources, enabling files to be pulled from a remote server and written to any supported destination in the same task.
Deliver backup files directly to any inbox — no additional storage account required.
Send Backup Files as Email Attachments
AnyFileBackup delivers backed-up files as email attachments to one or multiple recipients via a configured SMTP account. Each transferred file is sent as a separate message — email works file by file.
Multiple outgoing mail account profiles are supported, and OAuth authentication is available for modern providers such as Google Workspace and Microsoft 365. Per-destination file filters give precise control over which files reach this target.
Amazon S3, Google Cloud, Cloudflare R2, Backblaze B2 and more — one connector, any S3-compatible bucket.
S3-Compatible Cloud Storage — Amazon AWS, Google Cloud and More
AnyFileBackup connects to any S3-compatible cloud storage bucket as a backup destination. Supported providers include Amazon AWS S3, Google Cloud Storage, Cloudflare R2, Backblaze B2, IDrive e2, IBM Cloud Object Storage, Oracle Cloud Infrastructure, DigitalOcean Spaces, Wasabi, MinIO, and any other provider that implements the S3 API.
Authentication uses an access key and secret key pair. Multiple cloud accounts can be managed and reused across tasks — a single task can write to buckets at different providers simultaneously. S3 is also available as a backup source.
Nextcloud, ownCloud, SharePoint or any corporate document server — if it speaks WebDAV, AnyFileBackup can reach it.
WebDAV Server
AnyFileBackup can push backup files to any WebDAV-compatible host — Nextcloud, ownCloud, SharePoint Online, and corporate document servers that expose a WebDAV endpoint.
Connection options include Use SSL, Follow redirect, and Verify host name — which can be disabled for servers with self-signed certificates. Account profiles are managed centrally and reusable across any number of tasks.
Each destination independently controls which files it accepts and how they arrive — filter, compress, encrypt, or decrypt, per target.
Per-Destination File Filters and Transformation
Every destination target in a task carries its own set of file filters — accept or reject rules that determine which files from the source this target actually receives. Filters support plain text (literal filename matching), wildcards (* and ?), and regular expressions, and multiple masks can be combined. One target in a task can therefore receive only PDF files, another only archives, and a third everything — all from the same source, in the same run, without duplicating the task.
Each target also has its own Modify before transfer setting. Five modes are available: None (plain delivery), Compress (ZIP archive, no password), Uncompress (unzip before delivery), Compress and encrypt (ZIP password protection or PGP public-key encryption), and Decrypt and decompress (ZIP or PGP). One destination can receive a compressed encrypted archive while another receives the same file plain — all from the same task run.
Frequently Asked Questions
Can one task back up to multiple destinations at the same time?
Yes. A single AnyFileBackup task can write to any number of targets simultaneously — local folders, FTP servers, S3 buckets, WebDAV hosts, and email recipients can all be combined in the same task. All targets share the same source while each applies its own independent file filters and transformation settings.
Which FTP protocols does AnyFileBackup support?
AnyFileBackup supports four protocols: plain FTP, FTPS (FTP over TLS/SSL, Implicit SSL), SFTP (FTP over SSH), and TFTP (Trivial FTP — lightweight, no authentication, suited to local closed networks). Active and passive transfer modes are available for FTP and FTPS. Authentication options include username and password, OTP/TOTP one-time passwords, and client certificate authentication (for FTPS and SFTP, via Certificate accounts).
Which S3-compatible cloud storage providers does AnyFileBackup support?
AnyFileBackup works with any provider that implements the S3 API, including Amazon AWS S3, Google Cloud Storage, Cloudflare R2, Backblaze B2, IDrive e2, IBM Cloud Object Storage, Oracle Cloud Infrastructure, DigitalOcean Spaces, Wasabi, MinIO, and others. Multiple provider accounts can be managed independently and used within the same task.
Can AnyFileBackup back up to Nextcloud or SharePoint via WebDAV?
Yes. Any host that exposes a WebDAV endpoint is supported — including Nextcloud, ownCloud, SharePoint Online, and corporate document servers. SSL connections are supported, with options to follow redirects and to verify or bypass hostname checking for self-signed certificates. Configure a WebDAV account profile once and reuse it across as many tasks as needed.
Can AnyFileBackup use an FTP server or S3 bucket as a source, not just a destination?
Yes. Both FTP/FTPS/SFTP servers and S3-compatible buckets are available as backup sources. You can pull files from a remote server or cloud bucket and write them to any combination of supported destinations — local folder, another cloud provider, WebDAV, or email — in the same task.
Can different destinations in the same task receive different files or different file formats?
Yes. Each destination target has its own independent file filters — Accept or Reject rules using plain text, wildcards, or regular expressions — that control which files it receives. Each target also has its own Modify before transfer setting: None, Compress (ZIP), Uncompress, Compress and encrypt (ZIP or PGP), or Decrypt and decompress (ZIP or PGP). One target can receive compressed encrypted archives while another receives plain files, all from the same task run.