Test n8n locally: npm vs. Docker vs. desktop app

Anyone who wants to try n8n locally can currently choose between two officially supported paths: installation via npm or running it via Docker. A separate desktop app no longer exists; n8n has discontinued this application and instead recommends the npm route. For a quick test without a fixed setup, npm is the best choice; for a setup that should later also serve as a basis for permanent operation, Docker is the more robust choice. As of: July 2026.

npm installation: quick to test, little effort

The npm installation is the most direct way to get n8n running locally. It requires a Node.js version between 20.19 and 24.x. With the command npx n8n, you can try n8n without a permanent installation, accessible afterwards at http://localhost:5678. If you want to set up n8n permanently, install it globally with npm install n8n -g and then start it with the command n8n or n8n start. Updates are done via npm update -g n8n, a downgrade by reinstalling a specific version, optionally supplemented with n8n db:revert for database changes. By default, this variant stores credentials, workflows and past executions in an SQLite database under ~/.n8n/database.sqlite, along with the encryption key and log files in the same folder. This is sufficient for a first impression or for developing individual workflows, but for permanent operation with multiple users, this folder is not a reliable foundation.

Docker: cleaner setup, closer to production

The Docker route encapsulates n8n along with its runtime environment in a container and mounts a named volume so that data survives restarts. The basic installation documented by n8n first creates a volume (docker volume create n8n_data) and then starts the container with docker run, mounting the volume to /home/node/.n8n. Here too, n8n uses SQLite by default for credentials, executions and workflows; the data therefore remains in the same directory format as with the npm variant, just containerized and separated from the host via the volume. For more production oriented scenarios, the database can be switched to PostgreSQL via environment variables (DB_TYPE, DB_POSTGRESDB_*). n8n explicitly points out in its own documentation that self-hosting requires technical knowledge, for example in setting up and configuring servers and containers, managing resources and securing the environment. If you do not want to take on these tasks yourself, n8n points to its own cloud variant as an alternative to self-hosting.

The discontinued desktop app

n8n used to offer a desktop application that allowed n8n to be started locally without Node.js or Docker. This variant has since been discontinued, and the associated GitHub repository is archived. In the official announcement, n8n justifies the step by stating that cloud and self-hosted usage are growing strongly, while the desktop version was comparatively little used and is therefore no longer maintained. Users of existing desktop installations are referred to the npm route; existing workflows and credentials can be carried over. The source code remains publicly viewable, so independent continued maintenance by the community is at least technically possible, but official support is no longer available.

Which variant for which purpose

For a brief test of individual workflows or to get to know the interface, npx n8n is the fastest entry point, with no installation step at all. For regular local development, the global npm installation is worthwhile because workflows and credentials are retained between sessions. As soon as the environment needs to run longer, integrate multiple services, or later grow toward a production setup, Docker is the more sensible starting point, because the runtime environment and data are cleanly separated and the switch to an external database is prepared. If you are unsure how much server and container knowledge is actually available in your team, you should clarify this question before deciding, because n8n makes clear in its own documentation that self-hosting requires ongoing maintenance. With our n8n automation service, we take on this assessment for customers who want to decide for themselves whether a local test setup or a production server right away makes more sense.

Frequently asked questions about testing n8n locally

Does the n8n desktop app still exist?

No. n8n has discontinued the desktop application; the associated repository is archived. As a replacement, n8n recommends installation via npm.

Which Node.js version do I need for the npm installation?

According to its own documentation, n8n requires a Node.js version between 20.19 and 24.x.

Where does n8n store my workflows in a local installation?

By default in an SQLite database under ~/.n8n/database.sqlite, both for the npm installation and for Docker, though there within the mounted volume.

Can I work directly in production with a local npm or Docker installation?

Technically yes, but n8n explicitly points out that self-hosting requires knowledge in the areas of server and container operation, resource management and security. For permanent operation, it is therefore usually advisable to switch to an external database such as PostgreSQL and make a conscious decision for or against self-hosting.