selfhostlabmeasured on a real VPS, not copied from docs

n8n self-hosted requirements, measured

n8n 2.35.7 · Node.js 22.22.2 · SQLite · tests run 19 and 20 Nov 2026 · published 20 Nov 2026

Short answer. n8n used 555 to 850 MB of RAM at idle and peaked at 780 MB while it answered 1,000 webhook calls. A 1 GB server will swap or crash. 2 GB works for one person and light workflows. 4 GB leaves room for PostgreSQL, a reverse proxy and growth.
See 4 GB / 8 GB VPS prices (Hostinger) →

Most guides repeat a minimum (often "1 vCPU, 2 GB RAM") without showing where it comes from. We installed n8n on a VPS, started it, sent it real executions and read the memory of every n8n process. Here are the numbers, how we got them and what server size they point to.

What we measured

The test server is a Contabo Cloud VPS with 8 AMD EPYC vCPU and 23 GB of RAM, so memory was never constrained: the figures below are what n8n asks for, not what it squeezes into. We installed n8n with npm install n8n (no Docker), kept the default SQLite database and the default task runner (the separate process that executes Code nodes), and summed the resident memory (RSS) of the main process and the runner with ps, sampled every 0.3 s.

SituationExecutionsThroughputLatency p50 / p95RAM (main + runner)
Idle, 32 s after first start (19 Nov)0n/an/a712 + 137 = 849 MB
Idle, 37 s after start (20 Nov)0n/an/a418 + 137 = 555 MB
Webhook + Code, one at a time10013.5 /s82 / 141 mspeak 656 MB
Webhook + Code, 10 in parallel1,00026.5 /s351 / 565 mspeak 780 MB, 687 MB after
Heavy Code node (5M-step loop), 10 in parallel20033.1 /s298 / 378 mspeak 763 MB

Zero failed requests across 1,310 executions. The 19 Nov first start includes database migrations, which explains the higher idle figure. The npm exec wrapper (74 MB) is not counted because n8n start launched directly does not need it.

1 GB server (before OS) 2 GB server 849 MBidle, 1st 555 MBidle 656 MB100 seq. 780 MB1,000 x10 763 MBheavy x10
Peak RSS of n8n (main process + task runner) in each test, drawn to scale against 1 GB and 2 GB of RAM. Our measurements, 19 and 20 Nov 2026.

Which server size, then?

Add roughly 200 to 300 MB for a minimal Linux system, and more for anything else you run next to n8n (Caddy or Nginx, PostgreSQL, Redis for queue mode). That gives:

RAMVerdict from our numbersExample plan (Hostinger, price read 20 Nov 2026)
1 GBNo. n8n alone reaches 780 MB under load, and 850 MB on a first start.not offered on Hostinger VPS
2 GBPossible for one user, SQLite, light workflows. Add swap. Little room for a database.not offered on Hostinger VPS
4 GBComfortable: n8n + PostgreSQL + reverse proxy, with about 2.5 GB of headroom.KVM 1: 1 vCPU, 4 GB, 50 GB NVMe, $6.49/mo on 24 months ($155.76 paid upfront), renews $11.99/mo
8 GBQueue mode with workers, many parallel runs, or n8n next to other self-hosted apps.KVM 2: 2 vCPU, 8 GB, 100 GB NVMe, $8.79/mo on 24 months ($210.96), renews $14.99/mo

Compare KVM 1 and KVM 2 on Hostinger →

Prices are the ones shown on hostinger.com/vps-hosting on 20 Nov 2026 for a 24-month term, before tax. They change often: check the order page before paying. This link is an affiliate link: if you buy, we may earn a commission at no extra cost to you. It does not change the numbers above, which come from our own server.

For 8 GB on a smaller bill, Contabo lists Cloud VPS 4 (4 vCPU, 8 GB RAM, 100 GB SSD) at 4.40 EUR/month "for the first 24 months" (5.50 EUR list price), read on contabo.com/en/vps on 17 Nov 2026. Contabo does not publish the price after the 24 months on that page. Our own measurements were taken on a Contabo Cloud VPS, a larger plan than this one, so the RAM figures above apply to any provider.

See Contabo Cloud VPS plans →

Contabo link is also an affiliate link, same terms as above.

Weighing Cloud against a VPS? Our calculator turns your monthly executions into the n8n Cloud plan you would need and the 4-year VPS cost, renewal price included.

CPU: is one vCPU enough?

For webhook-style workflows, n8n is not CPU bound. Even the test with a 5-million-step loop in a Code node kept p95 latency under 400 ms with 10 runs in parallel. Our server had 8 vCPU, so a 1 vCPU plan will be slower under parallel load: we have not measured it yet and will not guess a figure. If you expect bursts of parallel executions or heavy Code nodes, 2 vCPU is the safer choice.

Disk space

The npm install pulled 2,266 packages and took 2.9 GB on disk (3 min 20 s with a warm npm cache, 5 min 43 s without). After about 1,310 executions the SQLite database was 7.6 MB plus a 4 MB write-ahead log, so about 9 KB per execution of this small workflow. Workflows that move files or large JSON store much more per run. Self-hosted n8n prunes old executions by default, so 20 GB of disk is enough for a single-user setup that does not keep binary data.

How to reproduce this test

npm install n8n@2.35.7
N8N_PORT=5799 npx n8n import:workflow --input=wf.json   (download wf.json)
N8N_PORT=5799 npx n8n start
# then, in another shell, sample memory every 0.3 s:
ps -eo rss,args | grep -E 'n8n start|disallow-code-generation'

The workflow is a Webhook node (POST, respond with the last node) followed by a Code node that sums the integers up to n. Load was sent from the same server with 1 or 10 Python threads (script and raw CSV on GitHub), so network latency is not included.

Limits of this test

FAQ

Can n8n run on a 1 GB VPS?
Not reliably. n8n alone used 555 to 850 MB at idle and 780 MB at peak in our test, before the operating system and anything else. 2 GB is the practical floor.
How much RAM does n8n need?
Plan 2 GB for light personal use with SQLite, 4 GB if you add PostgreSQL and a reverse proxy, 8 GB for queue mode or several apps on the same server.
Is n8n CPU intensive?
Not for simple workflows: 13.5 executions per second one at a time, 26.5 per second with 10 in parallel, no errors. Heavy Code nodes and parallel bursts are what use CPU.
How much disk space does self-hosted n8n need?
2.9 GB for the install, plus about 9 KB per small execution in SQLite. 20 GB is enough for most single-user setups.