
You've probably run into this frustrating workaround before: in the Webflow CMS, a multi-reference field lets you link several items together. Authors on an article, related products on a product page, tags attached to a project. The problem? Until now, there was no simple way to change the order of these elements once they were selected.
The only workaround was to delete everything and re-select each item one by one, in the right order. A tedious operation, prone to mistakes, and particularly painful once the list grew past three or four items.
As of August 13, 2026, Webflow is rolling out drag-to-reorder for these multi-reference fields. You open a CMS item, hover over a selected entry, and drag it where you want it. That's it.
The mechanics are simple and consistent with the rest of the Webflow interface:
Good news for accessibility: the feature can also be fully controlled with the keyboard. The left and right arrow keys let you navigate to the entry you want, the spacebar "picks it up," the arrow keys move it, and pressing spacebar again "drops" it into its new place.
On paper, this sounds like a minor tweak. In practice, the order of elements in a multi-reference field often has a direct impact on how the front-end of a site renders: the display order of authors, the hierarchy of related products, the priority of featured tags. It's not just about tidiness in the back office, it's about the final user experience.
| Before | Since the update |
|---|---|
| Delete all selected entries | Drag the entry directly to reorder it |
| Re-select each item in the right order | Order changed in a few seconds |
| High risk of error on long lists | Reliable, predictable operation |
| No keyboard option | 100% keyboard navigation and reordering |
Let's be honest: this isn't the feature that's going to headline a Webflow conference. But it's exactly the kind of improvement that matters to us, as an agency, on a day-to-day basis.
On projects where the Webflow CMS structures rich content -- articles with multiple authors, product catalogs with cross-referenced items, team pages with multiple roles -- this kind of micro-friction always ended up coming back in client feedback. "How do I change the order of the authors on this already-published article?" We'd explain the workaround, and see that slightly disheartened look. It was never a dealbreaker, but it gave the impression of an unfinished tool on what should have been a basic feature.
What Mazette.co particularly appreciates is that Webflow took care of the issue as a whole: both the mouse version AND the keyboard version, with genuinely accessible behavior (arrow-key navigation, spacebar selection). It's a consistent signal in the direction the platform has been heading over recent updates: closing functional gaps that, taken individually, seem minor, but that add up to real friction in advanced CMS usage.
For our clients who manage their own content day-to-day once the site is delivered, this kind of improvement has a direct impact on their independence. Fewer support tickets, fewer "I don't know how to do this" moments, more comfort in everyday content management. And that's exactly what we aim to pass on through our method: not just a polished site at handoff, but a tool the client can truly own once the project is complete, without needing us.
Our only gripe: this feature should clearly have existed since multi-reference fields themselves were launched. But we'll take a late, well-executed fix over a rushed feature shipped on time, any day.
If you run a blog with multiple contributors, a catalog with related products, or any CMS structure built on multiple relationships between items, this update immediately simplifies your editorial workflow. No action is needed on your part: the feature is automatically available on all existing and future Webflow sites.
If you're considering a migration to Webflow from another CMS and are concerned about managing complex relational content, this is one more good argument in favor of making the switch. The Webflow CMS keeps maturing on use cases that, historically, required workarounds.
Code