Webflow Localization

Localizing CMS Option Fields

Overview
Known Localization Limitations & Bugs
001
Supported Languages
010
Tips & Techniques
Choosing the Right Locales
100
Localizing an Already-Localized Site
101
Localizing Dates
102
Localizing CMS Option Fields
103
Localizing Numbers & Currencies
104
Locale-Specific Styles & Code
105
Maintaining a Localized Site
106
Locale-Specific Pages & Sections
107
Localizing Form Success & Error Messages
107
Locale Switcher
The Locale List Element
401
Build a Dropdown Locale Switcher
402
Add Flags to the Locale Switcher
403
Add Localized Locale Names to the Locale Switcher
404
Make the Locale Switcher Responsive & Visible in your Nav
405
Advanced Localization
Splitting Locales by ccTLD
801
No items found.
Published
December 23, 2023
Updated
December 23, 2023
in lightbox

As of 23-Dec-2023 Webflow Localization doesn't localize CMS option fields.

I'd expect options localization to be solved eventually, and I'm not sure why it's not already supported. My best guess is that it's related to implementation issues in how options were built, and the extensive changes Webflow needs to make to easily support alt locales in option fields.

Ref Field Workaround

The simplest option is probably to replace your option fields with ref fields, as long as;

  • You have space for the added collections to represent those options lists
  • You have space for the additional ref fields needed. Maximum per collection is 5 ( cms plan ) or 10 ( business plan ).

I generally prefer ref fields to options anyway for the added field support, sort order control, etc.  However, currently options work ok for things like collection list filtering, so they can be a good lightweight choice.

## test

Videos
No items found.
Table of Contents
Comments
Did we just make your life better?
Passion drives our long hours and late nights supporting the Webflow community. Click the button to show your love.