Members CMS
PHP 8.1+ & MySQL Buy license · $349.95
Media library

How to organise one media library for several websites

Keep every image, video and story in one central library and feed several websites from it. Folder structure, naming, IDs and statuses that scale.

Updated 5 minute read The Members CMS team

Once you run more than one or two websites, media has a habit of spreading out. A photo set lives in one site's upload folder, a slightly different copy sits on another site, and the video you edited last month only made it to the newest site. Before long nobody is sure which version is the real one, or where it has already been shown.

The fix is to treat your content as one central library and treat each website as a view of that library. This guide covers the structure, naming and statuses that keep a shared library tidy as it grows from a few hundred files to many thousands.

One original, many websites

The single most useful rule is this: keep exactly one original of every file. Websites should not own their own copies. Instead, each website has its own rules about which items from the central library it may show, and it draws matching content straight from that library.

Working this way has some clear benefits:

  • Less storage. A video used on four sites is stored once, not four times.
  • No out-of-date copies. If you replace a badly exported image, every site that uses it gets the corrected version.
  • Edits reach everywhere. A fixed title, a new category or a better cover image only needs changing in one place.
  • Clear reach. You can see at a glance which sites an item reaches and which ones leave it out.

If you want to go deeper on sharing the same item between several sites, see reusing content across several sites without duplicating files.

Group files into sets

Individual files are hard to manage in bulk. Most content naturally comes in groups - a photo shoot, a short series of clips, a themed collection - so make the group the main unit you work with. Call it a set. A set has one title, one description, one cover image and one list of categories, and it contains as many images and videos as belong together.

Sets also make publishing simpler. Publishing "the beach shoot" is a lot clearer than handling 37 separate files and hoping none were missed. The easiest way to create sets is straight from your existing folders, one folder per set - our guide to uploading image and video sets in folders walks through preparing them.

Folder structure and stable IDs

It is tempting to name folders on disk after their content: puppy-sit-and-stay. That works until you rename the set, fix a typo or re-categorise it. Then you either live with a misleading folder name or rename the folder and risk breaking anything that points at it, such as backups, thumbnails and saved links.

A sturdier approach is to separate the two jobs:

  • On disk, store each set in a folder named by a stable internal ID, such as set-000001. This never changes.
  • In the database, keep the title, description, categories and the original folder name you uploaded. These can change as often as you like.

Avoid building folder trees by category (for example /dogs/puppies/obedience/). A set usually belongs to several categories at once, and moving folders every time you re-tag something is a recipe for broken links.

Naming that still helps people

Stable IDs are for the system, but people still need to find things. Give every set a clear title, keep the original folder name as a searchable field, and write a short description. Good search across titles, descriptions, folder names, IDs and categories means you rarely need to browse folders at all.

Statuses that scale

A status tells you, and the system, where each item is in your workflow. Keep the list short. Four statuses cover most networks:

StatusMeaningCan go to websites?
DraftJust uploaded, still being checked, titled or taggedNo
ReadyFinished and reviewed, waiting for sign-offNo
PublishedApproved for useYes, subject to each site's rules
ArchivedRetired from use but keptNo

Two points are worth stressing. First, new uploads should always start as Draft, so nothing half-finished leaks onto a site. Second, "Published" means "allowed to be used", not "shown everywhere". Each site still decides, through its own category rules, whether the item appears there at all.

Categories do the routing

With one library feeding several sites, categories are what decide which content goes where. A site about puppy obedience might select Puppies and Obedience; a recall site might select Recall. Each set simply carries the categories that truly describe it, and every site picks out what matches.

That means tagging quality matters more than folder structure. A short, consistent routine for tagging new sets pays off quickly. Our guide to tagging content so it lands on the right sites covers that routine in detail.

A weekly tidy-up checklist

  1. Review Draft items and move finished ones to Ready or Published.
  2. Check for sets with no categories, which no site will pick up.
  3. Merge duplicate or near-duplicate categories.
  4. Look for failed uploads or missing thumbnails and retry them.
  5. Archive anything you no longer want any site to use.

How Members CMS handles this

Members CMS is built as the central library for a network of websites. Each uploaded folder becomes a media set stored under a stable ID such as set-000001, with the original folder name kept separately, so renaming a set or changing its categories never renames anything on disk. Originals are kept as uploaded (unless you opt in to image size reduction), and thumbnails and previews are generated separately.

Every set has a Draft, Ready, Published or Archived status, new sets start as Draft, and only Published content can be considered for a website. The Media Library offers grid and list views, search, filters for status, category, media type, orientation and dates, and bulk actions for categories and status, so the weekly tidy-up takes minutes. Every set also has a content-usage panel showing which websites it reaches. One license covers one installation, and that installation can manage as many websites as you like - see the full feature list.

Frequently asked questions

Should each website have its own copy of the media?

No. Keeping one original of each file and deciding per website what may be shown avoids wasted storage, out-of-date copies and edits that only reach one site.

Should folder names change when I rename a set?

No. Use a stable internal ID for the folder on disk and keep the title in the database. Renaming then never breaks links, backups or anything that points at the files.

What publication statuses do I need?

Draft, Ready, Published and Archived cover most workflows. Only Published items should ever be considered for a website.

Get three guides like this every month, plus software update notices.Subscribe →