Interaction & UX

Navbar Breakpoint

Switch to the burger menu earlier — using exactly the tablet styling already in your project.

v1.2.13,5 kB gzipfree

View live demoGet the cloneableTutorial video
On this page

Add the script

Head code · inside <head>
<!-- FlowPowerUser · Navbar Breakpoint -->
<script defer src="https://cdn.jsdelivr.net/npm/@flowpoweruser/attributes@1/navbar-breakpoint.js"></script>

Once per project is enough, even if you use the solution on several pages: Project Settings → Custom Code → Head Code.

The script loads alongside the page without holding up rendering; it runs once the page is in place and does nothing while no fpu attribute is there.

Set the attribute

The attribute belongs on the native Webflow navbar component itself — not the container inside it, not the menu.

In the Navigator that is the element labelled “Navbar”. If it lands next to it, the nearest navbar is looked up; I would not rely on that.

Navbar component

Turns the solution on for this navbar.

Navbar component

Width in pixels up to which the burger menu is active.

In the Navigator
Navbar              fpu-navbar-element="navbar"
                    fpu-navbar-breakpoint="1100"
├─ Container
│  ├─ Brand
│  ├─ Nav Menu
│  │  ├─ Nav Link
│  │  └─ Nav Link
│  └─ Menu Button

Check

Publish the page and slowly narrow the browser window.

The switch has to happen at your value, not at 991. And it has to look the way it does on tablet — same background, same spacing, same font sizes. If it looks different, that styling is missing at the tablet breakpoint too.

Optional

Take the styling from a different breakpointDefault: tablet

In almost every Webflow project the navbar switches from tablet onwards — that is why it is the default and you need not set anything.

If your navbar is configured differently in the Designer, name the source here.

On the navbar

How far down the styling is taken from.

Default: tablet
On the navbar

Writes one line to the browser console: which source, which target value, and how many rules were carried over.

Default: false
The principle · Why Navbar Breakpoint
The principle · Why Navbar Breakpoint

Wide menus run out of room earlier. With six or seven links up there it already gets tight at 1100 pixels — but Webflow does not switch until 991. This solution closes that gap without you building the mobile menu a second time.

3fixed points in Webflow
pxany value you want
  1. NavbarThe attribute marks the native Webflow navbar. Everything inside belongs to it, nested to any depth.
  2. Tablet stylingThe project CSS is checked for the rules that apply to exactly those elements at tablet size.
  3. Pulled upThose same rules now apply from your pixel value onwards — limited to this navbar.
Additional features
  • Several navbars on one pageEvery marked navbar gets its own point and its own source. The rules carried over stay strictly with the navbar they belong to.
  • Upwards onlyThe value must be above the breakpoint the styling comes from. If you want the burger menu later rather than earlier, set that on the navbar itself in the Designer — no attribute needed.
  • What does not come alongThe project CSS is read when the page loads. Styling from third-party sources the browser is not allowed to read for security reasons stays out — Webflow's own CSS is not affected by this.

Access currently by invitation only