Home / Ongoing Work / Hosting & Infrastructure / Shared media library configuration

We configure shared media library access across your multisite network, so subsites can use a common pool of images and files rather than each maintaining entirely separate, duplicated media libraries — useful for a network of related sites wanting consistent branding assets or shared product photography.

MSO-008

Shared media library configuration

A shared media library configured across subsites, without forcing every subsite into it.

$109.32 delivered in 48 hours
Needs WP admin login and SFTP access. Create a limited sub-account — we never ask for your own password.
  • Full backup taken before we start
  • If we can’t fix it, you get your money back
  • We never ask for your own password

What we need from you

  • Access to your network admin dashboard
  • Confirmation of which subsites should share media, and any that should remain separate
  • Confirmation of the shared media plugin or approach you’d prefer, if you have one in mind

This or something else?

You want subsites on your network to share a common media library instead of separate ones This fix covers it
You want subsites to remain fully independent, with no shared media Not something you’d need this fix for — that’s typically multisite’s default behaviour without this configuration
You want a shared media library specifically for a new network being set up Still covered by this fix, applied as part of initial network configuration
Your existing shared media setup has stopped working correctly Worth describing the specific issue directly — likely a diagnostic fix rather than a fresh setup

What we do

  1. Confirm which subsites should share media and the intended approach
  2. Configure the shared media library solution across the specified subsites
  3. Verify subsites can access and use shared media correctly
  4. Test that media uploads and permissions behave as intended
  5. Confirm subsites not included in sharing remain appropriately independent
  6. Document the configuration for future reference

What is included

  • Shared media library access configured across specified subsites
  • Verified correct access and permissions
  • Confirmed independence for subsites not included in sharing
  • A written note on the configuration

Not included

  • Migrating or consolidating existing, separate media libraries into the shared structure — a separate, related fix if needed
  • Setting up the multisite network itself, if not already done
  • Ongoing media organisation or tagging as a standing service
  • Resolving storage capacity issues if the shared library grows very large

Questions about this fix

Will every subsite be forced to use only shared media?

Not necessarily — we can configure this so subsites have access to a shared pool while still being able to upload their own subsite-specific media if that's what you want, depending on your preferred structure.

What happens to media already uploaded separately on each subsite?

Existing, separate media isn't automatically merged into the shared library — migrating or consolidating existing media is a separate, related task if that's something you want done alongside this setup.

Can I limit which subsites see the shared library?

Yes, if you specify particular subsites for inclusion, we'd configure sharing accordingly rather than applying it network-wide by default.

Does this affect storage costs or limits?

A shared library consolidates storage rather than duplicating the same assets across subsites, which can actually be more storage-efficient, though very large shared libraries still need adequate hosting storage regardless.

Will this slow down media uploads or browsing for subsite users?

A well-configured shared library shouldn't introduce a noticeable slowdown, though an extremely large combined library could make browsing marginally less snappy than a smaller, dedicated one — we'd flag this if your specific scale seems likely to matter.

Shared media library configuration
$109.32 · delivered in 48 hours · needs WP admin login, SFTP access

Related fixes

If this is the second time this year

A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.

See care plans

Your access, your rules

Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.

We back up first, always

Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.

If it is not what you bought

If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.

If we cannot fix it

You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.

If it comes back

Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.

What we are responsible for

If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.