The Delulu Blog

Launching MultiStream.cc
Watch Twitch and Kick Together

By Eric Barker · July 2026

If you have ever tried to follow a tournament, a co-stream lineup, or a watch party across Twitch and Kick at the same time, you already know the friction: six tabs, three platforms, volume fighting itself, and a group chat asking which link to open next.

We built MultiStream.cc to remove that friction — one page, every stream visible, a URL you can paste into Discord and everyone lands on the same layout.

Why we built it

The original MultiTwitch project solved half the problem years ago: pack multiple Twitch embeds into a viewport-sized grid and let viewers share a single link. It became the default tool for speedrun watch parties and multi-caster events because the interface stayed out of the way.

Two things changed since then. Kick became a real second platform for live streaming, and the old MultiTwitch codebase was never designed to maintain two embed systems, responsive chat layouts, and modern mobile behavior at once. Rather than fork something fragile, we rebuilt the idea from scratch — same grid-packing logic, new platform adapters, and a codebase small enough to actually maintain.

MultiStream.cc is the result: a Design Delulu Labs product, live at version 0.1.0, intentionally scoped to do one job well.

What it does

At its core, MultiStream.cc is a lightweight multi-stream viewer. You add Twitch and Kick channels, and the page arranges every player in the largest possible 16:9 grid that still fits on screen — the same packing approach MultiTwitch pioneered, updated for wider viewports and optional chat.

• Twitch + Kick together — both platforms on one page via official iframe embeds.
• Responsive grid packing — desktop and tablet fit every stream in view; phones stack streams vertically.
• Shareable path URLs — send /t:username/k:username links so the lineup loads automatically.
• Twitch chat sidebar — show or hide chat on desktop and tablet; the grid reflows instead of covering video.
• Per-stream remove controls — drop a channel without rebuilding the whole layout.
• Static deploy, no backend — no accounts, no server-side storage, no build step required to use it.

Performance depends on how many live embeds you open — each stream is a full platform player. Fewer streams means smoother playback, especially on laptops and phones. That is a platform constraint, not something a wrapper can magically fix, but the layout is designed to keep every stream as large as your screen allows.

How to use it

The fastest path is the toolbar: pick Twitch or Kick, enter a username (or paste a full channel URL), and add. Each stream appears in the grid with its own remove button. Volume lives in each platform's native player UI — cross-origin embeds do not expose volume APIs to the parent page, so there is no master mute slider.

For watch parties, path URLs are the feature that matters. Build a lineup in the address bar:

https://multistream.cc/t:streamer1/t:streamer2/k:streamer3

Use t: for Twitch and k: for Kick. Legacy uppercase prefixes and older query-string formats still work, but the path style is the one worth bookmarking — it is readable, shareable, and survives a copy-paste into chat without breaking.

On desktop, the optional Twitch chat panel docks beside the grid — it resizes the stream layout instead of overlaying players, because clipped Twitch embeds pause when they think they are off-screen. On phones, chat hides entirely and streams scroll in a single column where touch targets stay large enough to use comfortably.

What we intentionally kept small

MultiStream.cc is vanilla TypeScript and Vite — no React, no server, no user database. Each platform is a small adapter file (parseInput, buildEmbedUrl) registered in a shared grid and state layer. Adding a third platform later means adding one adapter, not rewriting the viewer.

That scope discipline is deliberate. Most multi-stream tools either rot quietly or sprawl into features nobody asked for. We shipped the viewer first: grid, URLs, chat, mobile behavior, DreamHost-ready static output. Everything else waits until someone actually needs it.

The project is open source under MIT at github.com/designdelulu/multistream if you want to inspect the embed notes, device matrix, or deployment steps.

Open MultiStream.cc