# Making a comparison table readable on a phone

Why a comparison table turns unreadable on a phone and how to fix it with a responsive layout, frozen columns, stacked cards and readable type.

A comparison table becomes unreadable on a phone when it is written as one wide grid squeezed into a narrow screen. The fix is to change the layout for small screens, not the data, so each listing keeps its details. A responsive table layout, a stacked card view, or a frozen first column with sideways scrolling each solve a different part of the problem. 

- A wide comparison grid fails on a phone because columns shrink below a readable width.
- A responsive table layout reflows rows into stacked cards or lets the table scroll with a frozen first column.
- Landscape orientation gains width but costs height, so it helps only some tables.
- Font size and cell padding decide whether a narrow column can still be read.
- Zoom and scroll let a reader inspect a table but do not fix a layout that hides key details.
 

## Why the table breaks on a phone 

A comparison table breaks on a phone because the screen is narrow and the table is wide. Each column is forced into a sliver of width, so a heading wraps into a column of single words. The reader loses the link between a value and its column label. 

Horizontal scrolling is the first symptom a reader notices in the mobile view. The table overflows the screen edge, and the first column slides away as the reader moves right. Once the listing names are gone, the numbers and features no longer say which option they describe. 

Shrinking the font to fit more columns makes the problem worse. A small font size on small screens forces zoom and pinch gestures for every cell. Pinch zoom then pushes the header off screen, so the reader has to remember column labels while reading values. 

## Choose a responsive table layout 

A responsive table layout changes how the table presents itself as the screen narrows. The layout, not the content, adapts to the available width. Two broad approaches cover most comparison tables: keep the grid and let it scroll, or drop the grid and stack the cells. 

The scroll approach keeps the columns intact and gives the table a defined width inside a scrolling container. The stacked card layout removes the column grid on a narrow screen and turns each row into its own block. Each block carries its listing name and its labeled values. 

The right choice depends on how many columns the table holds and how readers compare values. A table with many short columns suits sideways scrolling with a frozen first column. A table with long text values suits stacked cards, because each value gets the full screen width. 
| Layout | What it keeps | Where it fits | 
| Scrolling grid | The full column structure | Tables with many short values | 
| Frozen first column | Listing names while scrolling | Wide tables read left to right | 
| Stacked cards | Full width for each value | Tables with long text or few columns |  

## Keep listing names in view with a frozen column 

Freezing the first column keeps the listing name visible while the reader scrolls across the other columns. The name stays pinned to the left edge of the scrolling area. Every value the reader reaches still belongs to a named option. 

A frozen first column works well when the table has many narrow columns of specs or numbers. The pinned column takes part of the screen width, so the remaining columns need a sensible minimum width. Set that minimum so a value does not wrap into an unreadable stack. 

A frozen column adds complexity to the styling and can overlap other cells if the widths are set loosely. Test the frozen column at the narrowest screen width you expect. Add a visible edge or shadow so the reader can tell the frozen area from the scrolling area. 

## Turn rows into stacked cards 

A stacked card layout turns each table row into a separate block on a narrow screen. The listing name becomes the card heading, and each value appears with its column label beside it. The reader scrolls down through options instead of sideways through columns. 

Stacked cards suit a comparison table where readers check one listing at a time in the mobile view. Each card repeats the label for every value, so a lone paragraph still makes sense away from the table header. Long values get the full screen width and stay readable. 

The stacked card layout makes side-by-side comparison harder, because two listings sit one above the other. Readers who want to compare a single feature across options must scroll between cards. Keep the card order stable and repeat the feature labels exactly so the eye can find the same row. 

## Set font size and cell spacing for small screens 

Font size on small screens sets the floor for readability in any comparison table. A body size that reads well in a paragraph also reads well in a table cell. Do not shrink table text below the body size to win extra columns. 

Cell spacing matters as much as the font size. Tight padding saves width but pushes values against borders and each other. Padding around each cell gives the eye room to separate one value from the next, even in a narrow column. 

Line length inside a cell also affects reading. A short line of three or four words wraps awkwardly and slows the reader. Allow a cell to wrap at a comfortable width, and let the row grow taller instead of squeezing the text. 

## Use landscape orientation and zoom with care 

Landscape orientation gives a phone more width and less height, which helps a wide table with short rows. The reader turns the device and sees more columns at once. Rows that run long then need more vertical scrolling. 

Zoom and scroll let a reader enlarge a table that still overflows. Pinch zoom is a workaround, not a design. A table that depends on zoom for every cell forces repeated gestures and loses the header as the reader pans. 

Design the table to read at the default zoom, and treat zoom as an extra tool for detail. Keep the header row visible while the reader scrolls, so a zoomed value still has its label. State in the page copy that turning the device sideways shows more of the table. 

## Test the table at a narrow width 

Test the comparison table at the narrowest screen width you expect readers to use. Narrow the browser window or use a device emulator for the mobile view. Watch where the layout breaks and note which column loses its label first. 

Check each of these points on the narrow view: the listing name stays visible, every value keeps its label, no text drops below the body size, and the table never overflows the screen edge. Repeat the check in landscape orientation. 

Run the check with the longest value in each column, not a short sample. Long product names and long feature descriptions expose wrapping problems that short values hide. Fix the layout until every value reads on its own without zoom. 

## Questions about phone table readability 

### Why is my comparison table unreadable on a phone? 

A comparison table is unreadable on a phone because the screen is narrower than the table, so columns shrink and the layout overflows. The first column with the listing names scrolls out of view, and each value loses its label. Changing the layout for small screens, not the data, fixes the problem. 

### Should I use a stacked card layout or sideways scrolling? 

A stacked card layout fits tables with long text values, because each value gets the full screen width. Sideways scrolling with a frozen first column fits tables with many short values that readers compare across options. Pick the layout that matches how readers use the table. 

### Does landscape orientation fix a wide comparison table? 

Landscape orientation helps a wide comparison table with short rows, because the phone gains width. The same rotation costs height, so long rows need more vertical scrolling. Landscape is a supplement to a responsive table layout, not a replacement for it. 

### How small can the font be in a phone table? 

Table text on a phone should stay at the body font size, not below it. Shrinking the font to fit more columns forces zoom and makes every cell harder to read. Let a row grow taller instead of reducing the font size. 

### What does freezing the first column do in a mobile view? 

Freezing the first column keeps the listing name pinned to the left edge while the reader scrolls sideways. Every value in the scrolling area stays tied to a named option. The pinned column takes screen width, so the other columns need a minimum width that keeps values readable.
