JWT Authentication in Express.js: Complete Guide
Express.js is the most popular Node.js web framework. It's widely used to build REST APIs that issue and verify JWT tokens for stateless authentication. This guide walks you through everything you need to implement robust JWT authentication in Express.js, from choosing the right library to writing production-ready code.
In This Guide
Recommended JWT Library for Express.js
jsonwebtoken
The recommended library for handling JWT authentication in Express.js. It provides a mature API, active maintenance, and wide community adoption — making it the go-to choice for production applications built with Express.js.
Whether you are building a small prototype or a large-scale enterprise application, jsonwebtoken gives you the tools to generate, sign, verify, and decode JWT tokens with confidence. It supports all major signing algorithms including HS256, RS256, and ES256, and integrates naturally with the Express.js ecosystem.
JWT Authentication Code Example
Below is a practical code example showing how to implement JWT authentication in Express.js using jsonwebtoken. This snippet demonstrates the core pattern you will use in most applications:
const jwt = require('jsonwebtoken');
function authMiddleware(req, res, next) {
const token = req.headers.authorization?.split(' ')[1];
if (!token) return res.status(401).json({ error: 'No token' });
try {
const decoded = jwt.verify(token, process.env.JWT_SECRET);
req.user = decoded;
next();
} catch (err) {
return res.status(403).json({ error: 'Invalid token' });
}
}
// Usage
app.get('/api/profile', authMiddleware, (req, res) => {
res.json({ user: req.user });
});This example shows the essential JWT workflow in Express.js. In production, make sure to store secrets in environment variables, use HTTPS, and implement proper error handling for token expiration and revocation.
How to Set Up JWT in Express.js
Follow these steps to get JWT authentication working in your Express.js project. Each step builds on the previous one, so we recommend following them in order:
- 1
Install: npm install jsonwebtoken
- 2
Create auth middleware to verify tokens
- 3
Generate JWT on successful login
- 4
Apply middleware to protected routes
- 5
Implement refresh token endpoint
Key Features of JWT Auth in Express.js
When you implement JWT authentication in Express.js, you gain access to several powerful capabilities that make your application more secure and scalable:
Why Use JWT Authentication in Express.js?
Express.js is widely used for building modern web applications and APIs, and JWT has become the de facto standard for stateless authentication. By combining Express.js with JWT, you get a scalable authentication system that does not require server-side session storage.
JWT tokens are self-contained, meaning they carry all the information needed to identify a user and their permissions. This makes them ideal for microservice architectures, mobile backends, and single-page applications built with Express.js. Each request includes the token, so your server can verify identity without a database lookup.
The jsonwebtoken library makes it straightforward to implement JWT in Express.js. You can generate tokens on login, verify them on each request, and handle token refresh to keep users authenticated without interruption. Combined with proper security practices — such as short expiration times, refresh token rotation, and secure storage — JWT provides a robust foundation for any authentication system.
Best Practices for JWT in Express.js
When implementing JWT authentication in Express.js, follow these best practices to keep your application secure:
- Use strong secrets: Always use a long, random secret key for signing tokens. Store it in environment variables, never in source code.
- Set short expiration times: Access tokens should expire quickly (15–30 minutes). Use refresh tokens for longer sessions.
- Validate on every request: Always verify the token signature and check expiration before granting access to protected resources.
- Use HTTPS: JWT tokens sent over plain HTTP can be intercepted. Always use HTTPS in production to protect tokens in transit.
- Handle token refresh: Implement a refresh token flow so users are not logged out when their access token expires. Rotate refresh tokens to prevent replay attacks.
- Do not store sensitive data in tokens: JWT payloads are Base64-encoded, not encrypted. Avoid putting passwords or other sensitive information in claims.
Decode & Inspect JWT Tokens Instantly
Use our free online JWT Decoder to inspect any token — view the header, payload, claims, and expiration status right in your browser. No sign-up required.
Try JWT Decoder Pro →