Rendering Locale Dataset Upgrade: JRE to CLDR
Wednesday, July 15, 2026
What it is
HubSpot is upgrading the locale data source used to render content, including how dates, times, numbers, and currencies are formatted, from Java's built-in dataset to CLDR (Common Locale Data Repository), the current industry standard for localization. All rendering services are migrated automatically, with no action required.
Why it matters
The upgrade unlocks modern Java features and improves internationalization accuracy. Most rendered content will see no change, and some may see slightly improved formatting. A small amount of content could shift if your implementation relies on the exact string output of locale-aware formatting, for example certain HubL filters.
The Take
Zach Hussion
For most portals nothing changes. The people who should spot-check are the ones doing real development work.
This is the one Zach understood out of the gate. HubSpot is swapping the behind-the-scenes locale dataset it uses to format dates, times, numbers, and currencies over to CLDR, the industry standard. The migration is automatic, and for the vast majority of portals nothing changes. Most people will never know it happened.
Where it matters is the development layer. If you have integrations or data transformations that depend on an exact formatted string, or HubL filters doing locale-aware formatting, this is the one to spot-check so a small formatting shift does not surprise you downstream. For everyone else, it is a free accuracy upgrade you do not have to touch.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
Produced by Value-First Media