Free2Box
Analizador de User AgentTI y DesarrolloInstant browser workflowFocused single-task utilityNo setup required

Analizador de User Agent

Analizar cadenas de User Agent para identificar navegador, SO, dispositivo y motor

Cadena de User AgentResultados del análisisDispositivoNavegador--Sistema operativo--
Cadena de User Agent
Pegue una cadena de User Agent o use la de su navegador actual...
Paste a raw user agent string to extract browser, engine, operating system, device, and CPU metadata.
Resultados del análisis
Analizar cadenas de User Agent para identificar navegador, SO, dispositivo y motor
Paste a user agent string or load your current browser to parse the environment details.

Continuar con

Mant?n el flujo de trabajo en movimiento con la siguiente acci?n relacionada.

NavegadorA?n no hay resultadoSistema operativoA?n no hay resultadoDispositivoA?n no hay resultadoArquitectura CPUA?n no hay resultado
Privacy & Trust

Resultados del análisis

Break raw user agent strings into browser, engine, OS, device, and CPU sections instantly.

Usar mi navegador

Use your current browser string to confirm how the client environment is being identified.

Resultado

Parsing stays in the browser, so logs and pasted headers do not need to leave the page.

Resultados del análisis

Enter a user agent string to generate a parsed snapshot.

Analizar cadenas de User Agent para identificar navegador, SO, dispositivo y motor

Cómo Usar

1

Pega o Escribe

Ingresa tu texto, código o datos en el área de entrada.

2

Elige las Opciones

Selecciona la transformación o formato que deseas aplicar.

3

Copia el Resultado

Copia la salida a tu portapapeles con un solo clic.

Por Qué Usar Esta Herramienta

100% Gratis

Sin costos ocultos, sin niveles premium — todas las funciones son gratuitas.

Sin Instalación

Se ejecuta completamente en tu navegador. No necesitas descargar ni instalar nada.

Privado y Seguro

Tus datos nunca salen de tu dispositivo. Nada se sube a ningún servidor.

Funciona en Móvil

Totalmente responsivo — úsalo en tu teléfono, tableta o escritorio.

User Agent Strings: Browser and Device Identification

Key Takeaways

  • User agent strings identify the browser, operating system, and device type — but their format is notoriously inconsistent and often misleading.
  • User agent parsing is essential for analytics, content negotiation, and debugging browser-specific issues.
  • All parsing happens in your browser — your user agent data is never sent to any external server.

Every HTTP request includes a User-Agent header that identifies the client software. What started as a simple browser identifier has evolved into a complex string carrying browser, engine, OS, and device information — with decades of legacy compatibility quirks. Parsing user agents is essential for web analytics, responsive design debugging, and understanding your audience's technology profile.

Chrome's User-Agent string contains 'Mozilla/5.0' and 'Safari' — a legacy of browser compatibility hacks dating back to the 1990s.

Historical Quirk

Key Concepts

1

User Agent String Components

A typical UA string contains: Mozilla compatibility token, platform/OS info (Windows NT 10.0, Macintosh, Linux), rendering engine (AppleWebKit, Gecko), and browser name/version (Chrome/120, Firefox/121).

2

User-Agent Client Hints

The new Client Hints API (Sec-CH-UA headers) provides structured, opt-in device information instead of the bloated UA string. It offers browser, platform, and architecture data in clean, parseable format.

3

Bot and Crawler Detection

Search engine crawlers (Googlebot, Bingbot) and other bots identify themselves via user agent strings. Detecting these helps serve appropriate content and manage server resources.

4

UA Freezing and Reduction

Chrome is gradually freezing and reducing user agent string information for privacy. Many fields now contain fixed values. Developers should migrate to Client Hints for detailed device information.

Pro Tips

Never rely on user agent strings for security decisions — they can be trivially spoofed by any client.

Use feature detection (Modernizr, CSS @supports) instead of user agent sniffing for browser capability checks.

When analyzing user agents for analytics, use a maintained parsing library rather than custom regex — the format is too inconsistent for manual parsing.

Test your site with various user agents to ensure you are not accidentally blocking legitimate traffic from non-standard clients.

All user agent parsing is performed entirely in your browser. Your user agent string and browsing information are never transmitted to any external server.

Preguntas Frecuentes