Both auto-fill and auto-fit tell the browser to create as many grid tracks as possible within the available space. The key difference: auto-fill preserves empty tracks (leaving visible gaps where items could go), while auto-fit collapses empty tracks and lets existing items stretch to fill the available space. Think of auto-fill as "reserving seats" and auto-fit as "only setting up chairs for people who showed up."

Use auto-fill when you want to maintain a consistent grid structure regardless of content count — for example, dashboard card layouts where empty slots should remain visible, product listing pages that load more items dynamically, or any layout where placeholder space improves UX. Use auto-fit when you want content to expand gracefully — like a tag cloud, a centered navigation bar, or a flexible card gallery where the last row should stretch to fill width.

Without minmax(), the behavior difference is barely noticeable. The minmax(min, 1fr) pattern is essential because the 1fr maximum allows auto-fit items to grow and fill extra space when empty tracks collapse. If you use a fixed value like minmax(150px, 150px), both auto-fill and auto-fit behave identically — columns stay at 150px and the extra space just sits unused. The 1fr is what makes the visual difference dramatic.

In most cases, no. Modern browsers handle both efficiently. However, auto-fill can create dozens of empty tracks in very wide containers with small minimum column widths (e.g., a 1920px container with 80px min columns could generate ~24 tracks). While this is generally fine, if you're animating grid properties or have complex nested grids, auto-fit may be slightly more performant since it collapses unused tracks. For 99% of use cases, choose based on design needs, not performance.

Yes, but you'll miss the magic. repeat(auto-fit, 200px) is valid CSS — it creates as many 200px columns as fit, and collapses empty ones. However, without 1fr, there's no stretching behavior. The items stay at exactly 200px. The minmax() function unlocks responsive flexibility: columns can be at least the minimum but expand when space allows. This is what makes auto-fit layouts feel truly fluid and responsive.

When the container width is less than minmax()'s minimum value, both auto-fill and auto-fit behave the same: they create a single column, and the item width is clamped to the container width (potentially overflowing if content is larger). This is why choosing a sensible minimum (like 200px–280px) is important for mobile-responsive designs. Test your layout at narrow widths to ensure items don't become unusably small.

The browser calculates available space after subtracting gaps and padding. For example, with a 620px container, 12px gap, and minmax(140px, 1fr): available width ≈ 620px − (n−1)×12px (where n is the number of columns). The browser then determines how many 140px columns fit. Gaps consume space, so larger gaps reduce the maximum number of columns. This is why adjusting gap can sometimes cause items to wrap or unwrap.

Yes! Both auto-fill and auto-fit are part of the CSS Grid Level 1 specification and have excellent browser support — all modern browsers including Chrome 57+, Firefox 52+, Safari 10.1+, and Edge 16+ support them fully. They're safe for production use. Internet Explorer 11 had partial grid support but did not support auto-fill/auto-fit, so if IE11 support is required, you'll need a fallback like @supports queries.

Absolutely! You can mix auto-fill/auto-fit with fixed track sizes in grid-template-columns. For example: grid-template-columns: 200px repeat(auto-fill, minmax(150px, 1fr)) 80px; — this creates a 200px sidebar, flexible center columns, and an 80px end column. The auto-fill/auto-fit only applies to the repeated section, while fixed tracks remain constant. This is powerful for complex responsive layouts.

Check three things: (1) The minmax() maximum must be a flexible unit like 1fr — if it's a fixed pixel value, items won't stretch. (2) Ensure there are fewer items than the maximum possible columns — if all tracks are filled, auto-fill and auto-fit look identical. (3) Check that grid items don't have explicit max-width or justify-self constraints that override the grid's sizing. Use your browser's DevTools grid inspector to see exactly how tracks are being sized.