Why does my Chrome User-Agent contain the word 'Safari'?

Google Chrome's Blink engine originated as a fork of Apple's WebKit, which itself was based on KHTML. Chrome retained the 'Safari' token so that web servers expecting Safari's WebKit rendering would not block Chrome.

What is User-Agent Client Hints (UA-CH)?

User-Agent Client Hints is a modern privacy-preserving standard in Chromium browsers where detailed information (like exact OS build or architecture) is only provided upon explicit HTTP header request rather than in the raw UA string.

Developer Utilities

User-Agent String Parser & Device Inspector

The problem: Deciphering historical tokens and browser signatures in raw HTTP User-Agent strings from server logs is tedious and confusing.

ASG Privacy VerifiedVerified

100% In-Browser Execution. Zero server uploads. Your data never leaves this tab — disconnect your internet and the tool keeps working.

ASG Privacy VerifiedVerified

100% In-Browser Execution. Zero server uploads. Your data never leaves this tab — disconnect your internet and the tool keeps working.

Browser

Google Chrome

Version: 126.0

Operating System

Windows

Release: 10 / 11

Device Category

Desktop

User Hardware

Rendering Engine

Blink (Chromium)

Layout compiler core

User-Agent String to Inspect

Test Presets:

User-Agent String Parser & Device Inspector: the complete guide

A User-Agent String Parser and Client Device Inspector decodes browser HTTP User-Agent strings to identify browser families, exact version numbers, operating systems, rendering engines, and device categories. Web developers and QA engineers debugging cross-browser rendering inconsistencies, responsive layout issues, or traffic analytics logs rely on UA parsing to diagnose device capabilities. This tool runs 100% in your browser with 1-click current device detection.

Deconstructing the Complex Legacy of User-Agent Headers

HTTP User-Agent strings carry historical legacy tokens dating back to the 1990s browser wars. For instance, modern Chrome strings still begin with 'Mozilla/5.0' and include 'AppleWebKit' and 'Safari' tokens for backward compatibility with legacy web server sniffing scripts. Our parser extracts the true browser engine and release version from nested token structures.

Detecting Search Engine Spiders and AI Crawlers

In addition to consumer desktop and mobile browsers, the parser identifies automated web crawlers and spiders, including Googlebot, Bingbot, Yandex, Baidu, Twitterbot, Discordbot, and AI scrapers like GPTBot. This enables backend engineers to verify whether an incoming request originates from an authentic search indexing spider.

Step by step: how to use User-Agent Parser

1
Click 'Detect My Current Browser UA' to inspect your active device and browser version.
2
Or paste any raw User-Agent string from web server access logs or bug reports.
3
Inspect the identified Browser Name and exact software release version.
4
Check the detected Operating System (Windows, macOS, iOS, Android, Linux) and kernel.
5
Review the Rendering Engine (Blink, WebKit, Gecko) and hardware device classification.

Security & privacy

Pure client-side regular expression parsing. No IP addresses, device identifiers, or user agent headers are transmitted to remote servers or third-party analytics.