Code and Elementor 6 min read
7 reasons your Elementor layout breaks on mobile (and how to fix each one)
Squashed columns, sideways scrolling and giant headings on phones usually come from seven fixable causes. Here is how to spot and fix each one.
By Shaz, UK web designer
Most Elementor mobile problems come from one of seven causes: fixed pixel widths, spacing set only for desktop, oversized headings, rows that never stack, absolute positioning or negative margins, a single element wider than the screen, and custom CSS or caching overriding your responsive settings. The good news is that each one has a straightforward fix inside Elementor's responsive mode. Below, I go through how to spot each problem and exactly what to change.
First, understand how Elementor's responsive settings inherit
Elementor uses a desktop-first approach. A value you set on desktop carries down to tablet and mobile unless you override it on those devices. Controls that can differ by device show a small screen icon next to their label. Click it (or use the device switcher at the bottom of the editor panel) to change the value for that device only.
This explains a lot of confusion: if you set 80px of padding on desktop and never touch mobile, your phone visitors get 80px of padding too. Keep this in mind for every fix below.
1. Fixed pixel widths
Symptom: a box, image or container is cut off on the right, or the whole page scrolls sideways.
Cause: a width set in px, for example a container at 1100px or an image at 600px. A phone screen is usually somewhere around 360 to 430 CSS pixels wide, so anything fixed wider than that will overflow.
Fix:
- Select the element and find its Width setting.
- Change the unit from
pxto%or leave the width on its default so it fills its parent. - If you need a cap on large screens, use Max Width in
pxrather than Width. A max width lets the element shrink on small screens but stops it growing too wide on desktop.
2. Padding and margins set only for desktop
Symptom: content is squashed into a narrow strip in the middle of the phone screen, or there are huge gaps between sections.
Cause: generous desktop spacing inheriting down to mobile, often on several nested containers so it adds up.
Fix: switch to mobile view, then click through each container from the outside in. Reduce side padding to something modest, such as 16px to 20px, and cut vertical padding roughly in half. Check the Navigator panel to find nested containers that each add their own padding. Setting sensible default container padding in Site Settings under Layout saves you doing this on every page.
3. Headings and text that are too big
Symptom: a single word wraps onto its own line, long words break mid-word or poke out of the screen, or the hero heading fills the whole first screen.
Cause: a 64px or 80px desktop heading size inherited by mobile.
Fix:
- Set heading sizes in the Global Fonts section of Site Settings, with separate tablet and mobile values. Then every heading using that global style is fixed at once.
- For one-off headings, open Typography, switch to mobile, and set a smaller size.
- Reduce line height and letter spacing on mobile too, as wide letter spacing makes long words overflow.
- If your version of Elementor offers a custom unit, you can type a CSS
clamp()value so the size scales smoothly between a minimum and maximum. Check it on a real phone afterwards.
4. Rows that do not stack
Symptom: three columns sit side by side on a phone, each one tiny and unreadable.
Cause: with Flexbox containers, a container set to Direction: Row stays a row on mobile unless you change it. Inner containers with a fixed percentage width (for example 33%) also stay at that width.
Fix:
- Select the parent container and switch to mobile view.
- Set Direction to Column (the downward arrow).
- Select each child container and set its mobile width to 100%.
- If you want items to wrap rather than stack, for example a row of logos, set Wrap to Wrap and give the children a mobile width such as 50%.
- Check the order. If the image should appear above the text on mobile, use the Order setting under the child's Advanced tab, or the Reverse option on the parent's direction.
5. Absolute positioning and negative margins
Symptom: a badge, shape or image floats over text on mobile, or overlapping sections cover each other.
Cause: Position: Absolute (under Advanced) places an element relative to its parent using offsets. Those offsets were chosen for a desktop layout. Negative margins used to create overlaps behave the same way.
Fix: switch to mobile view and either reset the offsets for mobile, set Position back to Default on mobile, or hide the decorative element on mobile using Responsive settings under Advanced. For negative margins, set a mobile margin of 0. Decorative overlaps rarely add much on a small screen, so removing them is often the cleanest answer.
6. One element wider than the screen
Symptom: the page wobbles or scrolls sideways, and there is a white strip down the right-hand edge, but nothing obviously looks too wide.
Cause: one element breaking out of the layout. Common culprits are embedded iframes such as maps or videos with fixed dimensions, tables, long URLs or email addresses, carousels, entrance animations that slide in from the side, and section dividers or shapes.
Fix: find the element first. Open your browser's developer tools, switch to a phone viewport, and paste this into the Console:
document.querySelectorAll('body *').forEach(function (el) {
if (el.getBoundingClientRect().right > document.documentElement.clientWidth) {
console.log(el);
}
});It lists every element whose right edge goes past the screen. Hover over the results to highlight them. Then fix the root cause: set iframes to 100% width, wrap tables in a container that scrolls horizontally, switch off side-entering animations on mobile, or break long text with the CSS below. It goes in the widget's Custom CSS box (an Elementor Pro feature), where selector stands for the current widget.
selector .elementor-widget-container {
overflow-wrap: anywhere;
}You will see people recommend adding overflow-x: hidden to the body. It hides the symptom but can break sticky headers and hides content that is genuinely off screen. Use it only after you have found and fixed the real cause, if at all.
7. Custom CSS or caching overriding your changes
Symptom: you change a mobile setting, it looks right in the editor, but the live site does not change.
Cause: either custom CSS elsewhere is winning, or an old version of the CSS file is being served.
Fix:
- Check for custom CSS in the widget's Advanced tab, the page settings, Site Settings, the theme Customizer and your child theme. Look for
!importantrules or media queries with different breakpoints from Elementor's. - Use the Regenerate CSS option in Elementor's Tools screen so Elementor rebuilds its stylesheets.
- Clear your caching plugin, any server cache and your CDN.
- Test in a private browser window on the actual phone.
A quick mobile check routine
In my client work, I run through this before handing over any Elementor page:
- Preview in Elementor's mobile view, then in browser developer tools at several widths, not just one.
- Scroll sideways on a real phone. If anything moves, something is overflowing.
- Check every container's Direction and Width on mobile.
- Check heading sizes and spacing on mobile.
- Tap every button and menu item to make sure tap targets are a comfortable size.
- Rotate the phone to landscape and check again.
Elementor's editor preview is a good guide but not a perfect copy of a real device, so always finish on a real phone. If you want to understand the HTML and CSS behind these settings, so you can fix problems faster, the HTML and CSS for Elementor course goes into this in detail.
Questions people ask
Why does my Elementor page look fine in the editor but broken on my phone?
The editor preview approximates a phone but is not identical. Caching, custom CSS outside Elementor, browser differences and the exact screen width can all change what you see. Clear caches, regenerate Elementor's CSS and always test on a real device.
Can I change Elementor's mobile and tablet breakpoints?
Yes. Breakpoints are set in Site Settings under Layout, and you can enable additional ones such as a larger mobile or laptop size. Change them early in a project, as adjusting breakpoints later can alter layouts you have already checked.
Should I build separate desktop and mobile sections and hide one on each device?
It is best avoided. Hidden sections still load in the page HTML, which adds weight and duplicates content. Adjust the responsive settings of one layout wherever you can and only hide small decorative elements.