I know this might be a known issue, but I wanted to bring it up anyway—maybe I’ve overlooked something, or there’s a workaround I haven’t thought of yet.
The Problem
I’m working on a client project that includes a blog, and I need to display the publish date of CMS items in German.
Custom date formats: Webflow allows us to choose different date formats, but there’s no option to define a fully custom format like DD. MMMM YYYY (10. Februar 2025). A workaround is to split the date into DD, MMMM, and YYYY and use separate text elements—but that’s not only annoying, it also feels unnecessary.
Language limitations: The bigger issue is that month names always appear in English, even though the site’s language is set to German. If Webflow supports localization, dates should respect that as well.
Workarounds?
I know it’s possible to use JavaScript to replace the month names dynamically, but that’s not ideal (hello, FOUC ). Shouldn’t this be handled on the server-side instead?
My Question
So, before I go all in with a custom script—is there really no native Webflow solution for this?
Would love to hear if anyone has tackled this differently!
It’s a bit frustrating that such a core localization feature is missing. While JavaScript can solve it, it feels more like a workaround rather than a proper solution—especially considering Webflow’s focus on no-code solutions.
Localization goes beyond just translating content; it should also cover elements like dates, numbers, and currency formatting natively. Hopefully, this is something that will be addressed in the future.
Yep, that would be nice. It does raise a ton of complications though, for example some currencies might need two decimals, some none, some 4 decimals. Some need text suffixes, some don’t.
Dates are potentially even more complex as there are a lot of formatting options, and some may not relate well to specific locale conventions.
Webflow also does not have a currency type per-se, outside of ECommerce which itself is not yet compatible with localization.
A lot of considerations, so deciding exactly what you need and setting it yourself is much cleaner.
Incidentally, I did some early prototyping of localized dates, with the ability to auto-detect the locale from the page’s <html lang> setting. I think it may be implemented in SA5 despite the warning note.
You’re welcome to try it here. It uses dayjs under the hood, which I found the best for this purpose.
). Shouldn’t this be handled on the server-side instead?