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

Serving members' media from the same server or a different one

Your content library and your paysites don't have to share a server. How signed, expiring links and local streaming work, and which suits your hosting.

Updated 4 minute read The Members CMS team

When your content lives in one central library and your membership sites live on their own hosting, a practical question comes up quickly: where do members actually load the pictures and videos from? The answer affects speed, hosting costs, security and how much work each paysite server has to do.

There are two sensible patterns. Either members load files from the central server through protected links, or, when a site shares a server with the library, the site streams the files straight from the storage folder. This guide explains how each one works, what a signed, expiring link really is, and how to pick the right option for each of your sites.

Why the location of media matters

Pictures and videos make up nearly all the traffic on a membership site. Page text is tiny by comparison. So the server that delivers media does most of the heavy lifting, and its location shapes several things:

  • Bandwidth and cost. Whichever server sends the files carries the traffic bill.
  • Load. A small paysite server that no longer has to send large videos has more room for everything else.
  • Storage. If files stay in one place, you don't need copies on every site.
  • Security. Wherever files come from, a copied file address should not give free access forever.

Option 1: media from a different server

In this pattern the paysite builds the page, but every picture and video on it points to the central server. Each link is a signed, expiring link: a web address for one file with two extra pieces added. One is a code that proves the link was issued by your system. The other is a time after which the link stops working.

When a member's browser asks for the file, the central server checks the code and the time. If the code is wrong or the time has passed, it refuses. That means a link pasted into a forum or shared with a friend goes dead soon after, and nobody can guess the address of another file by changing a number.

This option suits you when:

  • Your paysites are on separate or older hosting accounts.
  • You want the central server, which may have more storage and bandwidth, to carry the media traffic.
  • You would rather the paysite servers did as little work as possible.

The trade-off is that the central server needs enough bandwidth for all your sites together. With a good host, members rarely notice any difference in speed.

Option 2: media from the same server

If a paysite runs on the same server as the content library, there is no need for files to travel between servers at all. The site can read files directly from the library's storage folder and send them to the member itself.

Protection still matters here. The storage folder should sit outside the public web folder, so no file can be reached simply by typing its address. Instead, the site hands out signed tokens that work in the same way as signed links: the file is only sent if the token is genuine and still valid.

This option suits you when the library and one or more sites share a server, because it avoids an extra round trip and keeps everything in one place.

Comparing the two

Different serverSame server
Who sends the filesThe central library serverThe paysite, from the storage folder
ProtectionSigned links that expireSigned tokens
Copies on the paysiteNoneNone
Paysite server loadLowHigher, as it sends the files
Best forSites on separate hostingSites sharing a server with the library

You don't have to choose one pattern for everything. A network often has a few sites on the main server and others elsewhere, and each can use whichever suits it.

For example, imagine a network of three sites: a fitness site and a cooking site hosted on the same server as the library, and an older travel site on a separate hosting account. The fitness and cooking sites can stream straight from the storage folder, while the travel site loads its media from the central server through signed links. If you later move the travel site onto the main server, you simply switch its mode. When planning that main server, our guide to what you need to self-host a content CMS covers disk space and other requirements.

Practical tips

  • Use HTTPS everywhere, on the central server and on every site, so links and tokens cannot be read in transit.
  • Keep server clocks accurate. Expiry times depend on both servers agreeing roughly what time it is.
  • Plan bandwidth for the busiest server. If the central server sends media for several sites, size its hosting for their combined traffic.
  • Keep storage outside the web root. Our guide to protecting member media from direct links explains why this matters so much.

How Members CMS handles this

Members CMS never copies media to your websites. Each registered website has its own delivery mode. With "different server", files load from Members CMS through signed links that expire. With "this server", the connector streams files straight from the storage folder using signed tokens. Media is only ever served through access-checked URLs, and the installer suggests a storage folder outside the web root.

The connector needs PHP 7.2 or newer on each website, so older paysite servers can use either mode. Our guide to connecting your membership sites to one central library covers setting up the connector, and the self-check page confirms the connection and clock are working before members see anything.

Frequently asked questions

What is a signed, expiring link?

A web address for one file that includes a code proving it was issued by your system and a time after which it stops working, so shared links soon go dead.

Is it slower to serve media from another server?

Members load pictures and videos from the central server instead of the paysite. With a good host the difference is small, and the paysite does less work.

Can different websites use different modes?

Yes. Each website has its own setting, so sites on the same server can stream locally while others use signed links.

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