Tables are the workhorses of SaaS products and dashboards. They're also where many products quietly fail: misaligned numbers, hidden actions and filters nobody can find. Here's how to design tables people can actually work with.
Get the basics right
| Content | Alignment |
|---|---|
| Text | Left |
| Numbers and amounts | Right (so digits line up) |
| Dates | Consistent format, usually left |
| Status | Left, with a label not just a colour |
| Actions | Right, or at the end of the row |
- Use tabular (monospaced) figures for numbers.
- Keep headers short and clear, with units ("Amount (₹)").
- Avoid heavy borders; light row dividers or zebra striping are enough.
Choose the right density
Offer comfortable and compact density options for power users who scan hundreds of rows. Row heights around 40 to 56 pixels suit most products.
Sorting, filtering and search
- Make sortable columns obvious and show the current sort direction.
- Put the most common filters in view; hide advanced ones in a panel.
- Show active filters as removable chips, with a "Clear all" option.
- Add search for tables with many rows.
Row actions and bulk actions
- Show row actions on hover (desktop) and keep them in a menu on smaller screens.
- Let people select rows with checkboxes and show a bulk action bar when items are selected.
- Make the whole row clickable when it opens a detail view, but keep checkboxes and actions separate.
Watch out
Never make destructive bulk actions one click away. Confirm, show how many items will be affected and offer undo where possible.
Pagination vs infinite scroll
| Option | Best for |
|---|---|
| Pagination | Finding and returning to specific records |
| Load more | Browsing with occasional deep dives |
| Infinite scroll | Feeds, rarely for data tables |
Empty, loading and error states
Design what the table looks like with no data, while loading (skeleton rows) and when something fails. See empty states and error messages.
Tables on mobile
Wide tables don't fit phones. Options: show only key columns with a tap to expand, turn rows into cards, or allow horizontal scrolling with a fixed first column.
Make tables accessible
Use real table markup, proper headers, visible focus states and labels for icon-only actions.
For the bigger picture, see SaaS dashboard design and cognitive load in dashboards.
FAQ
How should you align data in a table?
Left-align text, right-align numbers so digits line up, keep date formats consistent and place actions at the end of the row.
Should data tables use pagination or infinite scroll?
Pagination is usually better for data tables because people need to find, compare and return to specific records. Infinite scroll suits feeds more than tables.
How do you design tables for mobile?
Show only the most important columns and let users expand rows, convert rows into cards, or allow horizontal scrolling with the first column fixed.
Key takeaways
- Align text left and numbers right, with tabular figures.
- Offer density options for power users.
- Make sorting, filters and active filters obvious.
- Design row actions, bulk actions and every state.
- Plan a deliberate mobile pattern.
What to do next
Open your busiest table and check alignment, filters and empty states against this list. For SaaS and dashboard design help, see our SaaS product design service.