A fullscreen hero section in Elementor may look correct on desktop but start jumping or become cropped on smartphones. The cause is usually not Elementor itself, but the way mobile browsers change the visible viewport when the address bar appears or disappears.
For mobile fullscreen sections, it is usually better to use 100svh instead of relying only on 100vh. This unit defines the minimum stable viewport height and does not change every time the browser shows or hides its interface elements. Below, we will explain how to add this rule in Elementor, when to choose dvh, and which issues to check after configuration.
Why 100vh Causes Problems on Mobile
The vh unit represents one percent of the viewport height. Therefore, 100vh is intended to equal the height of the browser's visible area. On mobile devices, however, this area is unstable: the browser's address bar and bottom toolbar may appear or disappear while the user scrolls.
As a result, the height of the hero section may be recalculated while the user is interacting with the site. Visually, this can appear as content jumping, a button shifting position, or the first screen suddenly becoming larger or smaller. In other cases, the block tries to occupy more space than is actually available, leaving part of the heading or button outside the screen.
The issue is especially noticeable in hero sections with background images, vertical centering, large headings, and CTA buttons. Fullscreen menus, modal windows, and popup blocks also require particular care.
- 100vh can behave inconsistently on smartphones with a dynamic address bar.
- The viewport height changes not only when the screen rotates, but also while the user scrolls.
- For sections containing content, use min-height rather than a fixed height so text is not cropped.
What Are svh, dvh, and lvh?
Modern CSS provides separate units for different states of the mobile viewport. They allow you to define more precisely whether a section should be stable, dynamic, or as tall as possible.
svh means small viewport height, or the smallest stable viewport height. It is calculated based on the state in which browser interface elements occupy space on the screen. When you set min-height: 100svh, the hero should not expand when the address bar appears or disappears. This is generally the best option for a first screen where avoiding jumps is important.
dvh means dynamic viewport height. It changes along with the state of the browser interface. This can be useful when a section must always fill the currently visible area, but dvh itself may cause content to move while the user scrolls.
lvh means large viewport height, or the largest viewport height available when browser interface elements are hidden. It suits some fullscreen scenarios, but for a stable mobile hero it often creates excessive height.
- svh — stability and predictable height.
- dvh — alignment with the current visible area, but possible changes during interaction.
- lvh — the maximum height available when browser interface elements do not take up space.
How to Configure a Hero Section in Elementor
First, open the container or section responsible for the first screen. It is important to apply the rule to the outer hero container, not only to the inner text column. Otherwise, the background or section area may remain shorter than intended.
In the Custom CSS field, add a fallback using 100vh followed by the modern 100svh rule. The order of the lines matters: a browser that supports svh will use the second value, while an older browser will fall back to 100vh.
If Custom CSS is not available in your Elementor setup, you can add this rule through your theme's CSS or another method for loading custom styles. In that case, replace selector with the class or another selector for the specific hero block.
- Make sure the rule is added to the container that should occupy the entire first screen.
- Use min-height so a longer text block can expand the section.
- Check that other styles do not assign height: 100vh or a fixed height to the same block with a higher priority.
selector {
min-height: 100vh;
min-height: 100svh;
}
When Should You Use dvh Instead of svh?
Not every fullscreen block needs to be stable in the svh sense. Sometimes the goal is for the section to match the currently visible screen area precisely at all times. For example, this may apply to a short interactive menu or a special screen with no vertical content.
In this situation, you can use 100dvh. The section will expand or shrink as the address bar appears and disappears. This provides a more precise fit to the screen, but the height changes may be noticeable to the user.
For a standard hero containing a logo, heading, description, and button, the stable svh option is usually more appropriate. When the block changes height, vertically centered content also moves, which can make the first screen harder to use.
- Choose svh when avoiding jumps is the priority.
- Choose dvh when the block must continuously fill the currently visible area.
- Do not automatically use dvh for every section simply because it is called fullscreen.
selector {
min-height: 100dvh;
}
What to Check After Adding the CSS
Changes in viewport height cannot always be evaluated accurately in a browser's responsive preview on a computer. For reliable testing, open the page on a real smartphone or use developer tools as an initial check, then test it on a physical device.
Test the page in Safari on an iPhone and in Chrome on Android. Open the page at the top, scroll down, return to the top, and change the screen orientation. Check whether the heading shifts, the button disappears, or the background image becomes cropped.
Also test a longer heading, an increased system font size, and a narrow screen. The hero should not hide important content simply because less vertical space is available on a particular device.
- Safari on iOS at the top and bottom of the page.
- Chrome on Android with the address bar both visible and hidden.
- Portrait and landscape orientations.
- Short and long versions of the heading.
- Different screen widths and an increased text size.
Common Elementor Errors
The problem is most often caused not by the height unit itself, but by a combination of settings. For example, the outer container may have min-height: 100svh, while an inner container has a fixed height: 100vh. In this situation, the inner block may still extend beyond the stable height.
Another common mistake is using height instead of min-height. If the text or buttons do not fit within one screen, a fixed height may crop the content or cause elements to overlap. For a hero with an unpredictable amount of text, min-height is safer.
You should also check padding values set in percentages or viewport units. Large padding-top and padding-bottom values are added to the minimum height and can make the section taller than the screen. Even when box-sizing is enabled, large internal spacing still reduces the space available for the content.
Do not use overflow: hidden as the first solution. It may conceal the symptom while also cropping a button, shadow, dropdown menu, or part of the text.
- Check height and min-height on all parent and child containers.
- Remove duplicate rules for the mobile breakpoint.
- Reduce excessive vertical spacing on narrow screens.
- Do not crop content with overflow: hidden without a clear reason.
- After clearing the cache, check that the new CSS is actually loading.
Frequently asked questions
Do I need to stop using 100vh completely?
No. 100vh can remain as a fallback for browsers that do not support the newer viewport units. For a mobile hero, write 100vh first and 100svh second so modern browsers use the more stable unit.
Why does the example use min-height instead of height?
min-height sets a minimum height while allowing the section to grow if the text or other content does not fit on one screen. height can crop content on smaller displays.
Does 100svh work in all browsers?
Support for modern viewport units depends on the browser and its version. That is why 100vh is kept as the first rule as a fallback. Current versions of Safari and Chrome generally support svh, but the result should still be tested on real devices.
Which should I choose for a popup or fullscreen menu: svh or dvh?
If the menu should remain stable and avoid moving elements when the address bar appears, start with svh. If it must continuously match the currently visible area, you can use dvh. For menus, always test scrolling and access to the close button.
Conclusion
For most mobile hero sections in Elementor, a practical baseline is min-height: 100vh with a fallback to min-height: 100svh. This preserves compatibility and reduces the risk of jumps while the browser address bar changes.
Use 100dvh when dynamic height changes are part of the intended design. Regardless of the unit you choose, test not only how the block looks in the editor, but also how it behaves in Safari on iOS and Chrome on Android.