Conditional Formatting in Microsoft Lists: How It Works

Yes. Microsoft Lists can use conditional formatting to change how columns or rows look when their values meet rules—for example, highlighting overdue tasks or making high-priority items stand out. Open the relevant column’s menu and choose Column settings > Format this column; the available formatting controls depend on the column type and the version of the Lists interface.

What conditional formatting means in Microsoft Lists

Conditional formatting is a visual layer applied to list items. It can use a value, such as a status, date, or number, to determine whether a label, background, text color, or other supported display detail should change. A rule might make a task’s status appear green when it is Complete, or highlight a due date when it has passed.

The formatting does not change the stored value. If a date is highlighted, it remains the same date; if a choice is colored, the underlying choice is unchanged. Other users who can see the same list view can see its formatting, but a visual rule does not update a task, send a notification, or enforce a business process. Use a flow or another process for those actions.

Lists is built on Microsoft Lists and SharePoint list capabilities. The same list may be opened from the Lists app, a SharePoint site, or a Teams tab, so the interface can look different even when the underlying data is shared. Formatting is associated with a column or a view, rather than being an Excel-style rule applied to individual worksheet cells.

Column formatting and view formatting

There are two useful scopes to understand. Column formatting changes how values in one column are displayed. It is a good fit for a Status column, a due-date column, or a numeric score. A rule on Status can color the status value without changing the display of other fields in the item.

View formatting can affect the presentation of items across a list view, including a whole row. This is useful when readers need to scan a record as a unit—for instance, making every row for an urgent request visually prominent. View formatting belongs to the selected view, so a different view can present the same records differently.

These options are not interchangeable. A column rule is usually easier to set up for a single field. A row-level design may need view formatting or JSON, especially when its appearance depends on a field that is not the one being displayed. Consider who needs the emphasis and in which views before choosing the scope.

How to add a conditional formatting rule

For a basic column rule in the modern Lists interface, use this sequence:

Open the list and locate the column you want to format.
Select the column heading’s menu, then choose Column settings > Format this column.
In the formatting pane, find Conditional formatting and choose the option to add a rule, if it is available.
Choose the condition and value, then choose the visual treatment offered by the pane.
Review the preview and save or apply the change. Check more than one item to confirm that the rule behaves as intended.

The names and placement of controls can vary as Microsoft updates Lists, and some column types or interfaces may offer different choices. If the pane shows a conditional-formatting section, use its available condition and style controls rather than assuming every type supports the same operators. If the option is absent, check that you are using the modern list experience and that you have permission to edit the list or view.

For formatting that applies to a view, open the view options and choose Format current view, then look for the formatting controls offered there. The exact options may differ by tenant and rollout. A view change is not necessarily a change to every view, so check the view name before applying it.

Practical examples for common lists

Good rules answer a question readers already have: what is late, urgent, blocked, or ready? For example, a project tracker might use distinct formatting for its Status values, while a service-request list could emphasize unresolved items that have passed their target date. A stock list might draw attention to quantities below a chosen threshold.

Task tracker: Highlight a status such as Blocked or At risk so team members can spot work needing attention.
Due-date list: Draw attention to past dates or dates approaching soon. Define whether completed items should still be highlighted; otherwise, an old due date can remain visually alarming after the work is done.
Request queue: Emphasize a High priority choice, or use view formatting to make the entire high-priority row easier to scan.
Inventory list: Flag a low quantity so someone can review it. Treat the highlight as a prompt, not as an automatic reorder or a guarantee that stock counts are current.

Before building a rule, decide what should happen at boundaries. For a numeric threshold, should a value equal to the threshold be highlighted, or only values below it? For dates, does “overdue” include today or only dates before today? These details matter because an unclear condition can produce a view that looks inconsistent to its users.

Using JSON for more control

Lists and SharePoint support JSON-based formatting for cases where the built-in controls do not express the desired design. In the formatting pane, use the advanced mode or the JSON editing option when it is available. Column-formatting JSON can control the rendering of a column; view-formatting JSON can customize the appearance of items in a view. The supported schema and available display features depend on the formatting context.

JSON is presentation logic, not a way to calculate or save new list values. It can test fields and choose styles, but it does not replace a calculated column, update another field, or trigger a workflow. A rule that depends on several fields can be more expressive in JSON than a simple point-and-click rule, but it is also easier to break with a misspelled internal field name or invalid syntax.

When working with JSON, start from Microsoft’s current list-formatting examples or a sample generated by the formatting pane, then make one small change at a time. Test against records that should match and records that should not. If the formatting disappears or displays unexpectedly, restore the previous JSON or return to the built-in formatting options. Avoid copying a JSON example designed for a different context, such as a column formatter, into a view formatter without adapting it.

Limits and design considerations

Formatting is for readability, not data integrity. A user may still enter a value that looks wrong, and a color rule does not prevent saving it. If a condition needs to be enforced, consider list validation or permissions where appropriate; if an action must happen automatically, consider Power Automate. These tools serve different purposes and may require additional configuration or licensing depending on the organization.

Keep the number of visual signals manageable. If every status, date, and number has a different color, users may have trouble identifying what matters. Use labels or icons as well as color when practical, because color alone may not be clear to people with color-vision differences or when viewed on a display with poor contrast. Check the result in the actual list view and on the devices your audience uses.

Also consider whether the rule should appear in every view. A formatting choice that helps a team’s operational queue may distract in a summary view. Views can be filtered and sorted separately from their formatting; a highlight does not remove items or change their order. If the real need is to show only overdue tasks, a filtered view may be more useful than coloring every overdue row.

Common problems and how to troubleshoot them

If a rule does not appear to work, first inspect the values in the list. Choice labels must match the intended condition, dates must be valid dates rather than text, and blanks may behave differently from populated values. Confirm that the rule is attached to the intended column or view, and verify that you are looking at that view rather than another one.

No conditional-formatting control: Confirm that you are in the modern experience, open the correct column menu, and check whether that column type exposes the feature. If not, review available JSON formatting options.
Only one field changes: You may have applied column formatting. Use view formatting if the goal is to change the whole row.
The rule seems to affect the wrong records: Recheck the chosen comparison, boundary values, blanks, and whether the condition refers to the intended field.
Formatting is missing in another view: Check whether the format was saved to a specific view. A view-level change should not be assumed to apply to every view.
Colors are difficult to read: Choose stronger contrast and test with realistic list values. A color should communicate emphasis without hiding the text.

When several people maintain a list, document what each color or style means. This is especially useful when custom JSON is involved: a brief note in the list’s guidance or team documentation can explain the rule and help future owners change it safely.

When to use a view, a flow, or another option

Choose conditional formatting when the goal is to make existing information easier to interpret. Choose a filtered or sorted view when people need a focused subset or a useful order. Choose Power Automate when a condition should send a message, create a task, or update information in response to a trigger. Those approaches can complement one another, but formatting alone does not perform the flow’s actions.

Excel is another option for analysis, charts, and spreadsheet-specific conditional formatting, but it is not simply a different screen for editing Lists rules. Exporting or connecting list data to Excel can create a separate workflow with its own refresh and collaboration considerations. If the list is the team’s shared operational record, configure the display in Lists where users work with that record.

Frequently Asked Questions

Can Microsoft Lists highlight an entire row?
Yes. Use view formatting when you want a row’s appearance to depend on a condition. Column formatting is intended to change the display of values in that column, not automatically every field in the row.

Does conditional formatting change the data?
No. It changes presentation only. The stored status, date, or number remains unchanged, and formatting does not validate a value or trigger an action.

Can I format a row based on a different column?
View formatting and JSON can support more advanced, field-dependent designs than basic column formatting. The exact options depend on the formatting context and available interface; test the rule with matching and nonmatching records.

Why can’t I see Conditional formatting?
The control may vary by interface, column type, and Microsoft rollout. Check the modern Lists experience and the column’s Column settings > Format this column pane. If the built-in control is unavailable, JSON formatting may be an option for that context.

Can conditional formatting send an alert?
No. It only changes how information is displayed. To send an alert or perform another action when a condition is met, configure an appropriate workflow, such as a Power Automate flow.

Will a rule appear in every view?
Not necessarily. Column and view formatting have different scopes, and view formatting is associated with a particular view. Check each view your audience uses rather than assuming one change applies everywhere.

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.