Ecosia browser user agent
Ecosia, known for its tree-planting search engine, also offers its own Chromium-based browser on desktop and mobile. Because it is built on Blink, its user agent looks Chrome-like, and it may add an Ecosia or EcosiaApp token. That token, where present, distinguishes Ecosia browser sessions from mainline Chrome.
What this means
Ecosia is best known as a search engine that funds tree planting, but it also distributes its own browser on desktop and mobile. The browser is built on Chromium, so it shares Chrome's engine and presents a Chrome-style user agent.
To distinguish it, Ecosia's browser or app may add an Ecosia-related token (for example an EcosiaApp token on mobile). Without that token, detectors that only match Chrome will fold Ecosia browser traffic into Chrome.
How it identifies itself
Look for an Ecosia or EcosiaApp token alongside the usual Chrome token and AppleWebKit chain. We mark this partially verified because the exact token presence and form can vary across the desktop browser and the mobile apps.
Match on an Ecosia-family token where you see it rather than guessing. As with any browser, the string is client-supplied and editable, so use it for attribution, not authentication.
- Chromium-based browser from the Ecosia search company
- Chrome-like UA; may add an Ecosia or EcosiaApp token
- Available on desktop and mobile
How it appears in analytics and logs
A Chrome-like user agent with an Ecosia or EcosiaApp token indicates the Ecosia browser. It is a real human browser; without that token, Ecosia browser traffic can fold into generic Chrome.
Diagnostic use case
Recognise Ecosia browser sessions that would otherwise be counted as Chrome, and understand why its user agent resembles Chrome.
What WebmasterID can help detect
WebmasterID attributes Ecosia browser traffic to its own family server-side where its token appears, keeping it distinct from mainline Chrome in your browser mix.
Common mistakes
- Counting Ecosia browser sessions as plain Chrome.
- Assuming a single fixed Ecosia token across desktop and mobile.
- Treating the Ecosia token as something that cannot be spoofed.
Privacy and accuracy notes
An Ecosia token names a browser brand, not a person. WebmasterID treats it as a browser-family signal and never as an individual identifier.
Related pages
- 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.
- Brave browser user agent
Brave is a privacy-focused Chromium browser that, by design, does not advertise itself in the user-agent string. It mirrors Chrome's user agent so sites cannot single Brave users out and to avoid breaking UA-sniffing sites. This page explains why Brave is hard to detect from the UA and why that is intentional.
- Browser user agents: how to read them
A browser user-agent string packs several tokens into one line: a legacy Mozilla prefix, a rendering-engine signature, the platform, and the browser itself. This page explains each part so you can read a UA without over-reading it, because the contents are client-controlled and can be copied by any client.
- Privacy-first analytics
Attribute browser families like Ecosia without tracking individuals.
Sources and verification notes
- Ecosia browserOfficial page; Chromium-based browser. Exact UA token form not asserted across all platforms.
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.