Multi-language sites and CMS fields

Each page and CMS entry is translatable. When creating fields for a Collection, mark whether that field is translatable (some fields won't need translation, like references to other collections, price fields, etc). 

An option for Links should be added to choose a language (in addition to external links, pages within the site, etc).

  • Brent Cartier
  • Jan 18 2017
  • Reviewed
  • Jan 19, 2021

    Admin response

    Hi all - this is not a priority in the immediate term as there are a number of 3rd-party solutions (e.g. Weglot) that allow customers to create multi-language experiences on their sites, but it’s definitely something we plan to build the right way within Webflow in the future.

  • mBusiness GmbH commented
    20 Jul 08:59pm

    Really sad how ignorant Webflow deals with this top voted requirement.

  • Gregory Zagkos commented
    17 Jul 10:51am

    Weglot is way too expensive. Not helping at all. Here in Europe pretty much every second business needs more than 1 language. Especially here in Switzerland, we have 4 native languages.

  • Jeroen van der Elst commented
    16 Jul 12:43pm

    Weglot only provides subdomain support, no subdirectory support. Being able to use subdirectories is a must for SEO. When your current site uses subdirectories for example .com/en or .com/de and you swap to and the penalty for SEO is HUGE.

  • Simon Wachtler commented
    11 Jul 10:33am

    This is absolutly neccessary!!!

  • Daan Steegmans commented
    7 Jul 09:05am

    This really needs to get done. We have built a big corporate website and using Weglot does not work at all for us and I believe a lot of others developers agree on this..

    Get this done Webflow..

  • Urs Odermatt commented
    25 Jun 07:21am

    DO THIS WITH PRIORITY. it is a base funicionality.

  • Tomas Ferezou commented
    9 Jun 06:33am

    How can this not be a priority? Webflow says there is Weglot out there (there are actually numerous other options) but it is so expensive that it hurts our business case (and Webflow's). And even if you don't look at the price, it is just not maintanable for larger websites, where every comma changed in the original language changes the end translation. How can you even pretend this is a solution? It's preposterous and arrogant from Webflow.

  • Christoffer Furnes commented
    27 May 11:43am

    Have been using Weglot on several projects lately. It's just not good enough for enterprise solutions. The UX experience for the client is terrible and there is a lot of issues with SEO, handling language versions of files and links, URL translations and much more. Weglot is an impressive hack, but it's exactly that; a hack, NOT a viable solution.

  • Ana Labudovic commented
    25 May 12:13pm

    come on webflow! you will lose me over this one..

  • Simon Hausdorf commented
    18 May 06:51pm

    wow, this is from 2017, is ranked second in popular and webflow keeps recommanding 3rd party solutions?

  • Javier Rodriguez commented
    17 May 10:11am

    I don't mind paying something for automatic translation. However, I would like to have both the functionality and hosting of my pages in one place; Webflow. That is also the reason why I am not on WordPress.

    In my eyes it is a wrong decision not to prioritize this fundamental function of a CMS.

  • Giles Holland commented
    14 May 09:43pm

    You don't even need to do full multi-lang or translation support. Simply allowing multiple template pages for a CMS collection but get us 90% of the way there. Then multi-language content would be as easy as making multiple text fields for different languages in a CMS collection, and use one template page for one language and a second for the other. See comments in This at least should be built in, even if you're not going to do the full thing.

  • Primoz Rome commented
    13 May 02:22pm

    This is also major concern of holding us back to migrate our large corporate site to Webflow. Weglot is not a viable solution for us nor is duplicating content. I would really like to see this being added natively.

  • Joshua Roberts commented
    6 May 06:19am

    Webflow not supporting multi-language natively is causing HUGE headaches for us. We cannot use Weglot to accomplish what we need to do, and duplicating tons of CMS collections that don't carry over their settings makes our job a complete nightmare. This issue must get solved or Webflow cannot be considered a true solution for multi-lingual needs. I will continue using Webflow for all single language websites cause it's so great, but for muli-language that will be a different story in the future. I sure do hope the team at Webflow realizes the importance of this feature natively.

  • Anurag Gupta commented
    27 Apr 07:53am

    Can we have an option to directly override the weglot translations ?
    That would be a good quick fix for many of us..

  • Micha Köly commented
    20 Apr 10:41am

    Hi there, not considering this as a priority sends a very bad message to webflow users. I'm really happy with all the functions and the convenience that webflow delivers but with this behavior concerning an issue that is clearly an absolute must-have for many of your users, I find myself reconsidering the decision to further build on the webflow service. I'm willing to pay the webflow subscription and hosting prices for the services we get so far (as I said I'm happy with that) but the slow progress on the multi-language issue paired with the obvious advertisement for WEGLOT conveys the impression of a solely money-oriented alliance. I get it - that's business, but please consider that this could be a major decision driver for users in the future to further use webflow as their faith decreases.

  • Code Chrysalis commented
    13 Apr 05:01am

    Hey there. I would also like for Webflow team to reconsider this priority. With corona moving businesses online, a major appeal is to attract a larger more international market. It is a business need on your customer's side, shouldn't it be yours?

  • Benjamin Mühlbauer commented
    13 Apr 03:28am

    I remember when in 2017 I started using Webflow with the promise that multi-language support is coming.

    Now it is four years later and you decided that this is not a priority? Hugely disappointing!

    I cannot justify the additional costs of using a third-party solution to my clients!

  • Tiada Guru commented
    9 Apr 01:59am

    Really disappointing this decision has not been overturned.

    A huge chunk of faith lost. Is this platform worth spending money if after years, huge promises just vanish?

    This is Adobe-level support & recognition of Very Bad Developer Honesty.

  • אילנה סביר דה ריבס commented
    6 Apr 07:35pm

    The problem with 3rd party solutions is that they are very expensive. As an independant bloger with limited income that speaks 3 languages fluentll and actually a professional translator & editor, I see no reason whatsoever to pay for something that I can do much better.

  • Load older comments
  • +6122