{"id":4233,"date":"2026-11-04T05:38:00","date_gmt":"2026-11-04T05:38:00","guid":{"rendered":"https:\/\/www.ucartz.com\/blog\/node-js-vs-express\/"},"modified":"2026-11-09T22:04:59","modified_gmt":"2026-11-09T22:04:59","slug":"node-js-vs-express","status":"publish","type":"post","link":"https:\/\/www.ucartz.com\/blog\/node-js-vs-express\/","title":{"rendered":"Node.js vs Express: What’s the Difference and Do You Need Both?"},"content":{"rendered":"\n

Node.js and Express are not alternatives. Node.js is the runtime: the program that runs JavaScript on a server instead of in a browser. Express is a small web framework, installed with npm install express<\/code>, that runs on top of Node.js and gives you routing, middleware and helpers for requests and responses. Every Express app is a Node.js app. You can build a web server with Node.js alone, but most people add Express (or a similar framework) once an app has more than a handful of routes.<\/p>\n\n\n\n

\"Terminal
Node.js 20 on Debian 13, the current Express version from npm, and a plain Node.js HTTP server answering 200<\/figcaption><\/figure>\n\n\n\n

Node.js vs Express at a glance<\/h2>\n\n\n\n
<\/th>Node.js<\/th>Express<\/th><\/tr><\/thead>
What it is<\/td>A JavaScript runtime environment<\/td>A web framework for Node.js<\/td><\/tr>
How you get it<\/td>Install it on the server (installer, package manager or nvm)<\/td>npm install express<\/code> inside your project<\/td><\/tr>
What it gives you<\/td>The V8 engine, a standard library (files, network, HTTP, crypto) and npm<\/td>Routing, middleware, body parsing, static files, error handling<\/td><\/tr>
Can it run on its own?<\/td>Yes<\/td>No, it needs Node.js<\/td><\/tr>
Used for<\/td>Web servers, command-line tools, scripts, build tools, workers<\/td>Web applications and APIs<\/td><\/tr>
Version we tested<\/td>24.21.0 (LTS)<\/td>5.2.1<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The Node.js project describes Node.js as “an open-source and cross-platform JavaScript runtime environment” that runs the V8 engine from Google Chrome outside the browser, in a single process with non-blocking I\/O (see Introduction to Node.js<\/a>). The Express repository<\/a> describes Express as a “fast, unopinionated, minimalist web framework for Node.js”.<\/p>\n\n\n\n

The same small API, with and without Express<\/h2>\n\n\n\n

The easiest way to see the difference is to build one endpoint twice. We ran both versions in a node:24-alpine<\/code> Docker container.<\/p>\n\n\n\n

Plain Node.js<\/h3>\n\n\n\n
const http = require('node:http');\n\nconst server = http.createServer((req, res) => {\n  if (req.method === 'GET' && req.url === '\/api\/hello') {\n    res.writeHead(200, { 'Content-Type': 'application\/json' });\n    res.end(JSON.stringify({ message: 'Hello from plain Node.js' }));\n  } else {\n    res.writeHead(404, { 'Content-Type': 'text\/plain' });\n    res.end('Not found');\n  }\n});\n\nserver.listen(3000, () => console.log('Listening on port 3000'));<\/code><\/pre>\n\n\n\n
It works, and it needs no packages at all. But you check the method and URL yourself, set headers yourself and turn objects into JSON yourself. Add route parameters, form data, file uploads and error pages, and that if<\/code> block grows quickly.<\/p>\n\n\n\n
Express<\/h3>\n\n\n\n
const express = require('express');\nconst app = express();\nconst port = process.env.PORT || 3000;\n\napp.use(express.json());\napp.use(express.static('public'));\n\napp.get('\/api\/hello', (req, res) => {\n  res.json({ message: 'Hello from Express' });\n});\n\napp.get('\/api\/users\/:id', (req, res) => {\n  res.json({ id: req.params.id });\n});\n\napp.post('\/api\/echo', (req, res) => {\n  res.status(201).json(req.body);\n});\n\napp.get('\/api\/fail', async (req, res) => {\n  throw new Error('Something broke');\n});\n\napp.use((err, req, res, next) => {\n  console.error(err.message);\n  res.status(500).json({ error: 'Internal server error' });\n});\n\napp.listen(port, () => console.log(`Listening on port ${port}`));<\/code><\/pre>\n\n\n\n
What we got back:<\/p>\n\n\n\n
GET  \/api\/hello     200  {\"message\":\"Hello from Express\"}\nGET  \/api\/users\/42  200  {\"id\":\"42\"}\nPOST \/api\/echo      201  {\"name\":\"test\"}\nGET  \/api\/fail      500  {\"error\":\"Internal server error\"}\nGET  \/              200  <h1>Static file<\/h1>   (public\/index.html)\nGET  \/nothing       404  (Express's default \"not found\" page)<\/code><\/pre>\n\n\n\n
What Express adds on top of Node.js<\/h2>\n\n\n\n