Is Netlify Identity Deprecated? 2026 Status, Plus Full Setup Guide
On this page
- Is Netlify Identity deprecated in 2026?
- What is Netlify Identity
- Requirements
- Enabling Netlify Identity
- Enabling Git Gateway (optional but common)
- Adding the Netlify Identity widget
- Opening the login modal
- Accessing the current user
- Protecting pages with redirects
- Using Identity with Netlify Functions
- Managing users and roles
- Custom authentication UIs
- When Netlify Identity is a good fit
- Final thoughts
Netlify Identity makes it possible to add authentication to a static site without running your own backend. It handles user management, login flows, and secure token handling, while staying tightly integrated with the rest of the Netlify platform.
Is Netlify Identity deprecated in 2026?#
No. This rumor comes up constantly, so let's settle it: as of July 2026, the Netlify docs list Identity as a supported service, available on every credit-based plan. Email/password signup and external provider login are on the free tier, with custom email templates and audit logs on Pro and Enterprise.
The confusion has a real source: Git Gateway, a related service that let Identity users edit Git-backed content (the classic Netlify CMS / Decap CMS setup), is deprecated. If your interest in Identity is powering a CMS login through Git Gateway, that workflow is on borrowed time and you should look at your CMS's other auth backends. For gating pages, members-only areas, and authenticated Functions (everything in this guide), Identity remains a working, supported option.
(Status verified against docs.netlify.com on July 28, 2026.)
The rest of this post sets up Netlify Identity from scratch and wires it into a typical static site.
What is Netlify Identity#
Netlify Identity is a managed authentication service built on top of GoTrue. It provides:
- Email and password authentication
- OAuth providers like GitHub and Google
- User roles and metadata
- JWT-based authentication tokens
- Built-in UI widgets or custom implementations
Because Identity is built into Netlify, it works especially well with Netlify Functions for gated content, admin areas, and APIs.
Requirements#
Before getting started, make sure you have:
- A Netlify account
- A site deployed on Netlify
- Basic familiarity with HTML and JavaScript
- Netlify CLI installed (recommended for local testing)
Enabling Netlify Identity#
Start by enabling Identity for your site.
- Open your site in the Netlify dashboard
- Go to Site configuration
- Select Identity from the sidebar
- Click Enable Identity
Once enabled, Netlify automatically provisions the Identity service for your site.
Enabling Git Gateway (optional but common)#
If you plan to use Identity with a CMS like Netlify CMS or Decap CMS, you should also enable Git Gateway.
- In the Identity settings, find Services
- Enable Git Gateway
- Choose a provider (GitHub is the most common)
This allows authenticated users to push content changes back to your repository.
Adding the Netlify Identity widget#
The fastest way to get authentication working is by using the official Identity widget.
Add the script to your site, typically in the <head>:
<script src="https://identity.netlify.com/v1/netlify-identity-widget.js"></script>Then initialize it in your JavaScript:
if (window.netlifyIdentity) {
window.netlifyIdentity.on("init", user => {
if (!user) {
window.netlifyIdentity.on("login", () => {
document.location.href = "/dashboard";
});
}
});
}This gives you a fully functional login and signup modal with no custom UI work required.
Opening the login modal#
To let users sign in, add a button anywhere on your site:
<button onclick="netlifyIdentity.open()">Log in</button>You can also open specific views:
netlifyIdentity.open("signup")
netlifyIdentity.open("login")Accessing the current user#
Once logged in, you can access the current user object:
const user = netlifyIdentity.currentUser()
if (user) {
console.log(user.email)
}The user object includes metadata, roles, and JWT tokens.
Protecting pages with redirects#
A common pattern is protecting pages using Netlify redirects.
Create a _redirects file or add this to netlify.toml:
[[redirects]]
from = "/dashboard"
to = "/login"
status = 302
conditions = { Role = ["authenticated"] }This ensures only authenticated users can access the dashboard.
Using Identity with Netlify Functions#
Netlify Functions can validate Identity tokens automatically.
Example function:
import type { Handler } from "@netlify/functions"
export const handler: Handler = async (event) => {
const user = event.context.clientContext?.user
if (!user) {
return {
statusCode: 401,
body: "Unauthorized"
}
}
return {
statusCode: 200,
body: JSON.stringify({
message: "Hello authenticated user",
email: user.email
})
}
}This makes it easy to build authenticated APIs without managing sessions yourself.
Managing users and roles#
In the Netlify dashboard, you can:
- View all users
- Assign roles
- Disable or delete accounts
- Invite users manually
Roles are especially useful for admin-only areas and CMS access.
Custom authentication UIs#
If you don’t want to use the widget, you can build a fully custom UI using the GoTrue API directly. This gives you complete control over the UX while still using Netlify Identity under the hood.
This approach is more advanced but works well for production apps with custom design requirements.
When Netlify Identity is a good fit#
Netlify Identity works best when:
- You are building a static or JAMstack site
- You want authentication without maintaining a backend
- You need simple role-based access control
- You are already using Netlify Functions
For very complex auth requirements or enterprise SSO, a dedicated auth provider may still be a better choice.
Final thoughts#
If you are already deploying on Netlify, it is often the fastest path from “public site” to “authenticated app.”

Written by
Developer Advocate at RevenueCat and creator of Netli.fyi. Building on Netlify since 2019 and writing from hands-on experience deploying dozens of production sites.
More about the author