Browser engines
Engines
Layout engines behind the browsers. Blink, WebKit, Gecko, and the rest.
- WebKitApple’s layout engine — the heart of Safari and every iOS/iPadOS in-app browser. Chromium forks still advertise AppleWebKit in the UA for compatibility, but real WebKit is what you get on Apple’s stack.35M hits
- GeckoMozilla’s layout engine behind Firefox and Firefox-derived browsers. Identifies itself with a Gecko/… rv:… token (and usually Firefox/…).11M hits
- TridentMicrosoft’s classic Internet Explorer engine (IE 4–11). Still shows up in enterprise and legacy Windows traffic as Trident/… like Gecko.16M hits
- KHTML KDE’s original HTML engine — the ancestor of WebKit. Mostly historical outside niche Konqueror builds.8.9K hits
- PrestoOpera’s pre-Chromium engine. Retired when Opera moved to Blink; surviving Presto strings are historical.1.0M hits
- EdgeHTMLMicrosoft’s short-lived Edge engine — a cleaned-up Trident fork used by legacy Edge before the Chromium switch. UAs use Edge/… (not the modern Edg/ token).6.0M hits
- GoannaA Gecko fork by Moonchild Productions, used in Pale Moon and related browsers.3 hits
- BlinkGoogle’s Chromium layout engine (a 2013 WebKit fork). Powers Chrome, Edge, Opera, Brave, Vivaldi, Samsung Internet, and most Android WebViews. In User-Agents it still often shows up as AppleWebKit/537.36.206M hits
- NetSurfLightweight open-source engine used by the NetSurf browser (RISC OS, Linux, and friends).300 hits
- ServoExperimental parallel layout engine started at Mozilla; research / embedding more than everyday browsing.78 hits
- TasmanMicrosoft’s Mac IE 5 engine — historical only.
11 engines with real write-ups from our archive. Useragent API