UnixEpoch

Locale Convertirer

Normalize locale identifiers online. Convertir BCP 47 tags, POSIX locale strings, ICU-style values, and Accept-Language headers into clean locale formats with live browser Intl previews.

Paste a locale tag, POSIX locale string, or Accept-Language header.

Common Locale Conversion Exemples

Input en_US.UTF-8 Output en-US

Common POSIX locale from shell environments and Linux servers.

Input zh_Hans_CN Output zh-Hans-CN

ICU-style locale with explicit script and region.

Input sr_RS@latin Output sr-Latn-RS

POSIX modifier converted into a script subtag.

Input Accept-Language: fr-CA,fr;q=0.9 Output fr-CA

Browser header reduced to the primary requested locale.

Comment utiliser cet outil

  1. Enter a locale tag, POSIX locale string, or Accept-Language header from your app, browser, or server logs.
  2. Check the canonical BCP 47 locale, POSIX form, HTML lang value, and Accept-Language fallback chain.
  3. Use the preview cards to confirm how Intl resolves dates, numbers, relative time, and sorting for that locale.

Ce que cette page explique

  • How do I convert en_US.UTF-8 into a browser locale tag?
  • What locale should I put in an HTML lang attribute or Intl API call?
  • How does an Accept-Language header map to a primary requested locale?
  • Which locale does the browser actually resolve for numbers, dates, and sorting?

Questions fréquentes

What does this locale converter normalize?

It normalizes common locale inputs such as en_US.UTF-8, zh_Hans_CN, sr_RS@latin, and Accept-Language headers into cleaner locale formats for browser and application use.

What is the difference between BCP 47 and POSIX locale formats?

BCP 47 uses dash-separated tags like en-US for web and Intl APIs, while POSIX locale strings often use underscores and charsets such as en_US.UTF-8 for servers and shell environments.

Can I parse an Accept-Language header here?

Yes. Paste a full header such as Accept-Language: fr-CA,fr;q=0.9 and the tool extracts the primary locale and shows a fallback chain.

Why do resolved locales differ from the requested locale?

Browser Intl APIs can fall back to a supported parent locale or canonical variant. The resolved locale cards show what NumberFormat, DateTimeFormat, ListFormat, RelativeTimeFormat, and Collator actually use.

Is this locale converter online only or does it call a server API?

The parsing and preview logic run in the browser, so you can inspect locale behavior instantly without sending the locale input to a conversion API.

Outils associés