Esports Streaming

Esports tournaments with sub-second video, on your own site

Casters, players and viewers react to the same moment. CreekX delivers WebRTC in under a second in our tests, carries chat, and can send the same match to Twitch and YouTube at the same time.

01triggers

When delay spoils the match

On a platform stream the audience is 5 to 30 seconds behind the game. That is fine for watching, and it breaks everything interactive: chat celebrates a round the caster has not reached, a prediction closes after the result is known, and a venue screen showing the stream is visibly behind the players sitting under it.

Chat reacts before the video

WebRTC measured 0.49 seconds median in our tests, and 0.41 seconds with the encoder set for real time. At that delay chat, casters and the venue screen stay on the same moment.

You want your own site and the platforms

Restream to several platforms at once while your site plays it live. The server copies the feed to Twitch, YouTube, Kick or any RTMP or SRT destination without re-encoding, so it costs little processor.

Players join from home

Bring remote players or casters in as live guests. A browser room takes up to five guests with their cameras, mixed in your browser and sent live. Game capture itself still comes from the production PC.

A mechanical gaming keyboard lit with blue and purple backlighting on a bright desk
Players react in tens of milliseconds. A stream that is 20 seconds behind them cannot be part of the event.
02process

How it works

One programme feed in, three ways out. The longer walk-through is in the esports tournament streaming guide.

Send the program feed

From OBS or a production switcher, over RTMP, or SRT if the venue line is unreliable. Turn B-frames off and set a keyframe every second: with OBS defaults the same server measured 1.70 seconds over WebRTC instead of 0.41. Steps: go live from OBS.

Deliver in real time

WebRTC to your site, low-latency HLS for large audiences. WebRTC viewers each hold a connection to your server; low-latency HLS is plain HTTPS and can go behind a CDN when the audience outgrows one server’s port.

Restream and record

Platforms at once, VODs afterwards. Turn on recording for the stream and each match lands in the video library when it ends, ready to share or to play as a 24/7 channel between events.

Diagram: a tournament production PC sends RTMP or SRT to a creekX server, which delivers WebRTC to the tournament site, restreams to platforms and records the match
The tournament path on one server. Delay figures: creekX 2026.10.13, 1080p source, measured on a local network. Conditions are on the benchmarks page.
03deliverables

What you get

  • WebRTC playback measured under a second on a local network
  • Chat beside the player, with moderation
  • Restreaming to up to 10 destinations per stream, without re-encoding
  • Live guests in a browser room, up to five
  • Recordings and VODs on your own disks
  • Private links or tokens for scrims and closed qualifiers
04protocol fit

Which protocol for venue, site and platforms

A longer comparison of the two low-delay options: WebRTC and low-latency HLS compared.

Protocol choices for a tournament. Delay figures are creekX’s own measurements on a local network.
LegProtocolMeasured delayUse it for
Production PC to serverRTMP, or SRT on a weak lineNot measured separatelyThe programme feed, B-frames off, keyframe every second.
Server to your tournament siteWebRTC0.41 s median tuned; 1.70 s with OBS defaultsViewers who chat, predict or sit in the venue.
Server to a large online audienceLow-latency HLS1.23-1.28 s median, 1.40 s worstMore viewers than one port carries; CDN in front.
Server to Twitch, YouTube, KickRTMP restreamThe platform’s own delayReach. The feed is copied, not re-encoded.
Venue screensHLS in the Android kiosk player, or WebRTC in a browser3.4-3.8 s / 0.49 s medianUse a browser where the screen must match the stage.
05sizing and cost

A sizing example: a weekend qualifier

From our test on a 4 vCPU, 8 GB server: 500 WebRTC viewers of one 1080p stream at 2.5 Mbit/s used 37% of the processor, and the server sustained about 890 Mbit/s of upload.

  • Source: one 1080p programme feed. Fast games need more bitrate than our 2.5 Mbit/s test clip; 6 Mbit/s is a common choice.
  • Viewers on your site: at 6 Mbit/s, 890 Mbit/s of upload carries about 148 WebRTC viewers. At 720p and 3 Mbit/s it carries about 296. Both are calculated from the port.
  • Everyone else: restream to the platforms, which costs the server one extra copy of the feed per destination.
  • Data: 148 viewers at 6 Mbit/s for an eight-hour day is about 3,200 GB sent.
  • Recording: a 6 Mbit/s feed writes about 2.7 GB an hour (calculated), about 43 GB for two eight-hour days.
  • Licence: Media Server Pro is USD 99 per server each month. No fee per viewer, match or hour.

A sensible split is WebRTC on your own site for the people inside the event, and platforms for the wider audience. Size a final with CreekX.

06First-party evidence

Measured delivery delay, with the test conditions

In a first-party test on 13 October 2026, CreekX 2026.10.13 measured a median delay of 0.49 seconds for WebRTC, with a worst result of 0.68 seconds. Low-latency HLS measured 1.23-1.28 seconds at the median and 1.40 seconds at worst. Standard HLS measured 3.4-3.8 seconds at the median and 4.4 seconds at worst. The test used the standard one-line installer on an Ubuntu 24.04 cloud server with 4 vCPU, 8 GB memory, a 100 GB NVMe disk and about 890 Mbit/s upload bandwidth. The source was a real 1080p, 25 fps H.264 clip at 5 Mbit/s, sent from OBS and viewed on a laptop over the local network. Each step ran for 60 seconds. These are product measurements under the stated conditions, not results from a sports customer deployment or a promise for each viewer.

07honest limits

What creekX does not do for esports

  • No overlays, scoreboards, brackets or instant replay. Those are made before the feed reaches creekX.
  • No measured 1080p60 result yet.
  • No DRM, no subscriptions and no built-in paywall. Access uses private links, tokens or your own approval check.
  • WebRTC viewers receive one quality. Viewers on weak connections need HLS with several qualities.
  • One server per installation; an audience of thousands on your own site needs a CDN and a rehearsal.
08Scope & limitations

Know where the security and data boundary sits

CreekX has no telemetry and can run with an offline licence and offline installation package supplied through sales. Video and the installed product’s operational account data remain on the customer-controlled server during local operation. Website and sales enquiries are separate. Enabling an off-site backup, external storage, restream destination or another outbound integration creates a corresponding outbound data path. Recorded video and library files are not encrypted by CreekX on the customer’s disks; use server-level disk encryption when encryption at rest is required. Viewer-security features have been checked through CreekX automated tests, but no formal third-party security certification or assessment has been completed.

09buyer fit

Start with a trial or speak to CreekX first

Start the trial yourself

The 14-day Media Server trial is available without a credit card. It includes the Media Server feature set with trial limits of five 24/7 channels, five restream destinations per stream and 500 library videos. Installation requires an internet connection. Your content is kept when the trial ends. Add a paid licence to continue using licensed features and creating channels after the trial and any applicable licence grace period.

Speak to CreekX before installing

Contact CreekX first if the deployment must be fully offline or air-gapped, will use several servers or more than 50 concurrent live streams, expects thousands of viewers, forms part of a tender, or needs installation, training or Enterprise support. CreekX currently operates one server per installation, so the team should check hardware, network capacity and product fit for a large audience before the trial.

10faq

Questions from tournament organisers

How low is the delay?

0.49 seconds median over WebRTC in our tests on a local network, 0.41 seconds with B-frames off and a one-second keyframe. The internet adds its own delay, and we have not measured viewers across home networks. The measurements are in where live stream delay comes from.

Can we still stream on Twitch?

Yes. Restream the same match to several platforms at once. Platform viewers keep the platform’s own delay; viewers on your site get the WebRTC delay. Steps: YouTube, Facebook and more at once.

Does CreekX add overlays or a scoreboard?

No. Add graphics in OBS or your switcher before sending. creekX carries the finished programme.

Does it handle 60 frames a second?

creekX passes the encoder’s video through without converting it, so the frame rate is whatever OBS sends. Our measurements used 25 and 30 fps sources. We have not measured 1080p60 at game bitrates, so test it on the trial before a final.

How many viewers can one server hold?

The network port decides. A 4 vCPU server sent one 1080p stream at 2.5 Mbit/s to 500 WebRTC viewers at 37% CPU. On 890 Mbit/s of upload that is about 340 viewers at 2.5 Mbit/s, or about 148 at a 6 Mbit/s game bitrate, calculated from the port.

Can a qualifier be private?

Yes. Leave the public watch link off and send teams a private link that expires, or one-time tokens. Steps: who may watch and stream.

Can several matches run at once?

Yes, each as its own stream. Receiving streams is cheap: 49 at once used 13% of a 4 vCPU server. Making several qualities for weak connections costs about 0.6 of a core per match.

11Your next step

Run your next qualifier on it

Try the trial with one match, then size the final with CreekX.

Follow the build