> 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/object-storage/s3-compatible-storage/filebase.md).

# Filebase

Mover connects to Filebase buckets through Filebase's S3-compatible interface. Filebase stores data using IPFS, the InterPlanetary File System.

## Connections

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

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

### Bucket Details

Fill the *Filebase Bucket Name* with the name of your bucket from your *Filebase web portal > Buckets* page.

### Credentials

Mover uses an Access Key and Secret Key to authenticate requests, following the protocol established by AWS for S3.

Use the [Access Keys dashboard](https://docs.filebase.com/api-documentation/s3-compatible-api#access-keys) in your Filebase account to create and manage your keypair.

Enter the key in *Filebase Access Key* and the secret in *Filebase Secret Key*.

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

Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, `MyFile.txt` and `myfile.txt` can be two different files. A case-insensitive system treats those names as the same file.

Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.