How to use User-Agent and Client Hints Explainer
- Paste the user-agent string you want to inspect.
- Optionally add the supplied client-hint header block.
- Review recognized tokens and any conflicting or unknown fields.
Example: User-Agent and Client Hints Explainer
A desktop Chrome user-agent and optional pasted Sec-CH-UA headers.
Options
- User-Agent
- Paste the recorded string rather than treating the local browser as the source. Recognizable tokens are heuristic observations and can be altered.
- Client hints
- Enter header-name: value lines actually observed. Missing hints stay missing; the page does not request hints or probe a device.
Supported inputs and limits
Where your input is processed
This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.
Disagreement needs investigation
Reduced user-agent strings, compatibility tokens and supplied hints can describe different levels of detail. A conflict does not by itself establish fraud or a specific operating system. Keep the original request context when diagnosing a compatibility issue and test the actual feature you need instead of using this output as verified identity.
Questions about User-Agent and Client Hints Explainer
Is a user-agent a verified browser identity?
No. It is supplied text and can be forged or reduced.
Are hints requested from my device?
No. The page inspects the fields you enter.
What does an unknown token mean?
It has not been mapped by this bounded heuristic; retain the original value for review.