Help

This Product Ideas board is currently undergoing updates, but please continue to submit your ideas.

Adjust header height

cancel
Showing results for 
Search instead for 
Did you mean: 
Pierre-Alexand2
6 - Interface Innovator
6 - Interface Innovator

It would be usefull to be able to adjust the header height. I woud use this feature to redure the width of a fied and still be able to read the header.

33 Comments
micky88
4 - Data Explorer
4 - Data Explorer

We neeeeed this. so basic...

mrmartin
4 - Data Explorer
4 - Data Explorer

Why is this still not possible???? It's worthless that a narrow value such as a checkbox, if you make it narrower, it is impossible to read what the column name is... Very frustrating.

Menashkes
5 - Automation Enthusiast
5 - Automation Enthusiast

Hi,

I’m quite surprised that Airtable does not have the ability to change the height of grid view headers. So often (most of the time?), one needs a descriptive header that is far wider than the data. It’s a total waste of screen space to make the entire column wide enough for titles.

Spreadsheets understood this decades ago by enabling adjustable height on headers (field names) so the data column widths could be optimized for screen width without sacrificing readability of the headers.

Please prioritize adding the capability to adjust grid view header heights.

Thanks!

------

Hi,

Guillermo from Airtable here 

! Thanks for reaching out.

I completely understand your concern about the limitations of not being able to change the height of grid view headers in Airtable. Your point about needing descriptive headers that may be wider than the data itself is well taken, and we value your input on this matter.

I want to shed some light on the current design decision regarding this feature. The lack of text wrapping and adjustable header heights in our grid view is intentional. Our aim is to maintain a consistent row height to prevent the creation of excessively large rows that can lead to a cluttered and less user-friendly interface.

We believe that the grid view should provide a concise overview of multiple records at a glance, while the expanded record view is designed to offer a more detailed and comprehensive look at individual entries. By keeping the row heights consistent, we strive to strike a balance between displaying essential information efficiently and avoiding visual overload.

Your feedback is invaluable to us, and we will certainly take your suggestion into consideration as we continue to improve and refine the Airtable experience for all our users. If you have any more suggestions or feedback, please don't hesitate to share them with us.

Thank you for your understanding and for being a valued member of the Airtable community.

Best,
Guillermo-Airtable Support Specialist


---


Thank you, Guillermo, for the thoughtful response. 
 
However, your explanation doesn't quite add up. If you can adjust the heights of all the other rows, insisting on maintaining consistency logically means the header's height should be adaptable as well.

The point that the grid view is intended for a concise overview falls short when considering the reality: your customers are employing it in diverse manners. Being forced to expand a column significantly wider than the necessary data width is not just inconvenient—it's a major drawback. This detracts significantly from the experience on your platform, which is otherwise amazing, innovative, and brilliant.

Your attempt to preserve the header row height constant, ironically, leads to a counterproductive outcome: more clutter (either through cut-off titles or disproportionately wide columns) and a decline in user-friendliness. This prompts me to challenge your stance; it appears the approach has been misguided.

It's only a matter of time before you recognize this as an issue that should have been addressed much earlier.

---
 
Hi,

Thanks for providing such detailed and thoughtful insights! Having this kind of context is incredibly helpful for our product team as we think through different features and their corresponding use cases.

I’ve officially logged your feature request and our team will be actively exploring possibilities to implement it in the future. Thanks for surfacing it! To stay on top of all things new at Airtable, please visit our What's new page.