Netlify Gives Private Projects a Pre-Launch Toolbar

Netlify put a visible marker on the private-by-default setting it flipped three weeks ago: private projects now carry a pre-launch toolbar, and public ones carry a Powered by Netlify badge, according to Netlify’s project visibility documentation, updated Aug 19, 2026.

What changed

A project’s visibility setting now decides which overlay Netlify shows on it: the pre-launch toolbar while it’s private, the Powered by Netlify badge once someone flips it public (Netlify Docs). The two overlays replace what used to be a single experience regardless of stage, an access page for outsiders and nothing distinctive for the team looking at their own in-progress build. Anyone who lands on a private project without permission still gets a page explaining they don’t have access and can request it from the team; the toolbar is what team members and invited collaborators see instead, a persistent marker that the project hasn’t launched yet.

This is the interface layer on top of the visibility default Netlify introduced Jul 28, 2026: new teams on Free, Personal and Pro plans get projects private by default, with nothing reachable outside the team until someone explicitly makes it public (Netlify changelog, Jul 28, 2026). Firerun covered that default flip when it shipped (Firerun, Jul 31, 2026); this release is Netlify following through on it with a UI a team actually sees on every deploy, not just a settings toggle three clicks deep.

Why it matters

A default that only shows up in a settings panel is easy to forget exists. A toolbar on every private preview reminds the team, on every visit, that the thing they’re looking at hasn’t shipped yet, which matters more now that agent-scaffolded projects and client prototypes routinely start life private under the July default. The Powered by Netlify badge does the inverse job: it marks the moment a project crosses from draft to public, the same beat Vercel’s “Deployed on Vercel” badge marks for its own free-tier sites, turning a routine deploy into small, recurring platform branding on every project that doesn’t pay to remove it.

Firerun’s take: pairing a private default with a visible toolbar closes a gap the July change left open. Flipping a setting protects a project from accidental exposure, but it does nothing to tell the people looking at that project what state it’s actually in. The toolbar is the missing feedback loop: it turns “private by default” from a policy you have to trust into a status you can see on the page itself.

Key Takeaways

• Netlify’s project visibility setting now drives a visible overlay: a pre-launch toolbar on private projects, a Powered by Netlify badge on public ones (Netlify Docs, updated Aug 19, 2026).
• Visitors without access to a private project still see Netlify’s existing request-access page; the toolbar is what the team and invited collaborators see instead.
• The overlay pairs with the private-by-default setting Netlify shipped Jul 28, 2026 for new Free, Personal and Pro teams (Netlify changelog), which Firerun covered at launch.
• The badge mirrors the “deployed on this platform” branding pattern other deploy platforms use on their free tiers, tied here to the moment a project goes public rather than to the plan alone.