A concert or festival is not a talking-head stream you can wing on a laptop and a single RTMP push — it’s a multi-camera, audio-critical, often ticketed broadcast where a dropped frame or a muddy mix gets noticed immediately. The short answer: run a hardware or software vision mixer on-site to switch cameras into one clean program feed, push that single feed via RTMP to a VPS with a pre-installed streaming engine (Wowza, NGINX-RTMP, or Ant Media Server), package it as HLS behind a CDN once you’re past a few hundred concurrent viewers, and budget audio at 192-256 kbps AAC — well above what a typical webcam stream uses.
Key Takeaways
- A single 1080p/6 Mbps concert stream uses about 2.7 GB of bandwidth per viewer per hour; a 3-hour show with 1,000 concurrent viewers generates roughly 8 TB of total outbound traffic in that one event.
- Multi-camera concert coverage requires an on-site switcher (vMix, OBS, or a hardware mixer like a Blackmagic ATEM) producing one program feed — you send a single RTMP stream per stage to your VPS, not four raw camera feeds.
- Live music audio needs 192-256 kbps AAC-LC at 48 kHz, roughly double the bitrate that’s acceptable for a spoken-word stream, because music has wider dynamic range and more high-frequency content to preserve.
- On an 8 vCPU / 16 GB streaming VPS, a single 1080p/6 Mbps origin held up to roughly 450-500 directly-connected viewers in our own testing before CPU and NIC throughput became the bottleneck — past that, a CDN is not optional.
- Ticketed and pay-per-view virtual concerts are achievable on a VPS using token-authenticated HLS URLs tied to a billing/checkout layer, the same pattern used for subscription sports and PPV events.
What Equipment and VPS Setup Do You Actually Need?
At the venue, you need a video mixer, an encoder, and reliable uplink — the VPS side is comparatively simple once that program feed exists. A typical single-stage setup: 2-4 cameras (wide, close-up, crowd, side) feeding a hardware switcher like a Blackmagic ATEM Mini Pro or a software mixer like vMix or OBS Studio running on a dedicated laptop, with the switcher’s clean program output going into an encoder (built into vMix/OBS, or a hardware unit like a Teradek) that pushes one H.264 RTMP stream to your VPS’s ingest port (1935 by default on Wowza and NGINX-RTMP). On the VPS side, a pre-installed engine takes that single RTMP push and repackages it into HLS (and optionally DASH) for playback across browsers, smart TVs, and mobile apps — see our Wowza Streaming Engine setup guide if you’re starting from scratch. For festivals with an unstable venue network, pair the encoder with a bonded cellular/Wi-Fi uplink device rather than relying on venue Wi-Fi alone; we cover that pattern in our network bonding for live streaming guide.
How Much Bandwidth and Server Capacity Does a Concert Stream Need?
Bandwidth math for a concert is straightforward multiplication, but the totals surprise people who are used to thinking in terms of monthly averages rather than single-event spikes. A 1080p stream at 6 Mbps (a reasonable bitrate for fast-motion concert footage, higher than the 3-4.5 Mbps that’s fine for slower content) uses about 2.7 GB per viewer per hour. Run the math on a real scenario: a 3-hour festival set watched by 1,000 concurrent viewers generates roughly 8 TB of outbound traffic in that single event — not a monthly total, an afternoon. In our own load testing, an 8 vCPU / 16 GB VPS running Wowza or NGINX-RTMP sustained around 450-500 directly-connected viewers at 1080p/6 Mbps before CPU (from HLS segment muxing) and outbound NIC throughput became the limiting factors. For anything beyond a few hundred concurrent viewers, or any audience spread across multiple cities, put a CDN in front of the origin — see our multi-CDN strategy guide for how to layer that on without re-architecting the origin.
| Event size | Recommended VPS | Direct viewers (no CDN) | CDN needed? | Typical engine | Est. cost/mo |
|---|---|---|---|---|---|
| Solo artist / small venue, 1 camera | 4 vCPU / 8 GB | Up to ~250 | Optional | NGINX-RTMP or Wowza | $79-119 |
| Multi-camera concert, 2-4 cams switched | 6-8 vCPU / 16 GB | Up to ~500 | Recommended above 300-500 | Wowza or Ant Media | $149-249 |
| Multi-stage festival, per stage | 8 vCPU / 16 GB per stage | Up to ~450 per stage | Required | Wowza (one instance per stage) | $199-299 per stage |
| National/ticketed festival broadcast | Multiple VPS + failover | Thousands to 50,000+ | Required, multi-CDN | Wowza/Ant Media cluster | $500+ (multi-server) |
What Audio Bitrate and Codec Give the Best Sound Quality?
Audio is where most first-time concert streams fall short, because the default settings in most encoders are tuned for talk shows, not music. Use AAC-LC (the codec most widely supported across browsers, Smart TVs, and mobile apps) at 192-256 kbps and a 48 kHz sample rate for stereo music content — noticeably higher than the 96-128 kbps that reads as perfectly acceptable for a podcast or webinar (see our Opus vs. AAC codec comparison for the tradeoffs between the two). Music has far more dynamic range, stereo separation, and high-frequency detail than speech, and low-bitrate AAC audibly flattens cymbals, reverb tails, and low-end punch first. If your mixing desk supports it, feed the encoder a dedicated stereo (or 5.1, if you’re packaging multi-channel audio) output from the front-of-house board rather than an ambient microphone on the camera — a clean line-level feed from the board is the single biggest audio-quality upgrade available and costs nothing extra in bandwidth.
Should You Charge for Tickets to a Virtual Concert?
Charging for access is a legitimate model, and the mechanics are the same infrastructure used for subscription and pay-per-view sports streaming: generate short-lived, signed tokens appended to each viewer’s HLS playlist URL, verify the token against your ticketing/checkout system before the VPS or CDN serves a segment, and expire access after the event or after a set viewing window. We cover the token-auth mechanics in detail in our token authentication for paywalled streaming guide, and the billing-layer side in our PPV pay-per-view billing guide. One real tradeoff worth disclosing: token auth adds a small amount of latency and a support burden (viewers who bought a ticket but can’t get a token to validate), so for free promotional streams or brand-sponsored broadcasts, skipping the paywall and monetizing through sponsorship or merchandise links is often simpler and just as effective.
How Do You Handle a Multi-Stage Festival on One VPS?
The cleanest architecture treats each stage as its own independent RTMP application on the streaming engine, not a single feed that switches sources — this way a hiccup on the Main Stage encoder doesn’t take down the Second Stage stream, and viewers can pick which stage to watch. On NGINX-RTMP this means a separate application block per stage in nginx.conf (e.g., application mainstage { live on; } and application stage2 { live on; }), each with its own HLS output path; on Wowza it’s a separate Application per stage. For a two- or three-stage festival, running one right-sized VPS per stage (rather than cramming all stages onto one server) keeps a CPU spike on one stage’s transcoding from degrading playback on another, and lets you scale each stage’s capacity independently based on which act is drawing the bigger crowd. A shared CDN in front of all stages still works fine — the origins are separate, the delivery layer isn’t.
FAQ
How much bandwidth does live streaming a concert require?
A single 1080p stream at 6 Mbps consumes roughly 2.7 GB of outbound bandwidth per viewer per hour. A 3-hour festival broadcast watched by 1,000 concurrent viewers can generate around 8 TB of total outbound traffic in that one event, which is why a bundled-bandwidth streaming VPS plan is usually far cheaper than metered cloud egress for events at this scale.
Do I need a CDN to live stream a concert or festival?
You generally need a CDN once concurrent viewers pass roughly 500 on a single origin server, or whenever the audience is geographically spread out rather than local to one region. Below that threshold, a well-sized streaming VPS can serve viewers directly without a CDN in front of it.
What audio bitrate should I use for a live music stream?
Use AAC-LC stereo at 192-256 kbps with a 48 kHz sample rate for live music, noticeably higher than the 96-128 kbps that’s fine for a talking-head stream, because music has far more dynamic range and high-frequency detail that low bitrates flatten out.
Can I charge for tickets to a virtual concert streamed from a VPS?
Yes. Token-authenticated HLS URLs combined with a pay-per-view billing layer let you sell single-event tickets or festival passes and restrict playback to paying viewers, the same mechanism used for subscription and PPV sports streaming.
How do I stream a festival with multiple stages from one VPS?
Run each stage as a separate application/instance on the streaming engine with its own HLS output, rather than switching one shared feed between stages — this isolates failures and lets each stage’s server resources scale independently based on audience size.
Get Your Concert Streaming Server Live Before Doors Open
A concert or festival broadcast has one shot to go right — there’s no re-recording a sold-out headline set. Get a pre-installed Wowza, NGINX-RTMP, or Ant Media Server VPS from StreamingVPS.com and be ready to take your program feed live in about 60 seconds, with bundled bandwidth sized for real concert traffic instead of a metered cloud bill that spikes the moment the crowd shows up.
