Roku and Tizen smart-TV user agents
Roku streaming devices and Samsung's Tizen-based smart TVs issue HTTP requests whose user agents carry platform tokens such as a Roku token or a Tizen token. These mark living-room/TV-platform traffic, letting you separate smart-TV and streaming-device requests from desktop and mobile browsers.
What this means
Roku is a streaming-media platform; Tizen is the operating system Samsung uses on its smart TVs (and some other devices). Both make web requests — for app content, media manifests, or an embedded browser-like component — and both identify their platform in the user agent.
These are not general-purpose desktop browsers. Treat their traffic as a distinct living-room device class.
How they appear
Roku user agents commonly include a Roku platform token. Tizen smart-TV user agents include a Tizen token, often alongside WebKit and a Samsung/SmartTV indicator. The exact layout varies by device and firmware.
Match on the platform token (Roku or Tizen) rather than a version, and remember the string is a claim. Some media clients on these platforms may not look like browsers at all.
- Roku: a Roku platform token in the user agent
- Tizen TVs: a Tizen token, often with WebKit and a SmartTV indicator
- Traffic is often app/media-driven, not general browsing
How it appears in analytics and logs
A user agent carrying a Roku platform token or a Tizen token indicates a streaming device or a Samsung smart TV. It is real traffic from a living-room device class, often app- or media-driven rather than general browsing.
Diagnostic use case
Recognise Roku and Tizen smart-TV traffic, separate it from desktop and mobile, and understand that these platforms behave differently from full browsers.
What WebmasterID can help detect
WebmasterID can classify Roku and Tizen tokens as smart-TV/streaming form factor, keeping living-room device traffic distinct in reporting.
Common mistakes
- Bucketing smart-TV traffic as desktop or mobile rather than a TV form factor.
- Assuming Tizen TV requests behave like a full desktop browser.
- Pinning a firmware version instead of matching the platform token.
Privacy and accuracy notes
These tokens reveal the device platform, not the household or person. WebmasterID treats them as coarse device context only.
Related pages
- Smart TV and game console user agents
Smart TVs and game consoles have built-in browsers and embedded webviews whose user agents include device-specific tokens — a SMART-TV marker, a platform name, or a console identifier. Recognising these connected-TV (CTV) and console tokens separates living-room devices from phones and desktops in your traffic.
- Samsung Internet user agent
Samsung Internet is the default browser on many Samsung Android devices. Built on Chromium, its user agent looks Chrome-like but carries a SamsungBrowser product token. That token is how you recognise Samsung Internet traffic, which is a meaningful share of mobile visits on Samsung hardware.
- PlayStation browser user agent
PlayStation consoles include a WebKit-based web browser. Its user-agent string carries WebKit tokens together with a PlayStation platform token (such as a PlayStation 4 or PlayStation 5 indicator), which lets you recognise console web traffic and separate it from desktop and mobile browsers.
- Privacy-first analytics
See smart-TV form factor as coarse device context.
Sources and verification notes
- MDN — User-Agent header structureRoku and Tizen platform tokens observed in the wild; layouts vary by device, versions not pinned.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.