> For the complete documentation index, see [llms.txt](https://docs.duplicati.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplicati.com/backup-destinations/destination-overview.md).

# Destination overview

This page describes what a "destination" is to Duplicati and lists some of the available providers

Duplicati makes backups of files, called the source, and places the backup data at a destination chosen by the user. To make Duplicati as versatile as possible, each of the destinations are implemented as a "destination" (or "backend"), each with different properties.

Some storage providers support multiple protocols with each their strengths, and you can generally pick which storage destination provider you like, but if there is a specific implementation for a given storage provider, that is usually the best pick.

Each storage destination has a number of options that can be provided via a URL like format. The options should preferably be provided as part of the URL, but can also be provided via regular commandline options. For instance, the `--use-ssl=true` flag can also be added to the URL with `&use-ssl=true`. If both are provided, the URL value is used.

{% hint style="warning" %}
Each backup created by Duplicati **requires a separate folder**. Do not create two backups that use the same destination folder as they will keep breaking each other.
{% endhint %}

## Timeouts

All destinations share three timeout options that guard against a connection that stops responding:

| Option                 | Default | Description                                                                                                                                                 |
| ---------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `--short-timeout`      | `30s`   | The timeout for short operations, such as deleting a file or creating a folder.                                                                             |
| `--list-timeout`       | `10m`   | The timeout for listing the files in the destination.                                                                                                       |
| `--read-write-timeout` | `30s`   | The timeout for uploads and downloads. The timeout is reset whenever data is transferred, so it only triggers if there is no activity for the given period. |

Like other destination options, they can be added to the destination URL or set as advanced options. The Rclone destination does not support `--read-write-timeout`.

## Duplicati Storage

[Duplicati Storage](/duplicati-console/duplicati-storage.md) is the storage that is integrated with the Duplicati Console. It requires no configuration of the destination, but requires that the machine is connected to the console.

## Standard based destinations

Destinations in this category are general purpose enough, or commonly used, so they can be used across a range of storage providers. Destinations in this category are:

* [File destination](/backup-destinations/standard-based-destinations/file-destination.md) (any path in the filesystem)
* [S3-compatible](/backup-destinations/standard-based-destinations/s3-compatible-destination.md)
* [FTP](/backup-destinations/standard-based-destinations/ftp-destination.md)
* [SFTP](/backup-destinations/standard-based-destinations/sftp-ssh-destination.md) (SSH)
* [WebDAV](/backup-destinations/standard-based-destinations/webdav-destination.md)
* [OpenStack](/backup-destinations/standard-based-destinations/openstack-destination.md)
* [Rclone](/backup-destinations/standard-based-destinations/rclone-destination.md) (binary required)
* [SMB](/backup-destinations/standard-based-destinations/cifs-aka-smb-destination.md) (aka CIFS, Windows network shares)

## Provider specific destinations

Storage destinations in this category are specific to one particular provider and implemented using either their public API description, or by using libraries implemented for that provider. Destinations in this category are:

* [Backblaze B2](/backup-destinations/provider-specific-destinations/backblaze-b2-destination.md)
* [Amazon S3](/backup-destinations/provider-specific-destinations/amazon-s3-destination.md)
* [Box.com](/backup-destinations/provider-specific-destinations/box.com-destination.md)
* [Mega.nz](/backup-destinations/provider-specific-destinations/mega.nz-destination.md) (deprecated)
* [IDrive e2](/backup-destinations/provider-specific-destinations/idrive-e2-destination.md)
* [Aliyun OSS](/backup-destinations/provider-specific-destinations/aliyun-oss-destination.md)
* [Tencent COS](/backup-destinations/provider-specific-destinations/tencent-cos-destination.md)
* [Jottacloud](/backup-destinations/provider-specific-destinations/jottacloud-destination.md)
* [pCloud](/backup-destinations/provider-specific-destinations/pcloud-destination.md)
* [Azure Blob Storage](/backup-destinations/provider-specific-destinations/azure-blob-storage-destination.md)
* [Google Cloud Storage](/backup-destinations/provider-specific-destinations/google-cloud-storage-destination.md)
* [Microsoft Group Drive](/backup-destinations/provider-specific-destinations/microsoft-group-destination.md)
* [SharePoint](/backup-destinations/provider-specific-destinations/sharepoint-v2-graph-api.md) (Microsoft Graph API)
* [SharePoint, legacy API](/backup-destinations/provider-specific-destinations/sharepoint-destination.md) (deprecated)
* [FileJump](/backup-destinations/provider-specific-destinations/filejump.md) (deprecated)
* [Filen.io](/backup-destinations/provider-specific-destinations/filen.io.md)
* [Drime Cloud](/backup-destinations/provider-specific-destinations/drime-cloud.md)
* [Movistar Cloud](/backup-destinations/provider-specific-destinations/movistar-cloud-destination.md)

## File synchronization providers

Storage destinations in this category are also specific to one particular provider, but these storage provider products are generally intended to be used as file synchronization storage. When they are used with Duplicati, the backup files will generally be visible as part of the synchronization files. Destinations in this category are:

* [Dropbox](/backup-destinations/file-synchronization-providers/dropbox-destination.md)
* [GoogleDrive](/backup-destinations/file-synchronization-providers/googledrive-destination.md)
* [OneDrive](/backup-destinations/file-synchronization-providers/onedrive-destination.md)
* [OneDrive for business](/backup-destinations/file-synchronization-providers/onedrive-for-business-destination.md) (deprecated, use OneDrive)

## Decentralized providers

Storage destinations in this category are utilizing a decentralized storage strategy and requires knowledge about each system to have it working. Some of these may require additional servers or intermediary providers and may have different speed characteristics, compared to other storage providers. Destinations in this category are:

* [Storj](/backup-destinations/decentralized-providers/storj-destination.md) (previously Tardigrade)
* [TahoeLAFS](/backup-destinations/decentralized-providers/tahoelafs-destination.md)

## Deprecated and untested destinations

Some destinations are marked as deprecated or untested:

* **Deprecated** destinations still work, but should be migrated away from: [Mega.nz](/backup-destinations/provider-specific-destinations/mega.nz-destination.md), [OneDrive for Business](/backup-destinations/file-synchronization-providers/onedrive-for-business-destination.md) (`od4b://`), the legacy [SharePoint](/backup-destinations/provider-specific-destinations/sharepoint-destination.md) (`mssp://`), [FileJump](/backup-destinations/provider-specific-destinations/filejump.md), and the `cifs://` name for the [SMB destination](/backup-destinations/standard-based-destinations/cifs-aka-smb-destination.md).
* **Untested** destinations are implemented, but the Duplicati team does not have an account to test them with: [Aliyun OSS](/backup-destinations/provider-specific-destinations/aliyun-oss-destination.md), [Tencent COS](/backup-destinations/provider-specific-destinations/tencent-cos-destination.md), and [Movistar Cloud](/backup-destinations/provider-specific-destinations/movistar-cloud-destination.md).

These destinations are not shown in the destination list in the user interface. To select one, type its exact protocol name (such as `mega` or `cos`) in the search field, or turn on "Show all" next to the search field.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplicati.com/backup-destinations/destination-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
