Why 404 Not Found handler in Express? - Purpose & Use Cases

The Big Idea

What if your website could gently catch every wrong turn visitors take?

The Scenario

Imagine you build a website with many pages, but when someone types a wrong address, nothing happens or the server crashes.

The Problem

Without a proper 404 handler, users get confused or see ugly errors. Manually checking every URL is slow and messy.

The Solution

A 404 Not Found handler in Express catches all unknown requests and shows a friendly message automatically.

Before vs After

✗ Before

app.get('/home', (req, res) => { res.send('Home'); }); // no catch for wrong URLs

✓ After

app.use((req, res) => { res.status(404).send('Page not found'); });

What It Enables

This lets your app gracefully handle missing pages and guide users back on track.

Real Life Example

When you mistype a URL on a shopping site, a 404 page helps you find your way instead of showing a blank screen.

Key Takeaways

Manual URL checks are hard and error-prone.

Express 404 handler catches all unknown routes automatically.

Users get clear feedback and better experience.