> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/storage/integrations/other-platforms/backblaze-b2.md).

# Backblaze B2

Learn how to connect to Backblaze B2 storage

## Overview

Couchdrop can connect directly to Backblaze B2 and make your existing Backblaze storage available through Couchdrop.

Once connected, you can use files and folders in Backblaze B2 with Couchdrop file transfer and workflow features while keeping the files in your Backblaze bucket.

## How to connect Backblaze B2

{% hint style="warning" %}

#### Before you start

To connect Backblaze B2, you will need:

* A Backblaze B2 account
* A Backblaze Key ID
* The corresponding Backblaze Master Key
* A Backblaze Bucket ID
  {% endhint %}

{% stepper %}
{% step %}

### Add a new storage connection

In Couchdrop, add a new storage connection and select **Backblaze B2** from the list of available connections.
{% endstep %}

{% step %}

### Configure Backblaze B2

Enter a **Name for this integration** and select the **Couchdrop folder path** where the connection will appear.

Enter your Backblaze credentials:

* **Backblaze Key ID** — Enter the Key ID Couchdrop will use to authenticate with Backblaze.
* **Backblaze Master Key** — Enter the corresponding Backblaze key.
* **Backblaze Bucket ID** — Enter the ID of the Backblaze bucket you want to connect.

Select **Save and Test** to verify the Backblaze B2 connection.
{% endstep %}

{% step %}

### Select your folder

After the connection has been tested, you can optionally select a specific folder to map into Couchdrop.

Leaving the folder selection blank allows Couchdrop to map the connected storage directly without restricting it to a specific folder.
{% endstep %}

{% step %}

### Save your connection and use Backblaze in Couchdrop

Optionally, configure **Transfer Shield** and select a content rule group to surface or block unexpected, non-compliant, or malicious files uploaded through this connection.

When the configuration is complete, save the integration.
{% endstep %}
{% endstepper %}

## Frequently asked questions

<details>

<summary>Does Couchdrop copy my Backblaze B2 files into Couchdrop?</summary>

No. Couchdrop connects to your existing Backblaze B2 storage and makes it available through Couchdrop. Your files remain in Backblaze B2.

</details>

<details>

<summary>Can I connect Couchdrop to a specific Backblaze bucket?</summary>

Yes. The **Backblaze Bucket ID** identifies the bucket Couchdrop connects to.

</details>

<details>

<summary>Can I map Couchdrop to a specific folder inside the bucket?</summary>

Yes. After the connection has been successfully tested, you can optionally select a folder or manually enter a path.

Leaving the folder selection blank allows Couchdrop to map the connected storage directly.

</details>

<details>

<summary>Can I create multiple Backblaze B2 connections?</summary>

Yes. You can create separate Backblaze B2 connections in Couchdrop for different buckets or storage mappings.

</details>

<details>

<summary>Can I use Transfer Shield with Backblaze B2?</summary>

Yes. You can optionally apply a Transfer Shield content rule group to surface or block unexpected, non-compliant, or malicious files uploaded through the connection.

</details>


---

# 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.couchdrop.io/storage/integrations/other-platforms/backblaze-b2.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.