Editor needs to be integrated with localization features

This is such a massive pain point for using Webflow's version of localization. The people using the designer don't speak every language that needs to be localized, and we should not be the gatekeepers of updating translated text.

Editors need to be able to update and correct translated text, so that end customers and hired language experts can perform work without having to go through middlemen.

  • Kevin Larsen
  • Nov 25 2023
  • Tobias Drevenstedt commented
    26 Apr 14:21

    This is a must.... or at least the Editor/Designer seat needs to be for free... unsellable like it is in comparison the weglot.

  • Tansen BEL commented
    03 Apr 10:00

    It's a huge scam for the price that we have to pay! Now we are completely stuck with the multiligual website we have just delivered, the client was supposed to correct directly the second language, it's going to ask us days of work just because of that mandatory feature missing!

  • Sandro Hagen commented
    19 Mar 17:01

    this makes localization unusable at all, i feel like scammed!
    need to switch to weglot and other localization services again... very disappointing

  • Tobias Gasser commented
    13 Mar 00:31

    This also makes localization significantly more expensive, as each editor who should have access to localization has to now be "promoted" to a full workspace member to have access to the edit mode in Designer.

    Even more: with e.g. a Freelancer plan that would limit the "localization-capable" editors to 3 - even if the hosting plan would allow for more editors (e.g. 10 on the Business Hosting plan).

    In consequence: hosting a bigger site with 2 locales for 4 editors would then cost $39 for hosting (Business) plus 4 x $35 for 4 workspace seats plus one locale with at least $9. That totals to $188 - compared to $48 ($39 plus $9), if only site hosting had to be considered for a site sitting in an agencies' workspace.

  • Shay from Dreamside commented
    27 Feb 15:38

    SO frustrating that editing translations isn't available to content editors. Does Webflow really think that web designers are going to be entering the translations for all the locales for all their clients?

  • Tijs Gn commented
    26 Feb 21:54

    this is a huge issue, that could easily be fixed... changing the locale in the URL already allows you to update blog posts in a certain locale, so it should be easy to make it work for the page content as well

  • Stichting NDSM-werf commented
    23 Feb 12:19

    This is a crucial feature! Update fast

  • Christer Persson commented
    16 Feb 09:59

    Uhm, yes we were just about to start migrating all translations and just realized that the content editors we have can't do it..

  • Guillermo D'onofrio commented
    13 Feb 10:50

    I have paid a subscription for localization right now but I have just realized that my customer can't edit the localization contents 🤦🏻😡. An absolute nonsense.

  • Roger Attlee commented
    02 Feb 17:26

    Wow, it looks like we've hit a snag with Webflow! My client is unable to edit the locales, which is a crucial feature we were counting on. The client editor features were a big reason for choosing Webflow, so it's surprising this isn't available for locales. We need a quick resolution, please.

  • Roger Attlee commented
    02 Feb 17:25

    Oh my God! Wow,
    it looks like we've hit a snag with Webflow! My client is unable to edit the locales, which is a crucial feature we were counting on. The client editor features were a big reason for choosing Webflow, so it's surprising this isn't available for locales. We need a quick resolution, please.

  • LTTR CORP commented
    01 Feb 16:38

    Designers are not translators. Why is there no localisation for editors?

  • I*AM Webmaster commented
    23 Jan 11:32

    We tested a possible solution which comes at zero additional cost:

    • create new "client" user + client workspace

    • invite the webmaster as a guest to the client workspace (admin permissions)

    • in the webmaster workspace: transfer the site to the client workspace

    • in the client workspace: add a hosting plan to the website

    "Real" Editor Access for the client


    hope this helps :)

  • Christoph Zillgens commented
    19 Jan 15:13

    We now have "the Editor" and the "Editing mode" within the Designer. This is already confusing for me as Web Designer, and for sure for my clients. The Editor is a big selling point to clients. The Editing mode is not. So bring localization to the Editor, please. THX!

  • Nekativ commented
    18 Jan 16:14

    This should have been the case from the beginning! Editors manage the site; they should be able to do all the translations by themselves. Come on webflow, so far you've been a game changer, keep the ball rolling.

  • I*AM Webmaster commented
    16 Jan 08:59

    After a bit of research, the only way to invite clients to edit a multilang site is via the webflow editor. But this comes with a few issues:

    • client needs to have a payed seat in our webflow workspace

    • client can see all our other websites and (with lowest permission rights) comment them - this is not acceptable. I wonder why Webflow chose to handle permissions like that - maybe it is to move customers in the following direction:

    Right now imo the only possible way to grant multilang-client access to the website via the editor is to

    • create a new webflow workspace for the client (new user)

    • invite our agency account to the workspace

    • upgrade the workspace plan to two seats (wtf)

    • set our agency account as workspace "admin"

    • set our acency account as website "admin"

    • set the clients account to "editor"


    In case you guys found a better way to handle the issue, please reach out to me. I know, this solution is hacky at best and comes with the cost of an additional workspace seat, which is imo not acceptable.

  • I*AM Webmaster commented
    15 Jan 15:06

    +1 today our first client asked for localisation access after the editor onboarding. It's a shame, that this missing feature is swept under the rug. We really need editor localisation access. Right now I really have no answer to my clients request 🫠

  • Aleksi commented
    09 Jan 05:52

    +1 from me. I'm charging my client for a professional localisation service so that they can easily update the content in all locales without my help. I was genuinely surprised to find out this feature is not supported. Please do add this in your roadmap and in the least update your customers about the progress and intentions. Thank you.

  • Épigraphe commented
    December 20, 2023 15:02

    Clients are usually the ones to localize sites, how is this even missing?

  • Samuel Uebersax commented
    December 14, 2023 16:28

    This is a must. Seriously. Please provide access to editors to all locals.

  • Load older comments