Wasabi

4 min readUpdated June 28, 2026

Wasabi is an S3-compatible cloud storage provider with flat-rate pricing and no egress fees. It is a cost-effective option for sites with high media volumes or frequent downloads. WP Media Cloud connects to Wasabi using S3-compatible credentials.

Before you start#

You will need:

A Wasabi account. Create one at wasabi.com.
A Wasabi bucket in your chosen region.
A Wasabi access key and secret key.

Step 1: Create a Wasabi bucket#

Log in to the Wasabi console and go to Buckets. Click Create Bucket. Choose a name and select a region. Wasabi bucket names must be globally unique, lowercase, and between 3 and 63 characters.

On the bucket settings screen, leave the default settings unless you have specific requirements. Click Create Bucket.

Step 2: Create access keys#

Go to Access Keys in the Wasabi console. Click Create New Access Key. Wasabi will generate an Access Key ID and Secret Access Key. Copy and save both values before closing the dialog — the secret key is only shown once.

Wasabi access keys have account-level access by default. If you want to restrict the key to a specific bucket, create a Wasabi policy in Policies and attach it to a sub-user. For most WordPress setups an account-level key is sufficient.

Step 3: Set bucket permissions for public access#

By default Wasabi buckets are private. To serve files publicly without a CDN, apply a bucket policy that allows public reads. In the Wasabi console, go to your bucket, click the Policies tab, and add the following policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": "*",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::your-bucket-name/*"
    }
  ]
}

Replace your-bucket-name with your actual bucket name. If you are serving files through a CDN, you may be able to keep the bucket private and allow access only from the CDN origin. Refer to your CDN provider’s documentation for that configuration.

Step 4: Connect Wasabi in WP Media Cloud#

You have two options for connecting Wasabi to WP Media Cloud. Use whichever suits your setup.

Option A: Setup wizard

Go to WP Media Cloud > Setup Wizard. The wizard walks you through provider selection, credential entry, and CDN configuration. This is the recommended option for most users.

Option B: wp-config.php constants

Add the following constants above the /* That's all, stop editing! */ line in wp-config.php:

define( 'WPMC_PROVIDER',           'wasabi' );
define( 'WPMC_WASABI_REGION',      'us-east-1' );
define( 'WPMC_WASABI_ACCESS_KEY',  'your-access-key' );
define( 'WPMC_WASABI_SECRET_KEY',  'your-secret-key' );
define( 'WPMC_WASABI_BUCKET',      'your-bucket-name' );
define( 'WPMC_WASABI_CDN_TYPE',    'custom' );
define( 'WPMC_WASABI_CDN_URL',     'https://your-cdn.com' );

Set WPMC_WASABI_REGION to the region code for your bucket. Wasabi region codes follow the same format as AWS. Common values are us-east-1, us-east-2, us-west-1, eu-central-1, eu-west-1, eu-west-2, ap-northeast-1, and ap-southeast-1. The region code is shown in the Wasabi console on the bucket’s overview page. Once the constants are in place, go to WP Media Cloud > Settings > Storage and confirm the plugin has loaded them. Constants override any values saved in the settings panel.

Step 5: Test the connection#

Click Test Connection. WP Media Cloud will upload a small test file to your Wasabi bucket and confirm it can be read back. A green success message confirms the connection is working.

Step 6: Configure CDN delivery (optional)#

Wasabi has no egress fees, which means you can serve files directly from the bucket URL without a CDN and not pay for bandwidth. For sites that need global edge caching and faster delivery, Wasabi works well with any CDN that supports a custom origin. Bunny CDN, KeyCDN, and CDN77 all work with Wasabi as an origin. Configure your CDN in WP Media Cloud > Settings > CDN.

Troubleshooting#

Connection test returns Access Denied
The access key does not have sufficient permissions on the bucket. Confirm the key is active in the Wasabi console and that the bucket policy or sub-user policy includes read and write access.

Connection test returns InvalidEndpoint or endpoint error
The region code is incorrect. Each Wasabi region has a specific endpoint in the format s3.[region].wasabisys.com. WP Media Cloud constructs this automatically from the region code you enter, so confirm the region code matches your bucket’s region exactly as shown in the Wasabi console.

Files upload but return 403 when accessed publicly
The bucket policy allowing public reads has not been applied or was applied incorrectly. Check the Policies tab on your bucket in the Wasabi console.

Bucket not found
Wasabi bucket names are case-sensitive. Confirm the bucket name in the Wasabi console matches exactly what you have entered in WP Media Cloud.