> For the complete documentation index, see [llms.txt](https://moverdocs.files.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moverdocs.files.com/connections/backblaze-b2.md).

# Backblaze B2

## Add a <code class="expression">page.vars.VENDOR\_NAME</code> Connection

Create a new Connection and choose <code class="expression">page.vars.VENDOR\_NAME</code> for the connection type.

Provide a **Connection Label** so you can identify the connection in a list. This is important if you need more than one connection of the same type.

### Bucket Details

Enter the name of the bucket to use for the connection.

Enter the endpoint for your Backblaze bucket. It will have a format like `https://s3.<region>.backblazeb2.com`.

### Credentials

Mover uses an access key and secret key to authenticate requests, following the protocol established by AWS for S3. In Backblaze B2, the access key is called **Key ID** and the secret key is the **Application Key**.

You can use the Backblaze web console to create Application Keys (or App Keys) for this connection. We recommend generating separate keys for each bucket, rather than one key for all buckets. You can also grant read/write access or limit it to read-only; Mover needs read/write access to copy files to the bucket.

## <code class="expression">page.vars.VENDOR\_NAME</code> is Case Sensitive

Be aware of case sensitivity differences when copying, moving, or syncing files and folders between connections. Copying items from a system which is not case sensitive to another that is case sensitive could result in 1 item being treated as 2 different ones, such as attempting to overwrite `MyFile.txt` with `myfile.txt` .&#x20;

In the other direction, copying from a case sensitive system to another that is not case sensitive can cause files to be overwritten, and folders to have their contents merged, if their case *insensitive* names are a match.