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

What you need to self-host a membership content CMS

PHP, MySQL, an image library, FFmpeg and cron: a checklist for hosting a central media CMS, and the questions to ask your host before buying.

Updated 5 minute read The Members CMS team

Self-hosting a content system means it runs on your own web server rather than someone else's platform. You keep control of your files, your data and your costs, but you also take responsibility for giving the software what it needs to run. For a CMS that stores large image and video libraries, that means more than just PHP and a database.

This guide is a checklist of what a central media CMS typically needs, why each part matters, and the questions to ask your hosting company before you buy anything.

The core software stack

Most self-hosted PHP content systems need the same basic pieces. Check each one with your host.

ComponentWhat it doesWhat to check
PHPRuns the applicationThe exact version required, and that you can choose it
MySQL or MariaDBStores titles, categories, website rules and settingsThat you can create a database and user
Apache or NginxServes the admin pagesThat URL rewriting is available
HTTPS certificateEncrypts logins and mediaFree certificates are offered by most hosts
Cron jobsRuns background work and scheduled backupsThat you can add a job running every few minutes
GD or ImageMagickCreates thumbnails and previewsWhich one is installed, and whether ImageMagick is available for unusual formats
FFmpeg and FFprobeReads video details and makes postersThat both programs are installed and allowed to run

Why media tools matter

A plain blog can get by with PHP and a database. A media library cannot. Every uploaded photo needs a thumbnail, and every video needs a poster image and details such as duration, resolution and codec. Those jobs are done by separate programs on the server.

Image processing

An image library such as GD or ImageMagick resizes images into thumbnails and previews without touching the originals. ImageMagick also copes with very large images and formats such as HEIC, TIFF and AVIF that simpler libraries cannot read. Our guide to portrait, landscape and square galleries explains why orientation detection matters.

Video processing

FFprobe reads a video's details and FFmpeg creates a still poster frame, and can also make a browser-playable copy of formats that would not otherwise play. These are the tools most often missing on shared hosting, because some hosts don't allow programs like these to run. If your host doesn't offer them, video features won't work fully, so ask before you buy.

Shared hosting, VPS or dedicated server?

You have three broad choices:

  • Shared hosting is cheap and managed for you, but you share resources with other customers and often cannot install extra software such as FFmpeg. It may work if the host already provides everything on the list.
  • A VPS (virtual private server) gives you your own slice of a server with full control over what is installed. It is the most common choice for a media CMS.
  • A dedicated server gives you a whole machine. It suits very large libraries or heavy video processing.

If you are unsure, a VPS with a control panel such as cPanel is a good middle ground. You get the control you need with a familiar interface for things like databases and cron jobs.

Disk space and backups

Media libraries grow quickly, and video takes far more space than images. A rough way to estimate what you need:

  1. Add up the size of your original media.
  2. Add around 5 to 10 percent for thumbnails, previews and posters.
  3. Add room for growth over the next year or two.
  4. Add space for backups, or plan to store them elsewhere.

For example, 200 GB of originals might need 210 to 220 GB for the library itself, before growth and backups. Keeping at least one backup copy away from the server is strongly recommended. Our guide on backing up a media library and its database covers this in detail.

Upload limits matter too. Browsers and PHP settings often cap file sizes. For very large sets it is usually easier to copy folders to the server by SFTP and import them from there.

Memory and processor power matter mainly for media processing. Making thumbnails for a big batch of photos, or reading details from long videos, can keep the server busy for a while. Running these jobs in the background means the admin area stays usable while they work.

Questions to ask your host

Before buying, send your host a short list like this:

  • Which PHP versions can I use, and can I switch between them?
  • Do I get MySQL or MariaDB, and how many databases?
  • Is HTTPS included?
  • Can I add a cron job that runs every few minutes?
  • Are ImageMagick, FFmpeg and FFprobe installed, and can PHP run them?
  • How much disk space is included, and what does more cost?
  • Can I upload by SFTP?
  • Are server backups included, and how often?

The cron question is easy to overlook but important. Background jobs such as thumbnail building and scheduled backups are far more reliable when the server runs them on a timer than when they wait for someone to open a page, and content drip schedules and timed offers depend on it entirely. Our guide on why scheduled releases need a cron job explains more. If your member sites will load media from this server, also read serving member media from another server.

Members CMS requirements

Members CMS is plain PHP with MySQL or MariaDB, so it uploads like any PHP script. The CMS server needs PHP 8.1 or newer (8.2 or 8.3 recommended) with the pdo_mysql, mbstring, fileinfo, json, dom and openssl extensions plus gd or imagick, MySQL 5.7.8+ or 8.x or MariaDB 10.3+, and Apache or Nginx. HTTPS is strongly recommended. Optional extras are the zip, exif and curl extensions, FFmpeg and FFprobe for video posters, details and browser-playable copies, ImageMagick for very large images and HEIC, TIFF, AVIF or BMP thumbnails, and cron for reliable background processing and scheduled backups. Without cron, processing can still run while an administrator has the admin area open, but content drip schedules and timed offer expiry need the cron job. Each website using the connector needs PHP 7.2 or newer, on the same server or a different one.

One license covers one installation on one domain, and that installation can manage unlimited websites. It is a ZIP download with an install.php wizard, activated with an Installation Key, for a one-time price with free updates. See the features section of the home page.

Frequently asked questions

Can I run it on shared hosting?

Usually, yes. Most shared hosts offer PHP 8.1 or newer, MySQL or MariaDB and cron. Make sure cron jobs are allowed, as drip schedules and offer expiry need one. FFmpeg is often missing, which only matters for video posters and playable copies, so check with your host if you use video.

How much disk space will I need?

Roughly the size of your original media plus roughly 5 to 10 percent for thumbnails and previews, plus room for backups. Video takes far more space than images.

Do I need HTTPS?

Yes. The admin area handles logins and private media, so it should only ever be used over HTTPS.

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