> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dataraven.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Backblaze B2

> Connect Backblaze B2 buckets as sources and destinations for transfer tasks.

Backblaze B2 cloud storage, using B2's native API with application keys.

## At a Glance

|                   |                                                             |
| ----------------- | ----------------------------------------------------------- |
| **Region**        | Optional                                                    |
| **Endpoint URL**  | Not needed                                                  |
| **Credentials**   | Application key — `application_key_id`, `application_key`   |
| **Task defaults** | `transfers: 32`, `fast_list: true`, `b2_hard_delete: false` |

## Credentials

Create a [secret](/secrets) with the **Backblaze B2** provider type. The auth method is
`b2_application_key`, which requires:

| Field                | Description           |
| -------------------- | --------------------- |
| `application_key_id` | B2 application key ID |
| `application_key`    | B2 application key    |

Create an application key from the Backblaze dashboard under **App Keys**, scoped to the bucket
you plan to transfer to or from.

## Location Setup

| Field             | Value       |
| ----------------- | ----------- |
| **region**        | Optional    |
| **endpoint\_url** | Leave blank |

Example:

| Field          | Example value      |
| -------------- | ------------------ |
| name           | `B2 Media Backups` |
| location\_type | Backblaze B2       |
| bucket\_name   | `acme-media`       |

## Provider Quirks

B2 locations automatically receive optimized [task defaults](/connecting-storage#provider-defaults)
following Backblaze's own recommendations: higher concurrency (`transfers: 32`), fast listing for
large buckets, and `b2_hard_delete: false` so deletions hide file versions rather than
permanently removing them. Override any of these in the task's rclone configuration.

## Importing from rclone.conf

B2 remotes appear in `rclone.conf` as `type = b2`. The remote's `account` field imports as
`application_key_id` and `key` as `application_key`. See the
[rclone import guide](/guides/import-rclone-config).