Puffin browser user agent
Puffin is a browser from CloudMosa that offloads rendering to cloud servers and streams a compressed result to the device. Its user agent carries a Puffin token, and because the cloud does the fetching, requests reach your origin from CloudMosa infrastructure rather than the end user's own network — similar in spirit to other proxy browsers.
What this means
Puffin, developed by CloudMosa, performs much of the page rendering on remote servers and streams a lightweight, compressed view to the device. This cloud-rendering model is designed to speed up browsing and reduce on-device work.
Because the cloud servers do the fetching, the request that arrives at your origin originates from CloudMosa's infrastructure. The end user's own network is not the source IP, which changes how you should interpret the connection.
How it identifies itself
Look for a Puffin product token in the user agent, typically alongside a Chrome/AppleWebKit-style chain since Puffin renders with Blink. The network source will be CloudMosa rather than a typical residential or mobile-carrier network.
Do not treat the CloudMosa server IP as scraping automation to be blocked: a real person is behind a Puffin session. As with any browser, the string is client-supplied, so match the token but interpret the proxy nature correctly.
- Cloud-rendering browser from CloudMosa
- User agent carries a Puffin token
- Requests originate from CloudMosa servers, not the visitor's network
How it appears in analytics and logs
A user agent with a Puffin token indicates a cloud-rendering browser. The fetch is performed by CloudMosa servers, so the connecting IP reflects CloudMosa rather than the human's device or location.
Diagnostic use case
Recognise Puffin's cloud-rendered traffic, understand why its requests come from CloudMosa servers, and avoid mistaking that infrastructure for the visitor's network or for automation.
What WebmasterID can help detect
WebmasterID recognises the Puffin token and its cloud-render model, so its server-originated requests are attributed to a real browser mode rather than mislabelled as datacenter scraping.
Common mistakes
- Blocking CloudMosa's render-server IPs as scraping automation.
- Reading the CloudMosa proxy IP as the visitor's location.
- Confusing Puffin's cloud render with on-device browsing behaviour.
Privacy and accuracy notes
Puffin's cloud-rendering means the request IP belongs to CloudMosa, not the visitor, so it must never be read as the user's precise location. WebmasterID treats the Puffin token as a browser-mode signal only.
Related pages
- Opera Mini user agent
Opera Mini is a data-saving browser that routes page rendering through Opera's servers rather than fully on the device. Its requests carry an Opera Mini token, and because the rendering proxy fetches resources, the originating IP is Opera infrastructure rather than the end user's network. That makes it distinct from on-device browsers.
- Datacenter vs residential traffic signals
People often want to tell datacenter traffic from residential traffic, but the user-agent string carries no network information at all. Network type is a separate, IP-derived signal that must be paired with verification, and described carefully to stay privacy-safe. This page explains what the UA can and cannot tell you.
- Mobile user agents: phones, tablets, in-app
Mobile user agents carry platform descriptors like iPhone or Android and often a Mobile token, but tablets and in-app browsers complicate the picture. An in-app browser (inside a social or messaging app) usually adds its own token to the string. This page explains the patterns and their pitfalls.
- Bot vs human
Separate cloud-render proxy browsers from datacenter automation.
Sources and verification notes
- CloudMosa — technologyOfficial site; Puffin offloads rendering to CloudMosa servers and streams to the device.
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.