Tables vs. Lists
Use a list for a simple set or sequence of similar items; use a table when readers need to compare structured information across two or more attributes or columns. Microsoft specifically warns not to use a table merely to display a simple list.
Choose a list for a simple set or sequence; choose a table when the information benefits from row-and-column relationships or multiple attributes.
Key details
Important caveats
List Boundary
Lists are better for simple related items, sequences, or priorities that do not need column relationships.
Table Boundary
Tables are useful for structured comparisons, values, categories, or items with multiple attributes; responsive width is a practical constraint.
Further guidance
Practical Application
Choose a list for a simple set, sequence, or priority. Choose a table when readers need to compare multiple attributes across items or understand row-and-column relationships.
Reader Check
Would removing the columns lose meaningful comparisons? If not, a list is usually simpler; if yes, a table may be the clearer structure.
Worked Example
Example: use a three-item list for setup steps, but use a table to compare three service plans across price, storage, and support level.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Lists (opens in a new tab)Microsoft Style Guide · Bulleted lists for unordered related items and numbered lists for sequences or priorities
- Tables — Microsoft Style Guide (opens in a new tab)Microsoft Style Guide · House-style guidance on when structured data belongs in a table instead of a simple list