View Formatting
Common Use Cases
- Conditional row color: turning a whole row red when an item is overdue
- Alternating bands: striping rows so long lists are easier to read
- Custom cards: redesigning the gallery layout into branded tiles
- Emphasis: highlighting rows that meet an important condition
- Compact layouts: tightening rows to fit more on screen
- Dashboards: making a view read like a status board
Benefits
- Whole-row styling: format every row, not just one column
- Layout control: reshape the gallery into custom cards
- Conditional logic: styles respond to values across the row
- Non-destructive: appearance only, the data is unchanged
- Reusable: the format saves with the view for all users
- Scannable: lists turn into something readable at a glance
How It Works
- Row JSON: a JSON object styles the row container and its cells
- Gallery JSON: a separate format defines card layout in gallery view
- Conditional expressions: formulas choose styles per row
- References fields: the JSON reads any column in the row
- Format current view: applied from the view dropdown menu
- Saves with the view: each view carries its own formatting
Limits and Nuances
- Presentational only: it changes appearance, never the data
- JSON complexity: advanced layouts are harder to maintain
- View-specific: each view must be formatted on its own
- Performance: very heavy JSON can slow rendering
- Mobile differences: some designs render differently on phones
- Pairs with column formatting: the two are often combined
Common Questions About View Formatting
What is view formatting in SharePoint?
View formatting uses JSON to style an entire list view – whole rows and the gallery layout – rather than a single column. It can color rows by status, add alternating bands, or turn a gallery into custom cards. Like column formatting, it is purely visual and saves with the view, so the underlying data is never changed by how the view is styled.
How is view formatting different from column formatting?
Column formatting styles one field, while view formatting styles the whole row and the layout around it. If you want a status column to show colored labels, use column formatting. If you want the entire row to turn red when overdue, or the gallery to display branded cards, use view formatting. They share the same JSON approach and are frequently combined on one list.
Do I have to write JSON for view formatting?
Generally yes for row and card layouts, since the design panel covers more of the simple column scenarios. Many teams start from a sample JSON snippet and adjust the colors and conditions to fit. The formatting pane lets you paste JSON and preview the result instantly, so you can iterate without committing until it looks right.
Can view formatting change my data?
No. View formatting only affects how the view looks, and it saves on the view rather than on the items. Every value in the list stays exactly as entered, so exports, searches, and flows see the raw data. Clearing the formatting returns the view to its default appearance with nothing lost.
Does the formatting apply to every view of the list?
No. Formatting is scoped to the specific view you edit. A list can have many views, and each carries its own formatting, so a board-style view and a plain table view of the same list can look completely different. To apply a look everywhere, you format each view, or create one well-formatted view and point people to it.
Is view formatting worth learning?
For lists people read daily, it pays off quickly. Greg Zelfond, the consultant behind LookBook 365, uses view formatting to turn ordinary lists into status boards that communicate at a glance, which is often the difference between a list people use and one they ignore. The investment is a little JSON up front in exchange for clarity every time the list is opened.