{"id":6058,"date":"2025-06-11T11:17:48","date_gmt":"2025-06-11T16:17:48","guid":{"rendered":"https:\/\/frontendmasters.com\/blog\/?p=6058"},"modified":"2025-06-27T12:08:10","modified_gmt":"2025-06-27T17:08:10","slug":"1fr-1fr-vs-auto-auto-vs-50-50","status":"publish","type":"post","link":"https:\/\/frontendmasters.com\/blog\/1fr-1fr-vs-auto-auto-vs-50-50\/","title":{"rendered":"1fr 1fr vs auto auto vs 50% 50%"},"content":{"rendered":"\n

Are these columns the same?<\/p>\n\n\n

.grid<\/span> {\n  display<\/span>: grid;\n\n  grid-template-columns<\/span>: 1<\/span>fr  1<\/span>fr;\n  grid-template-columns<\/span>: 50%<\/span>  50%<\/span>;\n  grid-template-columns<\/span>: auto auto;\n}<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
I mean, obviously they aren’t literally the same, but you also probably won’t be surprised that they have different behavior as well. And yet…. they do<\/em> kinda basically do the same thing. Two equal width columns.<\/p>\n\n\n
\n
\"A<\/figure>\n<\/div>\n\n\n
Above is a screenshot of three different grids, using each of those different grid-template-columns<\/code> I showed above. And indeed, they all seem to do the same thing: two equal width columns. I’ve put a red line down the middle and right edge of the container for illustration purposes.<\/p>\n\n\n\n
But things start to change as we do different things. For instance, if we apply some gap<\/code> between the columns. Here’s the examples with 16px<\/code> of gap<\/code> applied:<\/p>\n\n\n
\n
\"Screenshot<\/figure>\n<\/div>\n\n\n
Now the grid with grid-template-columns: 50% 50%;<\/code> is busting outside of the container element. Sometimes we think of % units as being quite flexible, but here we’re rather forcefully saying each columns needs to be 50% as wide as its parent element, so the width of the whole grid is actually 50% + 16px + 50%<\/code> which is wider than 100%. <\/em><\/p>\n\n\n\n
This is pretty awkward and largely why you don’t see columns set up using % values all that much. But it still can be valuable! The “sturdiness” of setting a column that way can be desirable, as we’ll see. If we wanted to prevent the “blowout”, we could account for the gap ourselves. <\/p>\n\n\n
.grid<\/span> {\n  display<\/span>: grid;\n\n  \/* Make each column smaller equally by half the gap *\/<\/span>\n  grid-template-columns<\/span>: repeat<\/span>(2<\/span>, 50%<\/span> - calc(16px<\/span> \/ 2<\/span>));\n}<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
Another unusual situation can be with auto<\/code>. That keyword has some rather special behavior, and it may be worth reading the whole bit that MDN has to say<\/a>. What’s helpful to me though is to think about the “intrinsic size” of the content inside that auto<\/code> column. That can be easy to know. If a column contains only an image that is 200px wide, the intrinsic size is 200px, and the auto column will be 200px. It’s tricky though when the content is text and there are multiple auto<\/code> columns with different<\/em> text. <\/p>\n\n\n
\n
\"A<\/figure>\n<\/div>\n\n\n
See above how the auto<\/code> column with more text is larger than the auto<\/code> column with less text. I have no idea how to explain how that works, but it does make some intuitive sense after a while, even if it feels a bit dangerous to use since it’s hard to know exactly what it’s going to do with arbitrary text. <\/p>\n\n\n\n
Let’s consider an <img><\/code> within the columns that is a bit wider than the current width of the columns. Each of the column setups we have behaves a bit differently here.<\/p>\n\n\n
\n
\"Screenshot<\/figure>\n<\/div>\n\n\n
The sturdy 50%<\/code> column remain in place, and the image overflows it. The auto<\/code> column grows, but not only to contain the image but a bit wider, as if it’s balancing the intrinsic weights across both columns (or something?). <\/p>\n\n\n\n
The column using fr<\/code> units (which essentially mean “fractions of the remaining space”) grows to contain the image, but then no more, and its sibling fr<\/code> columns takes up the remaining space.<\/p>\n\n\n\n
Interestingly, if we do the common thing and constrain the width of the image to a max-width: 100%<\/code>, the 50%<\/code> and 1fr<\/code> columns come back down to half width. <\/p>\n\n\n
\n
\"Screenshot<\/figure>\n<\/div>\n\n\n
Generally, I’d say that fr<\/code> units for columns behave the most intuitively and predictably and that’s why you see more grid setups using them. <\/p>\n\n\n\n
But fr<\/code> units are subject to “blowouts” which can be surprising. A way to think about it is that, however you’ve sized a column, the minimum width of that column is essentially auto<\/code>, and that can prevent it from staying sized how you want it to when there is content that pushes it wider. For instance, putting a long URL (no dashes and no spaces in a URL means it can’t “break” or wrap naturally). <\/p>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
You can see the columns blowing out in the auto<\/code> and 1fr<\/code> columns above. Trying to apply overflow<\/code> will not work here alone. We need to essentially give the column permission to be smaller. I typically do that like this:<\/p>\n\n\n
.grid<\/span> {\n  display<\/span>: grid;\n \n  \/* prevent blowouts *\/<\/span>\n  grid-template-columns<\/span>: repeat<\/span>(2<\/span>, minmax(0<\/span>, 1<\/span>fr));\n}<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
That minmax(0, 1fr)<\/code> still sizes the columns at 1fr<\/code>, but allows it to shrink in width below what auto<\/code> would be, meaning using overflow<\/code> will actually work.<\/p>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
There is more to know here, for sure. For instance, all your columns don’t need to be equal. You can mix and match as makes sense.<\/p>\n\n\n
.grid<\/span> {\n  display<\/span>: grid;\n\n  grid-template-columns<\/span>: 20%<\/span> 1<\/span>fr;\n  grid-template-columns<\/span>: 2<\/span>fr 5<\/span>fr 50px<\/span>;\n  grid-template-columns<\/span>: auto 1<\/span>fr;\n  grid-template-columns<\/span>: 50ch<\/span> auto 2<\/span>fr 1<\/span>fr;\n}<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
And there are more keywords that are worth knowing about, namely min-content<\/code>, max-content<\/code>, and fit-content()<\/code>. They are worth playing with particularly if you’ve found yourself in a bind where you can’t quite see to get columns to do what you want. Perhaps we can cover them in more detail later, if you’d find it interesting.<\/p>\n","protected":false},"excerpt":{"rendered":"
There are several different ways to do equal width columns. But some are, uh, more equal than others.<\/p>\n","protected":false},"author":1,"featured_media":6089,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"sig_custom_text":"","sig_image_type":"featured-image","sig_custom_image":0,"sig_is_disabled":false,"inline_featured_image":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[7,123],"class_list":["post-6058","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-post","tag-css","tag-grid"],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/frontendmasters.com\/blog\/wp-content\/uploads\/2025\/06\/1fr-1fr-vs-auto-auto-vs-50-50.jpg?fit=1140%2C676&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts\/6058","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/comments?post=6058"}],"version-history":[{"count":4,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts\/6058\/revisions"}],"predecessor-version":[{"id":6379,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts\/6058\/revisions\/6379"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/media\/6089"}],"wp:attachment":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/media?parent=6058"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/categories?post=6058"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/tags?post=6058"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}