DEVELOPER TOOL

Unit & Format Localizer

Automatically convert units, dates, and currency formatting across locales. Simple, accurate, and production-friendly.

input.txt
Price: $199.99
Distance: 12.5 miles
Date: 03/15/2026
Weight: 6.6 lb
                    
localized.txt
Price: EUR 184.20
Distance: 20.1 km
Date: 15/03/2026
Weight: 3.0 kg
                    
KEY FEATURES

Core Capabilities

Text-level conversion for units, dates and currency with locale presets and configurable decimals.

Units

Imperial ↔ Metric for speed, distance, weight, volume and temperature (mph, mi, lb, gal, °F ...)

Dates

Parse common date patterns and format for target locales (e.g., MDY → DMY)

Currency

Format to target locale currency, optional FX conversion with custom rate

Ready to Localize?

Open the dashboard and convert your text for your audience.

Open Dashboard

Localize Numbers, Units, Dates and Formats per Locale

Internationalizing the numbers in your app is easy to forget until a German user sees 1,234.56 where they expect 1.234,56, or a British user sees 5 miles where they expected 8 km. Every locale has its own conventions for number grouping, decimal separators, unit systems, date and time formats, currency, and measurement. The Internationalization API (Intl) in every modern browser and runtime implements all of this correctly - this tool is a visual front-end for it.

Pick a locale, and the tool renders numbers, dates, times, relative times, currency, and measurements in exactly that locale's conventions. Copy the formatted output, or use it as a reference when writing your own formatting logic. It is also a quick way to answer "what does this date look like in Japan?" without opening the spec.

Why Intl is the right foundation

Manually formatting numbers per locale is a bottomless pit - every country has quirks (thousand separators, non-Latin digits, mixed unit systems). The Intl API is spec-defined, ICU-backed, and correct by construction. Using it (which is what this tool wraps) means you get every locale right, including edge cases like Arabic-Indic digits, without maintaining a lookup table yourself.

Common Questions

What formats does this handle?
Numbers (grouping, decimals, percent, compact), dates and times, relative time, currency, and measurement - all per-locale, following the standard conventions of the chosen locale.
Why does 1,234.56 become 1.234,56 in some locales?
Number grouping and decimal separators are locale conventions. The US uses a comma for thousands and a period for decimals; Germany inverts them. The tool applies the exact convention of the selected locale.
Does it handle units like miles vs kilometers?
Yes. Measurements are rendered in the locale's conventional unit system, so a distance shows as miles in en-US and kilometers in de-DE. You can also specify a unit explicitly.
Can I use the output as a reference for my own code?
Yes. The output shows exactly what the standard Intl API produces for that locale, which is the same output you would get in your own application - a reliable reference for your formatting logic.
Does it support non-Latin digits?
Yes. Locales that use non-Latin numerals (e.g. Arabic-Indic digits) render them correctly, because the underlying API is spec-defined and ICU-backed.