Column Formatting
Common Use Cases
- Status pills: color-coded labels such as Open, In Progress, and Done
- Data bars: a bar whose length reflects a number, like percent complete
- Icons: a checkmark, flag, or warning sign tied to a value
- Clickable elements: turning a value into a link or an action button
- Conditional color: red, amber, or green based on a threshold
- Trend cues: arrows or symbols that signal direction at a glance
Benefits
- At-a-glance reading: users scan color and shape instead of parsing text
- No-code option: the design panel builds common styles without JSON
- Reusable: the format saves with the view and applies to every item
- Non-destructive: it only changes appearance, never the stored data
- Conditional logic: styles respond to the value in each row
- Consistent: everyone viewing the list sees the same visual rules
How It Works
- JSON behind the scenes: a small JSON object maps values to styles
- Design mode: a panel offers colors and icons without writing JSON
- Conditional expressions: formulas decide the style for each value
- Field references: the JSON reads the current field or other columns
- Action buttons: JSON can render a button that opens a link or flow
- Applies per view: the format lives on the view, not the data
Limits and Nuances
- Presentational only: it never filters, sorts, or changes the data
- Column type matters: some types support fewer formatting options
- JSON can get complex: elaborate styles are harder to maintain
- Mobile rendering: some styles render differently on phones
- View-scoped: applying it everywhere means formatting each view
Common Questions About Column Formatting
What is column formatting in SharePoint?
Column formatting controls how the values in a single column appear, using JSON or a no-code design panel. It can apply colors, data bars, icons, links, and action buttons based on each item value, without changing the stored data. It is the quickest way to make a list readable at a glance, turning plain text like a status field into colored pills or icons.
Do I need to know JSON to use it?
Not for the common cases. The Format this column panel includes a design mode with ready-made choices for colors and icons that require no code. For anything beyond that – custom thresholds, buttons, or referencing other columns – you switch to advanced mode and paste a JSON snippet. Many teams start in design mode and only reach for JSON when they need something specific.
What is the difference between column and view formatting?
Column formatting styles one field, while view formatting restyles the entire row. If you want a single status column to show colored labels, that is column formatting. If you want the whole row to turn red when an item is overdue, that is view formatting. They use the same JSON approach and can be combined on the same list.
Does column formatting change the underlying data?
No. Formatting is purely visual and lives on the view, not on the items. The values stored in the list stay exactly as entered, so exports, flows, and searches see the raw data. This makes formatting safe to experiment with, since clearing it returns the column to its default appearance with nothing lost.
Which column types can be formatted?
Most common types support formatting, including text, choice, number, date, person, and yes or no columns. Some specialized types offer fewer options, and a few cannot be formatted at all. The design panel only shows the choices that the selected column supports, which is a quick way to see what is possible before reaching for JSON.
Is column formatting worth the effort?
For lists that people read often, yes. Greg Zelfond, the consultant behind LookBook 365, uses formatting to make trackers self-explanatory: a glance at the colors tells the team what is on track and what needs attention, with no training required. The effort is small and it pays back every time someone opens the list, which is the mark of a design that earns its keep.