Plugin how-tos · Info
Avada Theme Responsive Settings Explained: What Each Option Does

Short answer
Avada's responsive settings live under Avada Options in the Responsive panel, plus per-element controls in the Avada Builder. They decide when columns stack, how headings shrink on phones and which elements show on small, medium or large screens.
Key takeaways
- Open Avada > Options > Responsive for the global settings.
- Leave Responsive Design switched on for almost every site.
- Breakpoints set the widths where layouts change.
- Typography sensitivity controls how much headings shrink.
- Element Visibility hides items per screen size but may still load them.
- Clear all caches after saving changes.
What are Avada's responsive settings?
Avada's responsive settings are the global options and per-element controls that decide how your layout, typography and visibility change on phones, tablets and desktops.
Most of them live in one place: Avada > Options > Responsive in the WordPress dashboard. That panel sets site-wide rules, such as whether responsive mode is on and at what screen width columns start to stack.
A second layer sits inside the Avada Builder. Each container, column and element has its own visibility and sizing options, and many of them can be set separately for small, medium and large screens.
Avada's own Responsive Options documentation lists every field. Option names shift a little between Avada versions, so treat the labels below as a guide and match them to what you see on screen.
| Setting | Where it lives | What it controls |
|---|---|---|
| Responsive Design | Options > Responsive | Turns the mobile layout on or off |
| Grid Responsive Breakpoint | Options > Responsive | When grid columns drop to fewer per row |
| Side Header Breakpoint | Options > Responsive | When a side header becomes a top header |
| Visibility Size Options | Options > Responsive | Widths for small and medium screens |
| Typography Sensitivity | Options > Responsive | How much headings shrink on small screens |
| Minimum Font Size Factor | Options > Responsive | The floor for shrinking text |
| Element Visibility | Each element in the Builder | Hides an element on chosen screen sizes |
MDN's guide to responsive design explains the media queries that theme breakpoint settings create behind the scenes.
Where do you find the responsive options in Avada?
Go to Avada > Options in your dashboard and open the Responsive tab in the left-hand list of panels.
If you do not see an Avada menu, the theme may not be active, or the Avada Core plugin may be switched off. Check Appearance > Themes and Plugins first.
Inside the panel, each option has a short description and often a reset arrow. Changes only take effect after you click Save Changes at the top of the options screen.
Per-element settings are different. Open a page in the Avada Builder, edit a container or element, and look for the visibility checkboxes and the responsive icons next to size and spacing fields.
Avada also lets you override some global options on a single page through the Page Options box below the editor. That is useful when one landing page needs a different header or layout on mobile.
What does the Responsive Design toggle do?
The Responsive Design switch tells Avada whether to serve a mobile-friendly layout at all; leave it on for almost every site.
When it is on, Avada outputs the CSS that stacks columns, swaps in the mobile menu and resizes text below each breakpoint. When it is off, phones get the full desktop layout scaled down, which is hard to read.
Turning it off is rare today. Google uses mobile-first indexing, so the mobile version of a page is the one it mainly looks at.
If you inherited a site with responsive mode turned off, switch it on and then work through the breakpoint settings below. Expect some layouts to need small fixes afterwards.
How do the breakpoints work in Avada?
A breakpoint is the screen width, in pixels, at which Avada switches from one layout to another, such as from multi-column rows to stacked columns.
The Grid Responsive Breakpoint controls grids, like blog and portfolio layouts. Below that width, a four-column grid drops to fewer columns so cards stay readable.
The Side Header Responsive Breakpoint only matters if you use a vertical side header. Below the set width, the side header turns into a regular top header with a mobile menu.
The Visibility Size Options define what Avada means by small and medium screens. Small usually covers phones, and medium covers tablets. Everything above medium counts as large.
These visibility widths matter because they feed the per-element visibility checkboxes. If you set medium to a high number, more tablets and small laptops will be treated as tablets.
A simple approach works for most sites:
- Keep the default values first and test on real devices.
- Raise a breakpoint only if columns look cramped just above it.
- Lower it only if content stacks too early on wide tablets.
- Change one value at a time so you can see the effect.
What do the typography settings control on mobile?
Avada's responsive typography options shrink headings and large text on smaller screens so a 60px desktop title does not break across five lines on a phone.
Responsive Typography Sensitivity sets how strongly text scales down. A value of zero turns scaling off, while higher values shrink large text more as the screen narrows.
Minimum Font Size Factor sets a floor. It stops headings from shrinking below a certain multiple of your body text size, so they still look like headings.
Avada has a separate guide to responsive headings if you want to set sizes per element rather than rely on global scaling.
For body text, keep a base size of at least 16px. Small body text on phones is one of the most common readability complaints, and web.dev's guidance on legible font sizes explains why.
If you prefer full control, set the typography sensitivity low and set explicit heading sizes for each screen size in the Builder instead.
How do you hide or show elements on mobile in Avada?
Edit the container, column or element in the Avada Builder and use its Element Visibility checkboxes to choose small, medium or large screens.
Unticking Small Screen hides that element on phones. Unticking Large Screen hides it on desktops. This is handy for showing a short mobile hero and a longer desktop hero.
Hidden elements are usually still in the HTML and only hidden with CSS. That means a heavy slider hidden on mobile may still load its files, so it does not always help speed.
Use visibility sparingly. Two full copies of a section, one for mobile and one for desktop, double your editing work and can confuse search engines about which content matters.
Avada also has Responsive Option Sets for some fields, shown as small device icons next to a setting. Click the icon to set a different value, such as padding or font size, for each screen size.
How do columns and ordering behave on small screens?
On small screens Avada stacks columns in the order they appear in the Builder, and each column has settings to change its width and order on each device.
In a column's settings you can usually set a different width for medium and small screens, such as half width on tablets and full width on phones.
Column order options let you move, say, an image below its text on phones while keeping it on the left on desktop. Avada documents this in its column size and order material.
Spacing also matters. Large desktop padding often looks huge on a phone, so set smaller top and bottom padding for small screens on key containers.
If you use another page builder on other sites, the idea is the same as in our WPBakery responsive settings guide, just with different labels.
How do header and menu settings work on mobile?
Avada switches the main menu to a mobile menu below a set width, and you can control that width, the menu style and the mobile logo from the header and menu options.
In Avada 7 and later, many sites build headers with the Header Layout Builder. In that case, the mobile menu is controlled by the Menu element's own responsive settings, including the width at which it collapses.
Older sites using the classic header options control the mobile menu from the Menu and Header panels in Avada Options instead. The labels differ, so check which system your site uses before changing anything.
A mobile logo option lets you upload a smaller or simpler logo for phones. This keeps the header short and leaves more room for content above the fold.
If your menu disappears on phones, the cause is often the breakpoint or visibility settings. Our guide on how to change the header in WordPress covers header changes in more depth.
How do you preview and test responsive changes?
Use the device icons in the Avada Builder toolbar to preview small, medium and large layouts, then confirm on real phones because previews only approximate real devices.
Your browser's developer tools are a good second check. Chrome's device mode lets you resize the page and pick common phone and tablet sizes.
Clear caches after every save. Avada has its own performance and CSS compiling options, and a caching plugin or host cache can show you an old version. Our guide on how to clear cache in WordPress walks through the common caches.
Test these things on each device size:
- The header and mobile menu open and close.
- Text is readable without zooming.
- Buttons are large enough to tap.
- Images do not overflow the screen.
- Forms fit and their fields are usable.
What are the best Avada responsive settings for most sites?
For most sites, leave Responsive Design on, keep the default breakpoints, use modest typography sensitivity and adjust spacing per container rather than hiding whole sections.
Defaults exist because they fit common screen sizes. Many layout problems come from custom padding and fixed widths rather than the global breakpoints themselves.
Here is a practical order of work:
- Check that Responsive Design is on.
- Preview the home page and one post on a phone.
- Fix spacing and column widths in the Builder first.
- Adjust typography sensitivity if headings look too big.
- Only then change global breakpoints, one at a time.
Before larger changes, take a backup or use a staging copy. Our guide to setting up a staging site shows how to test safely.
For wider mobile fixes that are not Avada-specific, see how to fix WordPress mobile view.
What should you do if responsive settings seem to have no effect?
If changes do not show, the usual causes are caching, a page-level override, a child theme CSS rule or an element-level setting that wins over the global option.
Start by clearing every cache, including Avada's own compiled CSS if your version has that option under the performance settings.
Next, open the page's Page Options and check whether it overrides header or layout settings. Page settings take priority over global ones.
Then check custom CSS in the child theme or in Avada's custom CSS box. A single fixed width rule can stop columns from stacking.
Finally, disable plugins one by one on a staging copy if nothing else works. Our plugin conflict guide explains a safe way to do that.
Frequently asked questions
Where are the responsive settings in Avada?
Go to Avada, then Options, and open the Responsive panel. It holds the global switches and breakpoints. Per-element visibility and sizing options are inside the Avada Builder when you edit a container, column or element.
Should I turn off responsive design in Avada?
Almost never. Turning it off serves the full desktop layout to phones, which is hard to read and works against mobile-first indexing. Keep it on and fix individual layout problems with spacing, column widths and typography settings instead.
Why is my Avada site not changing on mobile after I save?
Caching is the most common cause. Clear your caching plugin, host cache and any CDN, then check the page's own Page Options for overrides. Custom CSS with fixed widths can also stop columns from stacking.
Does hiding an element on mobile make Avada faster?
Not always. Avada usually hides elements with CSS, so the HTML and often the images or scripts still load. For speed, remove heavy sections or use lighter alternatives rather than relying on visibility settings alone.
What is the Grid Responsive Breakpoint in Avada?
It is the screen width at which grid layouts, such as blog and portfolio grids, reduce their number of columns. Below that width, cards drop to fewer per row so text and images stay readable on smaller screens.
Sources
- Responsive Options in Avada Avada
- Responsive Design in Avada Avada
- Responsive Headings Avada
- Mobile-first indexing best practices Google Search Central
- Simulate mobile devices with device mode Chrome for Developers
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


