How do I sort a Collection list in Webflow?

Add a sort rule on a dynamic list

A new Collection list does not know that a blog should start with the latest post. You tell it with Sort order. The control is on dynamic lists only. If you hand-picked items in a curated list, change the type to dynamic before you look for the setting. Curated order is the order you dragged, and it does not offer sort, filters, pagination, or a display limit.

Select the list on the canvas. Open Element settings, then Collection list settings, then Sort order. Click the plus icon. Choose the field in the first dropdown and the direction in the second, then click Save. Remove a rule with the trash icon beside it.

You can connect sort settings to component properties when one list design should sort differently in different places. For a single news index, one saved rule is enough.

Match the direction to the field

Each field type has its own directions.

• Random order reshuffles the list on every publish, not on every page view.
• Number fields use smallest to largest, or largest to smallest.
• Date fields use oldest to newest, or newest to oldest.
• Switch fields use Is ON first, or Is OFF first.
• Plain text, and also switch, date/time, and number fields, can use alphabetical (A to Z) or reverse alphabetical.

Alphabetical order is more specific than a dictionary. Webflow sorts by the first digit of a leading number, then uppercase letters, then lowercase letters, then letters with accents. The rest of the word is compared the same way, not only the first character.

Their documented example is the clearest check. Lowercase 'apple', 'figma', and 'webflow' sort as apple, figma, webflow. Capitalize the W and 'Webflow' moves ahead of 'apple', because uppercase comes first. A leading number is judged on the first digit, so '10' sorts before '7'. If names on your site mix capitals and lowercase, the live order can look wrong even when the rule is A to Z. Make the names consistent, or sort by a date or a number instead.

Stack rules when one field is not enough

You can add more than one sort. The list uses the first rule, then the next rule for items that tie, and so on.

A team page can put the employee of the month first and leave everyone else in a published random order. Add the switch rule first and choose Is ON first. Add Random order second. Reverse those rules and the switch no longer decides the top of the list.

A blog usually wants the newest post first, with a featured post above that. Add the Featured switch as Is ON first. Add the date as newest to oldest second. Items with the switch off still appear. They sit below the featured ones, still in date order. A filter would remove them. Sort does not.

If two posts share a date and you have no second rule, do not expect a stable tie-break you did not set. Add Name as A to Z underneath the date if equal dates should fall in a predictable order.

Build a custom order with a number field

Default directions cannot express 'show pricing, then work, then contact' when those labels would alphabetize differently. Add your own sequence.

Open the CMS panel, hover the Collection, and click the cog to open Collection settings. Add a new field, choose Number, and label it something like Custom sort order. Save the field, then save the Collection. Open each item, type a unique number, and publish the item when it should be live. Back on the list, sort by that field, smallest to largest.

For example: Services is 1, Work is 2, Pricing is 3, Contact is 4. The list follows those numbers even though Contact would lead an A to Z sort. Leave a gap (10, 20, 30) if you expect to insert a page later without renumbering everyone.

The numbers do nothing until a list sorts by them. A second list can ignore the field and sort by date instead.

Publish, then read the first items

Sort in the Designer updates the canvas. The live site updates when you publish. Open the published page and read the first three items against the rule you saved. If the newest post is not first, check that you sorted the date field you meant, and that the item is actually published.

Random order will look 'stuck' between publishes. That is the documented behavior. Publish again when you want a new shuffle.

A filter still decides which items are allowed in. Sort only orders the items that passed. If the featured post is missing, the switch filter or the draft status is the place to look, not the sort direction.

Keeping a custom number field current is ordinary CMS work: change the number, publish the item, and confirm the list. If you would rather send that as a written request, the membership is one plan for every existing Webflow site: $999 per month, including 10 hours of Webflow work. Additional work is $75 per hour. Before work exceeds the included hours, a written estimate is shared and you approve it first.