Locale
Locale is the per-user Salesforce setting that controls how the platform formats numbers, dates, currencies, names, and time displays for that user.
Definition
Locale is the per-user Salesforce setting that controls how the platform formats numbers, dates, currencies, names, and time displays for that user. The Locale field on the User record is independent of the Language field: a user can display the UI in English while using a French locale for date formats (DD/MM/YYYY instead of MM/DD/YYYY) and currency symbols. Locale also affects how the platform parses user input on edit forms, accepting locally-appropriate formats and converting to the storage representation.
The Salesforce platform supports a long list of locales corresponding to ISO standards (en_US, fr_FR, ja_JP, de_DE, en_GB, etc.). Each locale defines date format, time format, decimal separator, thousands separator, currency symbol position, calendar conventions, and other formatting details. The locale list is managed at the platform level; administrators do not add custom locales. Most orgs default each user's Locale to match their geographic location, but global support staff sometimes use a different locale to match the customer they are serving.
How Locale shapes Salesforce displays
What Locale affects
Locale shapes: date format (MM/DD/YYYY vs DD/MM/YYYY vs YYYY-MM-DD), time format (12-hour AM/PM vs 24-hour), decimal separator (period vs comma), thousands separator (comma vs space vs period), currency symbol and position, name display order (First Last vs Last First), and calendar conventions (week start day). Each of these is platform-controlled per locale; admins cannot override individual aspects.
Locale versus Language
Locale controls formatting; Language controls UI translation. The two are independent: a user can have Language=English and Locale=French to see the UI in English but with French date and currency formats. Most orgs default both to the same locale, but multi-language global orgs sometimes diverge. Set both deliberately rather than assuming they match.
Org default locale
The org has a default Locale (Setup > Company Information). New users created without explicit Locale inherit the org default. Setting the org default appropriately for the primary user population reduces per-user setup. For multi-region orgs, the org default is the locale of the largest user population; smaller regions are set per-user.
API and integration handling
The API does not return formatted strings; it returns raw values (numbers, ISO date strings). Locale formatting is applied only when the platform renders for users. Integration code working with Salesforce data sees consistent ISO formats regardless of the user's locale, which is the right behavior for data integrity. Custom UI code that displays data must apply locale formatting; the platform standard pages handle it automatically.
Effect on validation rules
Validation rules using TEXT() conversion on dates or numbers may produce unexpected results because the conversion uses the running user's locale. A rule comparing TEXT(SomeDate) to a hard-coded string fails for users in non-US locales because the date renders differently. Avoid locale-dependent string conversions in validation rules; use date and number functions instead.
Time zone interaction
Locale is distinct from Time Zone. Time Zone (separate field on User) controls which time zone Date/Time fields display in. Locale controls how the date and time are formatted within that time zone. Both affect what the user sees, but they configure separately. Multi-region orgs need both set correctly; mismatches produce confusing displays.
Changing locale mid-session
Locale changes take effect on the user's next page load or login. Existing open tabs may continue to show the old locale until refreshed. For administrators bulk-changing locale through Data Loader, users see the new locale on their next session start; coordinate timing with user expectations.
Configure user Locale
Configuring Locale is a per-user and per-org task. The steps below cover org defaults, per-user setup, and the testing that catches Locale-related bugs.
- Set the org default Locale
Setup > Company Information > Edit. Set Default Locale to the locale of your largest user population.
- Audit user Locale assignments
Query User for Locale distribution. Confirm regional users have their region locale set; global support has the locale matching their role.
- Set Locale per user
For users needing non-default Locale, edit the User record and set Locale explicitly. For bulk, use Data Loader.
- Coordinate Time Zone
Ensure Time Zone is set to match the user's actual location. Mismatches with Locale produce confusing displays.
- Test from a sample user
Use Login As. Verify date and number formats match the user's expected locale. Check reports and dashboards.
- Audit validation rules
Search for validation rules using TEXT() on dates or numbers. These are locale-dependent and may produce unexpected behavior for non-default-locale users.
- Train developers on locale awareness
Custom Lightning Components and Apex must use platform locale utilities when formatting for display. Hard-coded formats break for non-default locales.
Inherited by new users without explicit assignment.
Override on each User record.
en_US, fr_FR, ja_JP, de_DE, etc. Platform-managed list.
Derived from Locale. Cannot be overridden separately.
Decimal and thousands separators derived from Locale.
- Locale and Language are independent. Confusion between them is the most common source of "the platform is showing wrong format" tickets.
- TEXT() conversions in validation rules are locale-dependent. Avoid them; use date and number functions instead.
- Custom Lightning Components must use platform locale utilities. Hard-coded formats break for non-default locales.
- Locale changes take effect on next page load. Existing tabs continue with old locale until refreshed.
- API responses use ISO formats regardless of locale. Integration code working with Salesforce data should not depend on user locale.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Locale determine?
Q2. What format do locale codes follow?
Q3. How does Locale differ from Language?
Discussion
Loading discussion…