Netlify Makes New Projects Private by Default for Credit Plans.

A deployment no longer automatically means publication on Netlify. The hosting platform has changed its default visibility so new projects can remain inaccessible to the public through their first build, preview, and production deployment.

The change addresses a growing mismatch between how deployment platforms were designed and how teams now build software. Developers increasingly deploy prototypes, internal tools, unfinished client projects, and agent-generated applications that are not ready for a public URL. Netlify previously treated every new deployment as public unless the user took additional steps to restrict it.

According to Netlify’s official announcement, new teams using its credit-based plans now receive private projects by default. Existing teams can enable the same behavior through their team settings.

Once the setting is enabled, every new project starts private regardless of how it is created. The policy covers projects launched through Git imports, Netlify Drop, the Netlify CLI, Agent Runners, the Deploy to Netlify button, and Netlify’s API.

Builds and Deploy Previews continue to work normally. The difference is at the access layer: team members and invited collaborators must sign in with Netlify to open the project. Authorized viewers see a banner indicating that the project is private, while other visitors receive a Netlify access page and can request permission from the project owner.

That model avoids the need to create and distribute a shared password. It also reduces the risk of a preview URL being forwarded beyond its intended audience or indexed before launch.

The practical implications vary by plan and workflow:

• Free and Personal users can keep portfolios, experiments, or early products private until launch, including projects that are never intended for public access.
• Pro teams can review client work privately and operate internal applications limited to invited members.
• Development teams can keep both Deploy Previews and the main production site restricted while a product moves through testing and approval.

This is particularly relevant for AI-assisted development. Coding agents can move from repository changes to live deployments quickly, which makes visibility defaults more consequential. Netlify has been expanding its agent-focused infrastructure, including changes to Netlify Functions for agent workflows and an open source framework for testing coding agents. A private-first deployment model adds a guardrail when those automated systems generate or modify applications.

The previous Netlify workflow reflected an earlier era of web development, when deploying a project was often the final step before sharing it. Today, deployment is frequently part of the development loop. A builder may create dozens of previews before deciding that an application is ready for customers, a client, or search engines.

Netlify’s update separates those two events. Teams can still use hosted URLs to collaborate and review work, but making a project public becomes a deliberate action rather than a side effect of deployment.

That distinction should be useful to small businesses handling client materials, unreleased pricing, internal dashboards, or integrations containing test data. Private-by-default access is not a substitute for application-level authentication or proper secrets management, but it can prevent accidental exposure during development.

The setting became available on July 28, 2026. It applies automatically to new teams on Free, Personal, and Pro credit-based plans; existing teams must turn it on in team settings. Netlify has not indicated that previously public projects will be converted automatically, so teams should review the visibility of existing deployments separately.

What does private by default mean on Netlify?

It means a new Netlify project is restricted from public access when it is created. Builds, deployments, and previews still run normally, but only signed-in team members and invited collaborators can view them until the owner makes the project public.

Which Netlify plans support private projects by default?

Netlify says the setting is available to teams on its Free, Personal, and Pro credit-based plans. New teams receive the behavior by default, while existing teams can enable it from team settings.

Does Netlify make existing public projects private automatically?

The announcement only specifies the default for newly created projects and does not say existing public projects will be changed automatically. Existing teams can enable private-by-default behavior for future projects, but should review current project visibility independently.