Amazon Silk browser user agent
Amazon Silk is the default browser on Fire tablets, Fire TV, and Echo Show devices. It is Chromium-based, so its user agent follows the Chrome pattern and adds a Silk product token. Silk has historically offered a cloud-accelerated mode that routes fetches through Amazon's infrastructure to speed up rendering.
What this means
Amazon Silk ships as the default browser on Fire tablets, Fire TV streaming devices, and Echo Show smart displays. It is built on Chromium, so it carries a Chrome-shaped user agent: Mozilla/5.0, a platform token, AppleWebKit and Chrome markers, and Safari for compatibility, plus a distinguishing Silk product token.
Seeing Silk in your logs indicates an Amazon-ecosystem device. On Fire TV and Echo Show, this also signals a TV or smart-display form factor rather than a phone or desktop.
Cloud-accelerated mode
Silk has offered a split-architecture, cloud-accelerated browsing mode in which parts of page processing and fetching happen on Amazon's servers. In that mode, requests can originate from Amazon infrastructure instead of the device's local network.
This is expected Silk behaviour, not spoofing. Do not classify such requests as datacenter automation purely because of the origin network; the Silk token indicates a human session on a Fire device.
- Engine: Chromium (Chrome-pattern user agent)
- Distinguishing token: Silk plus version
- Optional cloud-accelerated mode may change the request origin
Device and layout context
Because Silk runs across tablets, TVs, and smart displays, the Silk token alone does not tell you the screen size. Where available, use Client Hints or viewport signals to adapt layout rather than assuming a single form factor.
Treat Silk on Fire TV similarly to other smart-TV browsers: human, lean-back, often remote-controlled navigation, which can produce different interaction patterns from desktop or mobile.
How it appears in analytics and logs
A Chrome-pattern user agent containing a Silk token is a human using Amazon Silk on a Fire device. In cloud-accelerated mode, some fetches may originate from Amazon infrastructure rather than the device's own network connection.
Diagnostic use case
Identify visits from Amazon Fire devices, separate Silk from generic Chrome, and understand cloud-acceleration behaviour that can change the request origin.
What WebmasterID can help detect
WebmasterID classifies Silk as a human browser on Amazon devices and notes the device family, so Fire tablet and Fire TV visits are counted as human traffic rather than mislabelled as generic Chrome or as bots.
Common mistakes
- Grouping Silk under generic Chrome and losing Fire-device visibility.
- Flagging cloud-accelerated Silk fetches as datacenter bots.
- Assuming Silk always means a tablet, when it also runs on TV and Echo Show.
Privacy and accuracy notes
Silk is recognised only from the user-agent token. WebmasterID records the device family as coarse context and never infers exact location or builds a fingerprint from Fire-device traffic.
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.
- Tablet user agents
Tablets are the hardest device class to read from a user agent. iPadOS requests desktop-class pages by default, so an iPad can look like a Mac, and many Android tablets omit the Mobile token that phones include. This page explains why tablet detection from the UA alone is unreliable and how to handle it.
- Chrome user agent and its quirks
Chrome's user-agent string is full of historical artefacts: it claims AppleWebKit and Safari for compatibility even though Chrome uses the Blink engine. Google has also reduced the detail Chrome exposes in the UA, moving fine-grained information into User-Agent Client Hints. This page explains the pattern and the quirks.
- Bot vs human
Recognise device browsers like Silk as human, even behind cloud acceleration.
Sources and verification notes
- Amazon — Silk browser developer documentationChromium-based; Silk token; optional cloud-accelerated mode.
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.