Dear community,
Describe the problem/error/question
In the Edit Image node, the resize output for image size is still showing the original file size (Schema, json, table), although the binary data (binary) show a compressed version - lower file size.
Please share your workflow
On-form submission > Edit image Node
Share the output returned by the last node
Information on your n8n setup
- n8n version: 1.92.2
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
- Operating system: Mac OS Version 15.4.1
That does seem a little confusing, but the schema view is showing the data structure instead of the actual execution data details. The editor could be improved to show the correct details in the schema view, but the workflow should still function properly, and you can see the actual details in the “binary” tab, so it probably wouldn’t be very high priority. If you want to formally report this as a bug, you might ask @Jon whether he wants to use this post as a reference or if he’d prefer a bug report/issue on the Github project.
1 Like
Hi my apology, I totally forgot the post. So sorry.
So reason I use resize is to downsize the image before being processed by Gemini to save on the input token cost. However, Gemini return the input token count lower but not the expected lowered cost per image based on the resizing node. And in some case it, Gemini token count is larger than the original size.
You might want to follow this post. It appears to be reporting the same Gemini-token-usage issue you just described.
1 Like
I see. Thank you for your time. My apology again for missing out your comment for so long. Sorry.
