Getting Started

1. Sign in to the Backblaze web console at backblaze.com.
2. In the left sidebar, click B2 Cloud Storage → Buckets.
3. Click Create a Bucket.
4. Enter a unique bucket name — at least 6 characters. This name is globally unique across all Backblaze customers.
5. Set Files in Bucket to Private. The app generates short-lived signed URLs for recipients, so the bucket itself should stay private.
6. Leave encryption and object lock at their defaults, then click Create a Bucket.

Application Keys let you grant scoped access to a single bucket without exposing your master key.

1. In the left sidebar, click Application Keys.
2. Click Add a New Application Key.
3. Give it a descriptive name (e.g. thefileshareplace-mybucket).
4. Under Allow access to Bucket(s), select your specific bucket from the dropdown — do not leave it set to "All".
5. Set Type of Access to Read and Write.
6. Leave the optional duration and file name prefix fields empty.
7. Click Create Application Key.
8. A dialog will show your keyID and applicationKey. Copy both immediately — the applicationKey is shown only once.

1. Open The File Share Place desktop app and go to Manage Buckets → Add Bucket.
2. Enter your details:

Recipients can download files either via the desktop app or directly in their browser. Browser downloads require a one-time CORS configuration on your bucket so the browser is allowed to fetch files from your storage provider.

Run this command using the Backblaze B2 CLI (pip install b2):

b2 bucket update --cors-rules '[
  {
    "corsRuleName": "tfsp",
    "allowedOrigins": ["https://thefileshare.place"],
    "allowedOperations": ["s3_head", "s3_get"],
    "allowedHeaders": ["*"],
    "maxAgeSeconds": 3600
  }
]' <your-bucket-name>

1. Sign in to the Wasabi Console at console.wasabisys.com.
2. Click the Buckets tab in the left sidebar.
3. Click Create Bucket.
4. Enter a unique bucket name and choose the Region closest to you or your recipients. Note this region — you'll need it for the endpoint URL.
5. Leave all options on the Properties step at their defaults (versioning and object lock disabled, enable logs if you want to self validate access).
6. Review and click Create Bucket.

Wasabi's built-in policies don't match what the app needs (read + write scoped to one prefix), so create a custom policy that grants only the required S3 actions on the thefileshare.place/ prefix of your bucket.

1. In the left sidebar, click Policies, then Create Policy.
2. Enter a name (e.g. TheFileSharePlacePolicy).
3. Paste the JSON below, replacing <your-bucket-name> with the bucket you created in Step 1.
4. Click Create Policy.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ObjectAccess",
      "Effect": "Allow",
      "Action": [
        "s3:GetObject",
        "s3:PutObject",
        "s3:DeleteObject",
        "s3:AbortMultipartUpload",
        "s3:ListMultipartUploadParts"
      ],
      "Resource": "arn:aws:s3:::<your-bucket-name>/thefileshare.place/*"
    },
    {
      "Sid": "BucketList",
      "Effect": "Allow",
      "Action": [
        "s3:ListBucket",
        "s3:ListBucketMultipartUploads"
      ],
      "Resource": "arn:aws:s3:::<your-bucket-name>",
      "Condition": {
        "StringLike": {
          "s3:prefix": ["thefileshare.place/*"]
        }
      }
    }
  ]
}

Create a sub-user (IAM user) and attach the policy you just created.

1. In the left sidebar, click Users, then Create User.
2. Enter a username (e.g. thefileshareplace).
3. Check Programmatic (create API key).
4. Click Next, skip through the Groups step, and on the Policies step attach the TheFileSharePlacePolicy policy you created in Step 2.
5. Click Create User. A dialog shows the Access Key and Secret Key. Copy both immediately - the Secret Key is shown only once.

1. Open The File Share Place desktop app and go to Manage Buckets → Add Bucket.
2. Enter your details:

Recipients can download files either via the desktop app or directly in their browser. Browser downloads require a one-time CORS configuration on your bucket so the browser is allowed to fetch files from your storage provider.

1. In the Wasabi Console, open the Buckets list and click the menu icon next to your bucket, then choose Settings.
2. Open the Permissions tab and find the CORS section.
3. Paste the JSON below and save.

[
  {
    "AllowedOrigins": ["https://thefileshare.place"],
    "AllowedMethods": ["GET", "HEAD"],
    "AllowedHeaders": ["*"],
    "MaxAgeSeconds": 3600
  }
]

1. Sign in to the Cloudflare Dashboard at dash.cloudflare.com.
2. In the left sidebar, click R2 Object Storage.
3. Click Create bucket.
4. Enter a bucket name (3–63 characters, lowercase letters, numbers, and hyphens only).
5. Optionally choose a Location for data residency (e.g. Western Europe, Asia Pacific). The default uses automatic placement.
6. Leave the storage class as Standard and click Create bucket.

1. From the R2 Overview page, scroll to API Tokens and click Manage R2 API tokens.
2. Click Create API token.
3. Give it a name (e.g. thefileshareplace).
4. Set Permissions to Object Read & Write.
5. Under Specify bucket(s), select your specific bucket — do not leave it set to "Apply to all buckets".
6. Optionally set a TTL to expire the token automatically.
7. Click Create API Token.
8. The confirmation page shows your Access Key ID and Secret Access Key. Also note the Endpoint URL on this page. Copy all three immediately — the Secret Access Key is shown only once.

1. Open The File Share Place desktop app and go to Manage Buckets → Add Bucket.
2. Enter your details:

Recipients can download files either via the desktop app or directly in their browser. Browser downloads require a one-time CORS configuration on your bucket so the browser is allowed to fetch files from your storage provider.

1. In the Cloudflare dashboard, go to R2 Object Storage → your bucket → Settings.
2. Scroll to CORS Policy and click Add CORS policy.
3. Switch to the JSON editor, paste the JSON below, and save.

[
  {
    "AllowedOrigins": ["https://thefileshare.place"],
    "AllowedMethods": ["GET", "HEAD"],
    "AllowedHeaders": ["*"],
    "MaxAgeSeconds": 3600
  }
]