How to build a sticky navigation bar in Framer
A step-by-step guide to a sticky Framer nav that stays readable, works on phones and links cleanly to sections.

The navigation bar is the one component every visitor touches on every page of your site. On a long landing page it also carries a lot of weight: it is how people jump back to pricing, find the contact button and understand where they are. When the bar scrolls away with the hero, all of that disappears at the exact moment someone decides they are interested.
A sticky navigation bar fixes that, but it is easy to get wrong. Bars that are too tall eat the screen on phones, transparent bars become unreadable over busy sections, and mobile menus break the moment you change a breakpoint. This guide walks you through building a sticky nav in Framer that stays out of the way, reads well on every background and works from desktop down to a small phone.
Decide what the bar has to do first
Before you open the layer panel, write down what the navigation actually needs to hold. Most marketing sites and portfolios only need four things in the bar itself:
- Your logo or wordmark, linking back to the home page.
- Three to five page or section links. If you have more, group them or move some to the footer.
- One primary action, such as "Book a call" or "Get the template".
- A menu toggle for tablet and phone breakpoints.
Everything else, like social icons, language switchers or a secondary button, competes with that primary action. A sticky bar is on screen the whole time, so every extra item is something people see on every scroll. Keep it short.
Build the bar as a component with a stack
Create a frame, add a horizontal stack inside it and set the distribution to space between. Put the logo on the left, the links in their own nested stack in the middle and the button on the right. Set the outer frame width to fill and give it a fixed height. Around 64px works well on desktop and 56px on phones.
Now turn the whole thing into a component. This matters for two reasons. First, you only maintain one nav for the entire site, so a new link or a renamed button updates every page at once. Second, components give you variants, which you will need for the mobile menu and the scrolled state.
Inside the component, constrain the content to a max width that matches your page layout, for example 1200px, and centre it. The background can still run edge to edge while the links line up with the content below.
Make it stick with sticky positioning
Place an instance of the nav component at the top of your page, then open the position settings in the right panel and choose Sticky. Set the top offset to 0. The bar will now scroll normally until it reaches the top of the viewport and then stay there.
A few details that save debugging time:
- Put the nav directly in the page, not inside a section. A sticky element only sticks within its parent, so if the parent is the hero section, the nav will scroll away with the hero.
- Raise its z-index above the content below it, so images and cards scroll underneath rather than on top.
- Check overflow on parent frames. If a parent clips its content, sticky positioning can stop working.
Preview the page and scroll the full length on each breakpoint before you move on.
Handle the scrolled state
Many sites start with a transparent nav over the hero and switch to a solid background once you scroll. Framer supports this with scroll variants: you create a second variant of the nav, for example "Scrolled", and set the component to switch to it after the page scrolls a set distance or past a section.
Use the scrolled variant for small, useful changes:
- A solid or slightly translucent background with a background blur, so text stays readable over photos.
- A thin bottom border or a soft shadow to separate it from the content.
- A slightly shorter height, for example from 72px to 60px.
Keep the logo and links in exactly the same positions in both variants. If elements jump around when the state changes, the bar feels unstable. Use a short transition of around 0.2 to 0.3 seconds so the change reads as a response, not as an animation people have to wait for.
Test the transparent state over your busiest hero image. If you have to squint to read the links, give the default variant a subtle background too.
Build a mobile menu that people can use
On tablet and phone breakpoints, swap the link stack for a menu button. Create two more variants: "Phone closed" and "Phone open". In the open variant, show a full-width panel below the bar with the links stacked vertically and the primary button at the bottom.
Add a tap interaction on the menu button that changes the variant from closed to open, and another on the close button that changes it back. Then check these points:
- Tap targets should be at least 44px tall, so give each link generous vertical padding rather than just bigger text.
- Section links should close the menu. If a link scrolls to a section on the same page, also set its tap interaction to switch back to the closed variant, or the panel will stay open over the content.
- The open panel needs a solid background. Translucent menus over page content are hard to read on a small screen.
- Keep the button visible. Your primary action should be reachable without scrolling the menu.
Link to sections and show where people are
On a one-page site, the nav usually links to sections rather than pages. Give each target section a clear name, then link to it from the nav so Framer scrolls to it smoothly. Because the bar is sticky, the section heading can end up hidden behind it. Add top padding to your sections, or a scroll offset if you are linking to them, roughly equal to the nav height.
On multi-page sites, style the link for the current page differently, for example in full contrast while the others are muted. It is a small cue, but it answers "where am I?" without the visitor having to think about it.
Check performance and accessibility
A sticky bar is rendered on every frame of scrolling, so keep it light. Avoid heavy background videos, large blur radii on big areas or complex effects inside it. Then run a quick accessibility pass:
- Text and icons need enough contrast against both the default and scrolled backgrounds.
- Icon-only buttons, such as the menu toggle, should have a clear label for screen readers.
- Use keyboard navigation in the published preview and make sure you can tab through every link in a sensible order.
- On phones, the bar should take up well under a tenth of the screen height.
Conclusion
A good sticky nav is short, readable on every background and identical in behaviour across pages. Build it once as a component, stick it directly to the page, use variants for the scrolled and mobile states and test it on real content at every breakpoint. Spend an hour on it now and every page you add later gets a navigation that simply works.


