Bolt mobile

Bottom Navigation Bar Overlapping Page Content in Bolt App

The fixed bottom navigation bar in your Bolt.new app covers the last items on every page. Users cannot see or tap buttons, form submit actions, and the last few items in lists are permanently hidden behind the nav bar. Scrolling to the bottom doesn't help because the nav bar moves with the viewport.

This is especially problematic on pages with action buttons at the bottom (checkout, submit, save), infinite scroll lists, and chat interfaces where the input field is at the bottom. Users literally cannot complete key actions because the navigation bar is covering them.

The problem gets worse on iPhones with the home indicator bar (iPhone X and later), where the safe area inset adds additional space that pushes the nav bar higher but doesn't account for the content behind it.

Error Messages You Might See

No error messages - this is a layout/UX issue Lighthouse: Tap targets are too close together Content is clipped by fixed positioned element
No error messages - this is a layout/UX issueLighthouse: Tap targets are too close togetherContent is clipped by fixed positioned element

Common Causes

  • Fixed bottom nav without content padding — The nav bar uses position: fixed but the page content doesn't have matching bottom padding to account for the nav height
  • No safe area inset handling — On notched iPhones, the env(safe-area-inset-bottom) is not applied, causing the nav to overlap the home indicator area
  • Dynamic content height changes — Content loads after the initial layout calculation, pushing elements behind the nav bar
  • Z-index conflicts — The bottom nav has a lower z-index than some page elements, causing inconsistent overlap behavior
  • Virtual keyboard pushing nav up — When the keyboard opens on mobile, the fixed bottom nav moves up and covers form inputs

How to Fix It

  1. Add bottom padding to main content — Add padding-bottom equal to your nav height plus safe area: <main className="pb-20"> for a nav bar that is h-16 (64px) with some buffer
  2. Handle safe area insets — Add env(safe-area-inset-bottom) to your nav: style={{ paddingBottom: 'env(safe-area-inset-bottom)' }} and add the viewport-fit=cover meta tag
  3. Hide nav when keyboard is open — Detect keyboard visibility and hide the bottom nav: use visualViewport.resize event to detect keyboard appearance
  4. Use a spacer element — Add an empty div with the same height as the nav bar at the end of your content: <div className="h-16" aria-hidden="true" />
  5. Set proper z-index — Give the bottom nav z-50 and ensure no other elements exceed it: <nav className="fixed bottom-0 inset-x-0 z-50 bg-white">
  6. Add viewport-fit meta tag — Update your viewport meta: <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />

Real developers can help you.

Luca Liberati Luca Liberati I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture Stanislav Prigodich Stanislav Prigodich 15+ years building iOS and web apps at startups and enterprise companies. I want to use that experience to help builders ship real products - when something breaks, I'm here to fix it. Costea Adrian Costea Adrian Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system. PawelPloszaj PawelPloszaj I'm fronted developer with 10+ years of experience with big projects. I have small backend background too Rudra Bhikadiya Rudra Bhikadiya I build and fix web apps across Next.js, Node.js, and DBs. Comfortable jumping into messy code, broken APIs, and mysterious bugs. If your project works in theory but not in reality, I help close that gap. Nam Tran Nam Tran 10 years as fullstack developer Daniel Vázquez Daniel Vázquez Software Engineer with over 10 years of experience on Startups, Government, big tech industry & consulting. Matthew Jordan Matthew Jordan I've been working at a large software company named Kainos for 2 years, and mainly specialise in Platform Engineering. I regularly enjoy working on software products outside of work, and I'm a huge fan of game development using Unity. I personally enjoy Python & C# in my spare time, but I also specialise in multiple different platform-related technologies from my day job. Pratik Pratik SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure BurnHavoc BurnHavoc Been around fixing other peoples code for 20 years.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

How do I calculate the right bottom padding for my content?

Measure your bottom nav height (usually 64px or h-16 in Tailwind) and add 16-20px buffer. In Tailwind, use pb-20 (80px) for a h-16 nav. On iOS, also add env(safe-area-inset-bottom) using the viewport-fit=cover meta tag.

Should I hide the bottom nav when the keyboard opens?

Yes, on mobile the keyboard pushes fixed bottom elements up, covering input fields. Detect keyboard visibility using the visualViewport API and hide or reposition the nav: window.visualViewport.addEventListener('resize', () => setKeyboardOpen(visualViewport.height < window.innerHeight * 0.75))

Related Bolt Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help