Learn how to install n8n on Windows with this simple step-by-step guide, covering setup, configuration, and tips for a smooth automation start.

Book a call with an Expert
Starting a new venture? Need to upgrade your web app? RapidDev builds application with your growth in mind.
The simplest and most reliable way to install n8n on Windows is to run it through Docker Desktop. Windows itself is not an officially recommended production OS for n8n, but Docker provides a clean Linux environment inside Windows, and that works very well. You install Docker Desktop, run a single docker‑run command, and n8n will be available at http://localhost:5678.
This method avoids the usual Windows pitfalls (like Node version conflicts, permission issues, or npm build errors). Docker runs n8n exactly how it runs in real production servers, so what you build locally behaves the same on deployment.
// This command starts n8n on http://localhost:5678
docker run -it --rm \
-p 5678:5678 \
-e N8N_SECURE_COOKIE=false \
n8nio/n8n
Why N8N_SECURE_COOKIE=false? On Windows localhost, https is usually not enabled. n8n’s login cookies are secure by default (they require https). Setting this env variable disables that check so you can log in locally.
After running the command, open:
http://localhost:5678
That’s it — n8n is installed and running.
This section breaks down the process in a way a junior developer or non‑tech teammate can follow with confidence.
By default, the temporary Docker container forgets everything when you stop it. In real workflows, you want your credentials and workflows to persist. You can add a volume:
// This keeps your n8n data saved on your Windows machine
docker run -it --rm \
-p 5678:5678 \
-e N8N_SECURE_COOKIE=false \
-v C:/n8n_data:/home/node/.n8n \
n8nio/n8n
Now all workflows, credentials, and settings survive restarts.
You can install n8n using Node/npm, but it’s less reliable on Windows for beginners because native build tools sometimes fail. Still, it works:
// Install n8n globally
npm install -g n8n
// Start n8n
n8n
If everything compiles successfully, n8n will again start at http://localhost:5678. But if you hit errors about Python or build tools, switch to Docker—it avoids all of that.
Even though you’re installing on Windows, remember that Windows is fine for development but not ideal for production. Real deployments usually use Linux, Docker Compose, or n8n Cloud. Still, Docker Desktop on Windows is stable and matches how n8n runs in real servers, so it’s the best development setup.
This approach gives you a consistent environment, fewer platform surprises, and a smooth path to production later.
When it comes to serving you, we sweat the little things. That’s why our work makes a big impact.