Am I On Mobile Or Desktop
You are on
Detecting…
Uses user agent, Client Hints, touch capability, and screen size. Resize or rotate to re-check.
How to use
- Open the page — Mobile, Tablet, or Desktop appears at the top automatically.
- Resize the window or rotate a phone to watch the classification update when signals change.
- Read the Details card to see touch points, screen size, and Client Hints used for the answer.
FAQ
Am I on mobile or desktop?
The headline answers with Mobile, Tablet, or Desktop based on your user agent device type, User-Agent Client Hints mobile flag when available, touch capability, and screen size heuristics.
Why does desktop DevTools show Mobile?
Chrome and other browsers can spoof a mobile user agent in device emulation mode. This page reports what the browser is currently pretending to be — turn off emulation to see your real desktop profile.
What is the difference between mobile and tablet?
Phones report mobile. Larger touch devices often report tablet. This page also uses screen width heuristics when the user agent is ambiguous.
Can a desktop have touch?
Yes. Touchscreen laptops may report touch points and a coarse pointer while still being desktop by user agent. The Details card shows how signals combined.
Why did it change when I resized the window?
Narrow windows on desktop can trigger mobile-like layout heuristics in some cases. Primary classification still follows user agent; resize listeners refresh touch and screen context.
Is any data sent to a server?
No. Classification uses browser APIs locally.
Introduction
Am I On Mobile Or Desktop gives a plain answer — Mobile, Tablet, or Desktop — as soon as you open the page, with the signals behind that decision listed below so you can understand edge cases like touch laptops or DevTools emulation.
Websites change layout, ads, and features based on whether they think you are on a phone. This page shows the same class of signals they use, which helps when a site stuck in mobile view on a large monitor or vice versa.
How classification works
| Signal | Role |
|---|---|
| User agent device type | Primary mobile / tablet / desktop flag from parser |
Client Hints mobile |
Chromium boolean when exposed |
| Touch points | navigator.maxTouchPoints — >0 on most phones and tablets |
| Coarse pointer | CSS media (pointer: coarse) — typical of touch |
| Screen size | Helps separate phone-sized vs tablet-sized touch screens |
The confidence line explains which rule applied.
Common use cases
- Responsive design QA — confirm which mode a site should enter at your current window size.
- Debugging redirects — see if the server might treat you as mobile when you expect desktop.
- DevTools sanity check — verify whether device emulation is still enabled.
- Teaching — demonstrate why "mobile" is inferred from several signals, not just screen width.
Best practices
- Turn off device emulation in devtools when testing your real desktop classification.
- Compare with what is my viewport size — layout breakpoints use viewport, not only mobile/desktop labels.
- For vendor and model, see what device am I using.
- For the full environment snapshot, open device info.