Webflow Flex Cards Overflow on Mobile: What to Check
Inspect flex direction, wrapping, child widths, and gaps when Webflow cards refuse to fit a phone screen. Flexbox controls the arrangement of a parent’s direct children. A desktop row can remain too wide on mobile when wrapping is disabled, children have fixed or minimum widths, or their combined widths and gaps exceed the available space. Styling a grandchild does not change the outer row’s flex behavior.
Based on the official documentation linked below. Editor labels and available controls can vary by version; verify changes on your published site.
The short version
Inspect flex direction, wrapping, child widths, and gaps when Webflow cards refuse to fit a phone screen.
Why this happens
Flexbox controls the arrangement of a parent’s direct children. A desktop row can remain too wide on mobile when wrapping is disabled, children have fixed or minimum widths, or their combined widths and gaps exceed the available space. Styling a grandchild does not change the outer row’s flex behavior.
Find the setting that owns the problem
Select the flex parent in the Navigator. At the relevant mobile breakpoint, choose a vertical direction for a one-column layout or enable wrapping when multiple rows are intended. Then inspect each direct child’s width and sizing behavior rather than forcing the whole section to clip.
Before changing your layout, run a free mobile-friendly test for public HTML checks and available Lighthouse diagnostics. Then verify the specific problem on a real phone; the test does not edit your site.
A focused repair checklist
Make the change on a saved copy or staging version when available. Keep the current page URL and capture the failing width so you can compare the same state after the repair.
- Find the parent that directly contains the overflowing cards.
- Choose the intended mobile direction or wrap setting in Layout.
- Review child widths, minimum widths, padding, and the parent gap.
- Check narrow phones and long card titles before publishing.
What not to assume
Wrap alone cannot fix a child that is wider than its container. Avoid setting overflow hidden on the whole page to conceal cards or focus indicators. Keep an intentional horizontal carousel distinct from accidental overflow.
| Approach | How it works | Best fit |
|---|---|---|
| Platform layout settings | Change the setting responsible for the layout | First choice when the editor exposes the control |
| Targeted custom repair | Adjust the affected component on a test copy | When native settings do not cover the problem |
| Whole-site redesign | Rework templates and critical visitor tasks | Only when the current structure prevents durable fixes |
Verify the published result
Check the affected Webflow page on a narrow phone, a wider phone, tablet, and desktop. Move between widths rather than checking only preset editor previews. Open the menu, follow the important link, and complete the relevant form or shopping task. An editor screenshot alone cannot prove those interactions work.
Run the free mobile-friendly test for public HTML signals and available Lighthouse diagnostics, then use real-device testing to confirm the visual repair. The automated audit does not sign in to your editor, change the website, or certify that every breakpoint works.
Key takeaways
- Select the flex parent in the Navigator. At the relevant mobile breakpoint, choose a vertical direction for a one-column layout or enable wrapping when multiple rows are intended. Then inspect each direct child’s width and sizing behavior rather than forcing the whole section to clip.
- Wrap alone cannot fix a child that is wider than its container. Avoid setting overflow hidden on the whole page to conceal cards or focus indicators. Keep an intentional horizontal carousel distinct from accidental overflow.
Common mistakes
- Changing the entire page before identifying the responsible element.
- Wrap alone cannot fix a child that is wider than its container. Avoid setting overflow hidden on the whole page to conceal cards or focus indicators. Keep an intentional horizontal carousel distinct from accidental overflow.
- Checking only one preset preview instead of the published page.
In practice
A worked example
For example: Three service cards use desktop widths and push the page sideways. Switch the mobile parent to a vertical layout, allow its children to fit the available width, and verify that longer service names do not reintroduce overflow. This is a worked scenario, not a client case study.
Measure the change
Success signals to watch
- The original layout problem no longer appears at the failing width.
- Important text, links, and actions remain accessible across views.
- The same visitor task works on the published page after the change.
Further reading
Authoritative references
Next step
See what your visitors experience on mobile.
Run a free mobile-friendly test for a practical first look, or request a custom estimate if the site needs deeper responsive work.
Frequently asked questions
Will this change my website automatically?+
No. This guide describes changes for you or your website team to make. Mobilify It reads public pages and offers a custom redesign estimate; it does not access your platform editor.
Why should I check the published page?+
The Webflow editor preview is useful, but the live page may include different assets, cache state, embeds, and interaction behavior. Confirm the exact affected URL after publication.