Kick.com on any website.

Kick exposes three useful content primitives through its public web endpoints and each maps to a different job. A live channel embed drops the Kick player iframe pointed at kick.com/yourname into your page, plays the live stream the moment the channel goes on, and goes to a configurable offline state when the streamer is not live. This is the right primitive for a personal homepage, a creator landing page, or any place where the goal is to convert visitors into live viewers. A VOD list pulls past broadcasts from the channel videos endpoint, surfaces them in a wall layout, and auto-includes new VODs as the streamer goes live and Kick saves the archives. This is the right primitive for a content library, a multi-VOD highlight page, or any place where the back catalogue matters more than the live moment. A category leaderboard pulls the top live streams in any Kick category at /categories/{slug}, ranks them by current viewer count, and refreshes every minute so the leaderboard always shows what is actually hot right now. This is the right primitive for a fan site, a category-specific community hub, or a discovery page that wants editorial freshness without manual curation. Picking correctly at the start saves you a re-embed cycle later, and Poper supports all three from the same widget config so you can switch primitives without rewriting your site code. There is also a fourth option worth knowing about: the Kick clips endpoint, which surfaces individual highlight clips with permanent slugs. Clips are the most durable Kick content type because they survive even if the source VOD is removed, which makes clip reels the right addition for sponsor pages and press kits where the same embed needs to keep working for years.

Every Kick widget on the market is gated by the same thing: Kick.com does not currently publish a stable, OAuth-secured developer API the way Twitch Helix does. What exists instead is a set of publicly readable web endpoints under kick.com/api that the Kick site itself uses, including kick.com/api/v2/channels/{slug} for channel metadata and live state, /api/v1/channels/{slug}/videos for VOD lists, and /api/v2/categories/{slug} for category leaderboards. These endpoints return JSON, are not officially documented for third-party use, and have informal rate limits enforced via Cloudflare. Most third-party Kick widgets either query these endpoints from the browser (which means every visitor to the embedding site triggers a direct Cloudflare call, hits the rate limit within minutes, and dies) or skip live polling entirely (which means the LIVE indicator stays stuck at whatever state was true on page load). Poper handles every Kick call server-side from a small pool of dedicated outbound IPs, caches responses at the global CDN edge, and pushes live-state changes to your embedded widget via WebSocket. The result is roughly 100x more headroom than a browser-based widget plus zero exposure of the embedding site visitor to Cloudflare challenges. We refresh channel metadata every 60 seconds for live status on Pro and 30 seconds on Business, refresh VOD lists every 6 hours, and refresh category leaderboards every 60 seconds because rankings move that fast. If Kick ships an officially documented developer API with OAuth in the future, Poper will migrate to it immediately so authorized features like sub-only VODs become accessible without any change to your widget config.

The Kick player iframe has three quirks that catch every widget builder by surprise the first time. First, autoplay is blocked by default in every modern browser unless the iframe is muted. Kick returns a static thumbnail with a click-to-play prompt when autoplay is enabled with audio, which kills any embedded experience where the visitor expects sound on first frame. The fix is to default the player to muted=true, autoplay=true on first load and let visitors click to unmute, which Poper does by default. Second, the player iframe at kick.com/embed/{channel} requires the embedding domain to be allowed via the parent= query parameter, the same way Twitch and Vimeo work. If your domain is example.com, the iframe must be loaded with parent=example.com or it will return a refused-to-display error. Custom subdomains, staging environments, and preview deployments all need their own parent values. Poper auto-injects the parent value from window.location.hostname so this never breaks across environments. Third, mobile playback uses a different player surface than desktop and requires playsinline=true to avoid the iOS native fullscreen takeover. Most third-party widgets ship the desktop iframe code on mobile, which is why so many Kick embeds black-screen on iPhone. Poper detects mobile user agents and serves the playsinline-enabled mobile player. On the polling side, the Kick channel endpoint is the source of truth for live status. A naive widget either never polls (so the live indicator stays stuck at whatever state was true on page load) or polls from the browser (which leaks visitor IPs into Kick's rate-limit pool and dies within minutes). Poper polls server-side every 60 seconds on Pro and 30 seconds on Business, pushes the result to connected widgets via WebSocket, and falls back to a 60-second client poll if the WebSocket connection drops.

Kick stores past broadcasts as VODs in a similar way to Twitch, with auto-saved archives appearing in the channel videos endpoint within minutes of a stream ending. Unlike Twitch, Kick does not enforce a 14-day expiry on VODs for non-Partner accounts, which means the back catalogue tends to be much deeper on Kick channels. Poper renders all VODs returned by the channel videos endpoint by default and lets you filter by date range, length, or title regex per widget instance. Clips work the same way as Twitch clips: short permanent-slug highlights that survive even when the source VOD is removed, served as MP4s from Kick's CDN, and load 4x faster than the live channel embed because they have no parent-domain requirement. The honest part of any Kick widget conversation is content policy. Kick was founded in late 2022 by a group that includes the owners of the Curacao-licensed crypto-casino Stake.com, and the platform's permissive stance on gambling, slots streaming, and IRL content is structural to its appeal. Most of the largest Kick channels stream slots, casino games, or other gambling content sponsored by Stake. The 95/5 creator revenue split that Kick markets aggressively is partially funded by gambling sponsorship economics rather than ad revenue. None of this is illegal, but it is fair to know what you are linking to when you embed a Kick category leaderboard or a top-streamer roster on your site. Poper renders the same content Kick itself surfaces, including mature-content warnings on flagged channels, and never editorializes the Kick feed beyond what the platform's own metadata flags.

The default Kick player iframe is one of the heaviest single resources you can put on a page. A single embedded channel pulls roughly 600KB of JavaScript on first load, sets multiple third-party cookies (including some routed through Stake-affiliated analytics domains), blocks the main thread for several hundred milliseconds during initialization, and frequently regresses Largest Contentful Paint by 1.2 to 2.0 seconds. Embed a multi-channel team lobby with five players and you can lose 22 Lighthouse points before any other code runs. The fix is the lite-player pattern, which renders only the thumbnail (pulled from the Kick channel endpoint or the channel preview image) and a play button overlay (under 6KB per channel) on initial load, and only swaps in the real Kick iframe when the visitor clicks play. The same pattern works for VODs and category cards. Poper ships lite mode as the default, so all the Kick content you embed costs you no more LCP than the same number of static images. Visitors who click see the full Kick player with chat overlay, quality controls, theatre mode, and every native feature included. Visitors who scroll past pay nothing. The performance difference between lite mode and standard iframe embeds is the difference between a 90+ Lighthouse score and a 65. There are three additional optimizations Poper applies on top of lite mode. First, channel thumbnails are served from Kick's CDN and converted to WebP on the fly through our edge layer, which typically halves thumbnail weight versus the default JPEG. Second, the play-button overlay uses a single inline SVG instead of an image request, which saves a round trip per channel. Third, when a visitor does click play, the iframe is loaded with the muted=true playsinline=true autoplay=true parameters and the correct parent= value, which avoids the autoplay block, the iOS fullscreen takeover, and the parent-domain refusal in one shot. The combined result is that a page with a five-channel Kick team lobby in lite mode often outperforms a page with one standard Kick embed on every Core Web Vitals metric. If page speed matters to your SEO, this is the single biggest reason to choose carefully which Kick widget you embed.