Origin Story • Big King Media

Big King Media began as a private solution to a real media problem — and grew into a WordPress Media Operating System.

Big King Media did not begin as a quick public experiment. It began as a practical answer to a real network media problem inside the Trott Bailey environment.

Before public release, the product was developed and used privately for more than five years while handling a very large media-heavy multisite workflow. That is why it entered public release as version 7 instead of version 1. Big King Media was already shaped by real use before it was made public.

What started as a better shared-media workflow for WordPress Multisite grew step by step into something bigger: a connected media system for reuse, publishing, galleries, lightbox, uploads, organization, visibility, media SEO, audio, video, slideshows, music videos, post discovery, and theme-safe public media presentation.

View Big King Media See Photofall at Scale

The first problem

It started with WordPress Multisite media pain.

The first version of the problem was simple: WordPress Multisite made media handling too repetitive, too fragmented, and too wasteful.

Media was trapped inside separate subsites. Teams had to re-upload the same files, hunt down old URLs, switch between libraries, and repeat work just to set one featured image, publish one gallery, or reuse one asset across the network.

Big King Media was built to remove that friction. The first core promise was practical: one cleaner media workflow across the network, less repetition, faster discovery, and more realistic reuse.

Origin point: Big King Media began by solving the real operational headache of managing media subsite by subsite.

The growth path

What began as shared media kept growing because the real workflow was bigger.

Once the shared-media problem was being solved properly, the next truth became obvious: media operations do not stop at shared access. Sites also need front-end publishing, organization, visibility, creative playback, metadata, search, and richer public presentation.

Big King Media grew because the original problem kept leading into the next one. Shared media led into Photofall. Photofall led into lightbox. Upload needs led into frontend uploads. Publishing needs led into featured media, post orchestration, and theme-safe homepage takeovers. Accessibility and discovery needs led into Kaleeyon Media SEO and AI alt text. Creative release needs led into Princess Keilah Studio and the music-video maker line.

Stage 1 — Shared media access Network-wide browsing, reusable media, reduced repetition, and a more practical path from asset discovery to publishing.

Stage 2 — Public media presentation Photofall, responsive masonry, lightbox, shortcode deployment, and theme-safe media surfaces.

Stage 3 — Media intelligence Folders, visibility controls, indexing, AI alt text, media SEO, and stronger metadata workflows.

Stage 4 — Creative media system Princess Keilah Studio, playlists, audio, slideshows, music videos, featured media, and post orchestration.

The category shift

Big King Media outgrew the label “shared media library plugin.”

At first, it could be described as a WordPress Multisite shared media library plugin. That description is now too small.

Big King Media still includes powerful shared-media logic, but the product no longer lives inside that narrow lane. It now spans access, presentation, automation, and orchestration. It supports both multisite networks and ambitious single-site WordPress installations. It upgrades the media stack without forcing a theme rebuild.

That is why Big King Media is now best described as a WordPress Media Operating System.

Access layer

Shared media without the usual cross-site chaos

Network-wide browsing, indexed discovery, zero-duplication reuse, cross-site featured media workflows, and centralized media controls.

Presentation layer

Turn media into on-site experiences

Photofall, lightbox, responsive grids, shortcode deployment, player modes, and theme-safe homepage takeovers.

Automation layer

Accessibility and discovery built into the stack

AI alt-text workflows, bulk remediation, media SEO, interlinking, visibility controls, and metadata support for stronger archives.

Orchestration layer

Operate media like infrastructure

Frontend uploads, folder organization, post-card indexing, curated groups, mixed media-post feeds, and builder-friendly deployment.

Creative layer

Product proof videos

See the system that grew out of the original problem.

The self-hosted product videos are loaded in portrait frames with metadata-only preload. They do not autoplay, but visitors can play each proof video when they are ready.