Edit Image (Resize) Stream Yields Empty Buffer

Questions
1

Describe the problem/error/question

Anytime I change another node (add/remove/re-arrange), the Edit Image (Resize) node breaks on run, rendering an error “Stream yields empty buffer”. The only way I can fix this is to fully remove the node and add it back.

Possible red herring but it’s frustrating regardless is when I test run the Edit Image node, it always seems to re-run upstream nodes even if the data is pinned. It seems more like a UI issue than an actual problem, but it could be related.

Note the expectation for the Edit Image (Resize) is to resize the image along the horizontal dimension, maintaining aspect ration, converting it from a png to jpeg @ 60% quality.

Note I have confirmed the docker container contains the graphicsmagick package.

What is the error message (if any)?

Problem in node ‘Edit Image’ – Stream yields empty buffer

Please share your workflow

Information on your n8n setup

instance information

Debug info

core

  • n8nVersion: 1.100.1
  • platform: docker (self-hosted)
  • nodeJsVersion: 22.16.0
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/137.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2025-07-03T13:31:21.653Z

Note I’m running the n8n docker container in the cloud.

2

Got same problem. Removing it and adding it back doesn’t work for me. The exact same workflow has worked well for weeks before I changed an irrelevant node and it broke down. Really frustrating.

3

This topic has still not been addressed.

4

Solved it by reinstalling graphicsmagick

5

I’m running on a docker container and rebuild for each image update (thus graphicsmagick is a fresh install each time). This issue still persists.

6

This start to happen to me, turns out it was lack of memory ram because the input image was bigger than the one that I use for testing.

7

Check if you have installed GraphicsMagick

gm version

If there is no output for that, you need to install it. (had the same issue with LXC version of N8N)

apt-get update && apt-get install -y graphicsmagick

Then just restart n8n.

systemctl restart n8n

pm2 restart n8n

docker restart n8n

Steps might differ from LXC 2 Docker, so just ask AI for the solution.

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.