The editorial team uploads rushes to the same hosting as the WordPress site. Documentary launch day saturates shared hosting; the editorial page goes down with the video player. Nobody had separated editorial publishing from video delivery — yet these are two distinct technical jobs.
An online video media project combines two needs: an editorial site (CMS, SEO, paywall, show notes) and a delivery chain (adaptive bitrate, encoding, edge cache). Merging them on classic web hosting is the most common mistake — and often the most expensive when launch traffic spikes.
The right architecture is decided before the first upload, not the day the bandwidth bill or "site unreachable" ticket arrives.
Two stacks, two budgets
| Role | Usual stack | Key metric |
|---|---|---|
| Editorial site | WordPress, Ghost, custom CMS — VPS or entry cloud | Response time, PHP, database |
| Video delivery | Object storage + CDN or Mux, Cloudflare Stream, etc. | Egress, encoding, concurrent viewers |
The site lives on web hosting; video lives on the delivery chain. Reversing roles — serving multi-gigabyte MP4 files from shared Apache or nginx — turns a page host into an improvised streaming server without the guarantees or pricing to match.
Platform, CDN or self-hosting
Platforms (YouTube, Vimeo, Mux, Cloudflare Stream): encoding, device compatibility and CDN included — less operational load. Ideal to start or if the team has no dedicated sysadmin.
S3-compatible self-hosting + CDN: full control, egress cost to watch closely. Model budget with our hosting budget guide and anticipate traffic spikes described in marketplace and hosting.
Classic mistake: serving large MP4 files directly from shared web server. Even one viral file can saturate outbound link and slow the entire site.
Bandwidth: a mandatory calculation
Rough transfer volume estimate:
GB transferred ≈ views × duration (s) × bitrate (Mbps) / 8 / 1000
Example: 10,000 views × 600 seconds × 5 Mbps ≈ 3.7 terabytes egress. On cloud, egress bill can far exceed web server cost. On "unlimited" shared hosting, it is a provider email and throttling.
Size for peak (launch, social buzz), not monthly average. A video going viral changes project physics overnight.
Live and VOD: two different requirements
Video on demand (VOD) suits object storage, long CDN cache and predictable cost if the catalog is stable.
Live streaming requires ingest, real-time transcoding and low-latency CDN — rarely the same infrastructure as a blog. Size for peak concurrent viewers, not stream average.
For Iberian or European audience, cross-check point-of-presence location with our Spain data and Netherlands and CDN guides depending on targets.
The peak: video does not scale like editorial content
Here is what "site + media included" quotes leave unsaid.
Separating early costs less than emergency migration on launch day.
Decide and move forward without blind spots
Before the first production rush, align editorial and technical teams on a concrete plan. Separate the editorial CMS from the video pipeline — two budgets, two owners. Estimate egress on a peak scenario (modest virality or marketing launch). Choose a turnkey platform or object storage plus CDN depending on control required. Lighten WordPress: no 500 MB files in uploads for long-format streaming. Load-test the player seven days before launch day, with monitoring on site and video chain. Finally document who pays what if quota is exceeded.
Compare site hosts via the directory; evaluate CDN and streaming separately.
Frequently asked questions
Can videos be hosted on the same shared hosting as the site?
Possible for very small volume. Once files grow or streaming scales, separate: object storage plus CDN or dedicated platform. Shared hosting is not sized to serve heavy media in a loop.
YouTube/Vimeo or self-hosting?
Platforms reduce operational load and initial cost. Self-hosting or dedicated CDN is justified for editorial control, no ads or rights constraints — with egress budget to calculate.
What bandwidth cost should you plan for?
Model views × duration × bitrate. One terabyte of egress can cost very differently by provider. Do not rely on VPS price alone.
Recommended architecture for WordPress and video?
Light CMS on VPS or entry cloud; video files on object storage plus CDN or streaming host; embedded player; RSS and metadata on site, not video bytes.
Next time someone puts a video in wp-content, ask how many terabytes of egress if it goes viral. The answer decides architecture — not WordPress drag-and-drop comfort.