---
title: "Multisite"
url: "https://dudlewebs.com/guideline/media-cloud-sync/plans-and-multisite/multisite/"
markdown_url: "https://dudlewebs.com/guideline/media-cloud-sync/plans-and-multisite/multisite.md"
type: "Docs"
language: "en-US"
date_published: "2026-11-08T11:14:31+00:00"
date_modified: "2026-11-09T17:23:47+00:00"
---

# Multisite

Media Cloud Sync works on WordPress Multisite. Each site in the network works independently.

## How it works

- **Setup per site:** each site runs the [setup wizard](https://dudlewebs.com/guideline/media-cloud-sync/getting-started/connecting-your-cloud-storage-setup-wizard/) and has its own connection, settings, delivery provider, and bulk jobs.
- **Records per site:** each site has its own `wpmcs_items` table. It’s created when you network-activate the plugin, and when a new site is added.
- **Jobs per site:** jobs and their counts are per site, not network-wide.

## Sharing keys

A `WPMCS_CONFIG` constant in `wp-config.php` applies to **every site in the network**, so each site reads the same keys. Each site still chooses its own bucket in the wizard. See [Storing Credentials in wp-config.php](https://dudlewebs.com/guideline/media-cloud-sync/storage-providers/storing-credentials-in-wp-config-php/).

## Sharing a bucket

> **Warning:** Give each site **its own bucket or its own prefix**. Bucket keys are built from your prefix, the year and month, and the file name. WordPress’s `sites/2/` folder isn’t part of them. So two sites with the same prefix that upload `photo.jpg` in the same month would use the same cloud file, and one would overwrite the other.

With a shared bucket, set **Add Prefix to Bucket Path** per site before syncing, for example:

| Site | Prefix |
| --- | --- |
| Main site | `media/site-1` |
| Site 2 | `media/site-2` |
| Site 3 | `media/site-3` |

Don’t nest one site’s prefix inside another’s, such as `media` and `media/site-2`. [Clean Up Unused Files](https://dudlewebs.com/guideline/media-cloud-sync/pro-tools/clean-up-unused-files/) `PRO` scans the base path, so the nested site’s files would look unused to the outer one.

[Bucket CORS](https://dudlewebs.com/guideline/media-cloud-sync/pro-tools/bucket-cors/) `PRO` rules are per bucket, so add the other sites under **Also allow**.

## Pro license

A license is activated for a site’s address, so activate it on each site that needs Pro. How many sites you can use depends on your plan: the License screen shows **Limit Reached** if you run out.

## Copying settings between sites

Use [Import / Export](https://dudlewebs.com/guideline/media-cloud-sync/sync-and-maintenance/copying-settings-with-import-export/) to copy settings from one site to another.

## Related

- [Storage Settings reference](https://dudlewebs.com/guideline/media-cloud-sync/settings/storage-settings-reference/)

[← Previous Free vs Pro](https://dudlewebs.com/guideline/media-cloud-sync/plans-and-multisite/free-vs-pro/) [Next → Developer Docs: Overview](https://dudlewebs.com/guideline/media-cloud-sync/developers/developer-docs-overview/)

Still need help?

[Chat with us Quick questions, answered live](https://dudlewebs.com/contact/) [Contact us Sales, partnerships or anything else](https://dudlewebs.com/contact/) [Create a ticket Technical issues with your site](https://dudlewebs.com/submit-ticket/)
