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.
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.
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.
