Midori and Falkon user agents
Midori and Falkon are lightweight, open-source desktop browsers popular in minimal Linux environments. Their user agents follow the engine each is built on at a given time, so they can look Chromium-like or WebKit-like rather than carrying a unique, headline brand token. That makes them low-volume but legitimate human browser traffic.
What this means
Midori and Falkon are open-source browsers favoured for being lightweight, often shipped in minimal or older desktop Linux setups. Both have used web engines that change over their history, so the user agent they present mirrors the engine of the build rather than a single fixed brand identity.
That is why these browsers can appear Chromium-like or WebKit-like in logs. They are genuine, if uncommon, human browsers, not scripts or scrapers.
How they appear
Depending on the version and platform, Midori or Falkon may include a recognisable product token, or may largely resemble the underlying engine's user agent. We do not assert a guaranteed, version-stable token for either, because their engine basis has shifted over time.
Treat any Midori or Falkon token you do see as a niche-browser signal. As always, the string is client-supplied and editable, so use it to attribute, not to authenticate.
- Lightweight open-source desktop browsers, common on Linux
- User agent reflects the build's engine (Chromium- or WebKit-like)
- Low volume; legitimate human traffic, not automation
How it appears in analytics and logs
A user agent from Midori or Falkon reflects the rendering engine the build uses, so it may resemble a Chromium or WebKit client. It is a real human desktop browser, typically low in volume.
Diagnostic use case
Recognise traffic from lightweight browsers like Midori and Falkon, and understand why their user agents reflect an underlying engine rather than a prominent unique brand token.
What WebmasterID can help detect
WebmasterID classifies Midori and Falkon traffic as human browser activity where their tokens are present, rather than mislabelling low-volume niche browsers as automation.
Common mistakes
- Treating low-volume niche browsers as bots by default.
- Assuming a fixed, version-stable token for Midori or Falkon.
- Folding their engine-like UAs into the wrong mainstream browser bucket.
Privacy and accuracy notes
These tokens describe niche browsers, not people. Any engine resemblance is a technical detail, and WebmasterID treats the UA as a coarse browser-family signal only.
Related pages
- Epiphany / GNOME Web user agent
GNOME Web, also known as Epiphany, is the default browser of the GNOME desktop, built on WebKitGTK. Its user-agent string carries WebKit tokens together with an Epiphany product token. Because it shares the WebKit engine with Safari, naive detection can confuse the two; the Epiphany token disambiguates genuine GNOME Web traffic.
- Konqueror and KHTML user agent
Konqueror is the KDE desktop's web browser, historically powered by the KHTML engine — the codebase Apple forked to create WebKit. Its user-agent string carries Konqueror and KHTML tokens. Understanding it explains why so many modern user agents still include a KHTML-derived token, and identifies genuine Konqueror traffic.
- 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 niche browser families without identifying individuals.
Sources and verification notes
- Falkon — KDE project pageOfficial Falkon site; lightweight browser whose engine basis has changed over time. Midori is a separate lightweight open-source browser.
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.