CSS Fix

Fix CSS Grid breaking on mobile without fighting the layout.

When a grid looks perfect on desktop but starts crushing cards, overflowing sideways, or behaving strangely on phones, the problem is usually not Grid itself. It is usually rigid column sizing, aggressive track definitions, or child elements refusing to shrink.

Browse CSS Fixes See the Difference

Common production bug
Usually a track sizing issue
Often fixed with simpler rules

Quick diagnosis

If your grid breaks on mobile, the browser is usually doing exactly what you told it to do. The problem is often that the track rules are too rigid for the available width.

Columns are too rigid Fixed widths or aggressive minmax() values leave no breathing room on small screens.

Children refuse to shrink Long text, images, buttons, nested flex layouts, or code blocks can force overflow inside the grid.

Gap, padding, and width stack up A layout that fits comfortably on desktop can overflow on mobile once spacing reduces the usable width.

No mobile fallback exists A grid that works beautifully at 1200px often needs fewer columns below 768px.

What the bug looks like

Cards get squeezed, text spills out, horizontal scroll appears, or the grid feels cramped and unstable on smaller screens.

Why it happens

The track sizing is too ambitious for the screen, or one child inside the grid is wider than the grid can safely absorb.

What usually fixes it

Looser column sizing, fewer columns on smaller screens, and children that are allowed to shrink properly inside the grid.

Why CSS Grid gets blamed unfairly

Grid often becomes the scapegoat because the visible break happens in the layout. But Grid is usually just enforcing the track logic you defined. If the columns demand more width than the screen has, Grid will not magically save the design for you.

That is why the smartest fix is often not more complexity. It is reducing rigidity.

Common signs the track sizing is too aggressive

Cards almost fit, but still overflow That usually means gaps, padding, or minimum sizes are pushing the total width just over the limit.

One card breaks the whole row The grid may be fine in general, but one child is refusing to shrink or wrap.

The layout looks “compressed” instead of clean Even without full overflow, the columns may be too ambitious for a phone-sized viewport.

Recommended fix

Safer mobile pattern

This is a stable starting point for most card grids. It uses simple desktop columns, gives children room to shrink, and switches cleanly to one column on smaller screens.

.cards {
  display: grid;
  grid-template-columns: repeat(3, minmax(0, 1fr));
  gap: 24px;
}

.card {
  min-width: 0;
}

.card img {
  max-width: 100%;
  height: auto;
  display: block;
}

@media (max-width: 768px) {
  .cards {
    grid-template-columns: 1fr;
    gap: 16px;
  }
}

Common broken version

Too much minimum width

This looks elegant, but it often causes trouble when the minimum size is too ambitious for a phone.

.cards {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(320px, 1fr));
  gap: 24px;
}

Why this breaks

A phone viewport may not have enough usable space for a 320px track once padding, gaps, and parent width are factored in. That can lead to overflow or awkward compression.

Simple rule: if mobile is breaking, test whether your minimum column size is simply too ambitious.

`minmax()` is doing too much

A smart-looking rule can still be too rigid if the minimum width is larger than the layout can really support on mobile.

Children are wider than the grid expects

Long text, media, or nested layouts can create overflow even when the track definition looks reasonable.

The grid never gets a clean mobile fallback

Many layouts work better with fewer columns or one column on mobile instead of trying to be “smart” at every width.

Fast practical rule

If the grid is breaking on mobile, reduce complexity first. Fewer columns, smaller gaps, and children with min-width: 0; solve more Grid bugs than people expect.

Debug checklist

Check whether the parent container has padding that reduces the real usable width.
Inspect the grid track definition and look for overly large minmax() values.
Add min-width: 0; to grid children that contain long text, images, or nested flex items.
Test whether buttons, code blocks, or media elements are forcing horizontal overflow.
At mobile breakpoints, reduce the number of columns before trying more advanced fixes.

Best first move Switch to one column on smaller screens and confirm the bug disappears before tuning upward again.

Most overlooked fix Add min-width: 0; to grid items when nested content is causing overflow.

Better mindset Do not fight mobile with complicated track math if a simpler column structure solves the real problem.

Good mobile-friendly pattern

For many production layouts, explicit desktop columns plus a simple mobile fallback is more stable than trying to make one clever rule handle every screen size.

In real projects, predictable usually beats clever.

Alternative pattern

Simple and stable

.cards {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: 20px;
}

@media (max-width: 640px) {
  .cards {
    grid-template-columns: 1fr;
  }
}

Final takeaway

CSS Grid breaking on mobile is rarely a sign that Grid itself is unreliable. It is usually a sign that the layout is asking too much from the available width.

Relax the track sizing, let children shrink, and give mobile a simpler fallback. Once you do that, the grid usually becomes much easier to trust.

Want more fixes like this?

Browse more CSS debugging guides or jump straight to the full FrontFixer library.

Browse CSS Fixes All Fixes