I am working on a table of fixed height and due to the large data, I need both vertical and horizontal scrolling. Although, I am thinking that users might get confused.

If it is ok to use them both, what would be potential ux adjustments that I could make to the table in order for the users to know that there is more content and scrolling is required? (e.g. not displaying the entire row at the end of the table or use shadows or have the scrollbars always visible)

  • If you need both, then use both. It's not like you can just make peoples display devices larger.
    – musefan
    Commented Oct 2, 2020 at 10:38
  • Do you mean that the table data itself is scrollable or the page it is on? Both are valid options when done right.
    – jazZRo
    Commented Oct 2, 2020 at 11:02
  • Thank you for your replies. The table data is scrollable, not the page.
    – george
    Commented Oct 2, 2020 at 11:48
  • If you scroll up/down, then have the top legend fixed. If you scroll left-right, have the left legend fixed. Then the data will make sense. Once the legend scrolls out of range, there might be a lot of back-and-forth scrolling to make sense of the data.
    – Steve
    Commented Jun 24, 2022 at 20:39

1 Answer 1


It is common in ERP (Enterprise Resource Planning), CRM and a lot of other tools. The main question is: What is the key ID the user is looking for in this data table?

Let start it from the very basics:

  • All data tables have these three common build blocks: Column, Row, Cell.
  • Column and rows help the so-called scanning.
  • The cells help to identify the key data, information, etc.
  • If it is about scrolling, the main question is: is there any redundant information in this data table? Like all the columns contains information about a date. (YYY.MM.DD - 2020.09.30). Or the rows are redundant? (Fix content like Screen size, OS type, 5G compatibility etc. where the columns contain the name of each of the products.)

So the main quest is: how user scans this data table?

  • It is column specific? (Vertical)

  • Or it is row specific? (Horizontal)

The use case for vertical scrolling: Choosing the column > Scrolling and scanning > Identifying.

The use case for horizontal scrolling: Scrolling and scanning > Identifying > Choosing (the related column)

What is the key identifier in a data table?

  • Mostly it is in the very first 2-3 columns or rows. Like ID, Class, Name (Unique identifier)

Best practices:

  • If there is a row or column that is redundant, you can make it collapsible or put them into a dropdown menu.
  • Or you can add an arrow (Right-Left) next to them.(If the column contains the date, the use just can step between days or weeks or months etc.
  • You can make the very first column (of first 1-2 columns) fix. They will stay on the left side of the screen and every other columns are scrollable. (Sticky columns)
  • You can add a Settings menu where user can turn on/off which column or row should be visible.
  • You can also add accordion to these data tables, so groups of rows or columns can be closed or opened.

And there are plenty of other solutions. Search for mobile ready or mobile friendly data tables. ;)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.