An eight-column table may look orderly on a large monitor and become nearly unreadable on a phone. Making everything smaller merely moves the problem. Start by deciding what comparisons readers actually need to make. A table comparing three plan features has different requirements from a complete inventory. The format also imposes limits: a fixed PDF page behaves differently from a responsive webpage.
Preserve the comparisons that matter
Do not discard important information, but examine the purpose of every column. A note repeated in each row may belong once above the table. Long explanations can sometimes move into accompanying prose, provided their relationship to the entries remains unambiguous.
For a few objects with many attributes, a short separate list for each object may work better. If readers must compare objects directly, keeping them in one table may be preferable. Choose the form around the reading task rather than automatically putting every available detail into a grid.
Abbreviations save width but can introduce comprehension problems. Use familiar abbreviations or explain them nearby. Put units in clear headings such as “Width, cm.” This avoids repeating the unit in every cell and makes the numbers easier to compare.
Prefer a simple table structure
Use an identifiable header row and avoid unnecessary merged or nested cells. A simple structure helps both ordinary reading and assistive technology. Tables should express relationships between data, not merely position text and pictures on a page.
Allow sensible wrapping within cells and test long words, web addresses, and numeric identifiers. One unbroken string can widen the entire table. Do not shrink the type until ordinary reading requires constant zooming.
For multipage documents, repeated column headings help where the application supports them. Inspect page breaks: a small remnant of a long row on the next page may lose its context. The right setting depends on the length of individual records and the space available.
Test the actual delivery format
Open the file on a small screen and attempt a specific task, such as finding the price for one entry and comparing it with the next row. Notice whether horizontal movement makes the row label disappear. Looking at a reduced image of the whole page tells you little about actual usability.
If a fixed PDF remains too wide after revision, consider an additional narrow presentation or a structured data file. Explain the purpose of each version. Keep their values synchronized; a readable but outdated table does not solve the problem.