CDN77
CDN77 is a content delivery network you put in front of your storage bucket with a CDN Resource. WP Media Cloud serves your media from the resource, purges replaced files automatically and shows bandwidth on the Dashboard.
Which storage providers can use it#
| Provider | CDN77 | Dashboard bandwidth | Where to set it |
|---|---|---|---|
| Amazon S3 | Yes | Yes | Setup wizard only (no CDN card in Settings) |
| Google Cloud Storage, Wasabi, Hetzner Object Storage, Backblaze B2, Custom S3 | Yes | Yes | The provider’s CDN card in Settings, for example Wasabi CDN |
| DigitalOcean Spaces | Yes | No | DigitalOcean Spaces CDN card |
| S3-compatible | Yes | No | S3-Compatible CDN card |
| Bunny Edge Storage, Cloudflare R2 | No CDN choice |
Before you start#
- Set up your storage provider in WP Media Cloud first, using its guide under Storage providers.
- Make the files publicly readable, because CDN77 fetches them from the bucket’s public address.
- Have a CDN77 account.
Step 1: Create a CDN Resource#
- In the CDN77 Client Panel, click Create new CDN Resource.
- Choose the URL origin type and enter your bucket’s public address as the origin.
- Click Create CDN Resource.
- Optional: to use your own domain, add it in the resource’s CNAME & SSL section and save.
Step 2: Get an API token#
In the CDN77 Client Panel, go to Account Settings > API Token, then create or copy a token. WP Media Cloud uses it to list your resources, purge replaced files and read bandwidth.
Step 3: Choose CDN77 in WP Media Cloud#

Setup wizard:
- Open Media Cloud. A new site opens the wizard automatically; otherwise go to Settings and click run the setup wizard.
- Choose your storage provider and fill in its fields.
- Under CDN Configuration, choose CDN77.
- Paste the token into CDN77 API Token and click Load Resources.
- Select your resource in CDN Resource.
- Click Continue, then Save & Go to Dashboard.
Settings:
- Go to Media Cloud > Settings and find your provider’s CDN card.
- Choose CDN77.
- Paste the token into CDN77 API Token and click Load resources.
- Select your resource in CDN Resource.
- Click Save Settings, then Update all media URLs under Apply to Existing Media.
Selecting a resource sets the CDN URL automatically. If the resource has a CNAME, the first one is used. CDN77 has no separate CDN URL field.
Fields#
| Field | What it is |
|---|---|
| CDN77 API Token | Your token. After saving, the field says the token is saved; paste a new value to replace it. |
| CDN Resource | The resource in front of your bucket. It appears after you click Load Resources. |
Step 4: Check it works#
- Upload a test image in Media > Add New Media File.
- Open it in the Media Library and copy the File URL.
- Check the address starts with your CDN77 hostname or CNAME, then open it and check the image loads.
The Health page has a CDN URL check that reports whether your CDN URL responds.
Purging replaced files#
When an image optimizer or Enable Media Replace uploads a new version of a file under the same name, WP Media Cloud purges the old copy from CDN77 automatically, with every image size. This uses your API token and the resource you selected, and needs Auto purge CDN on replace on in Settings > Offload Behaviour (the default). See Automatic CDN purge.
Dashboard stats#
With CDN77 and a provider that supports it, the Dashboard shows:
- CDN Bandwidth: total traffic served by the resource for the selected period.
- CDN Bandwidth, Last 7 Days: a daily chart; 7D, 14D and 30D change the period.
- Storage Used: CDN77 does not report bucket storage, so it comes from your storage provider where it reports it, or is counted from WP Media Cloud’s records.
Configure with wp-config.php#
Replace <PROVIDER> with AWS, GCS, DO, WASABI, HETZNER, B2, S3 or S3COMPAT:
| Constant | Value |
|---|---|
WPMC_<PROVIDER>_CDN_TYPE | 'cdn77' |
WPMC_<PROVIDER>_CDN77_API_TOKEN | Your CDN77 token |
WPMC_<PROVIDER>_CDN77_RESOURCE_ID | Your resource ID, for example '123456', used for purging and bandwidth |
WPMC_<PROVIDER>_CDN77_URL | Your CDN URL, for example https://cdn.example.com |
WPMC_<PROVIDER>_CDN_URL | Your CDN URL. Media addresses are built from this, so always set it. |
Constants override values saved in Settings.
Change or remove it later#

- A different resource or a new CNAME: in the provider’s CDN card, click Load resources, select the resource, click Save Settings, then Update all media URLs.
- Amazon S3: run the setup wizard again.
- Back to the bucket address: choose Direct Bucket and click Save Settings. This also clears the CDN URL.
Troubleshooting#
| Problem | Cause | Fix |
|---|---|---|
| Load resources in Settings does nothing | The CDN77 request failed, and Settings does not show the error | Try Load Resources in the setup wizard to see CDN77’s message, and check the token |
| The resource list won’t load | The token cannot read your resources | Choose Custom CDN and enter your CDN77 hostname as CDN URL, or set the constants above |
| 404 errors from CDN77 | The origin does not point at your bucket, or files are not public | Open a file at the bucket’s own address, then check the origin in CDN77 |
| Images still load from the bucket | No resource is selected, so the CDN URL is empty | Select a resource, save, and clear your page cache |
| A replaced image still shows the old version | Auto purge is off, or no resource is selected | Turn on Auto purge CDN on replace and select the resource |
| CDN Bandwidth shows 0 B | The resource has no traffic yet, the provider is DigitalOcean Spaces or S3-compatible, or CDN77 returned an error | Check statistics in the CDN77 Client Panel. On versions before 1.2.0 the chart stayed empty; update the plugin |