ImageCheveretoUploader

Every render needs to end up somewhere, and for a subset of people "somewhere" is their own self-hosted image host. Chevereto is the PHP/MySQL image-hosting script people run to make their own imgbb - a gallery with uploads, albums, and direct links. ImageCheveretoUploader takes an image from your graph and pushes it to a Chevereto instance via its API, so generated output lands in your gallery without you manually dragging files into a browser.

Let's be upfront about the audience: this node is only useful if you already run (or your team runs) a Chevereto server with an API key. If you don't, the node is dead weight - there are plenty of general-purpose "upload to X" utilities, but this one speaks Chevereto's dialect specifically.

How it works

For each image in the batch, it converts the tensor to a PNG, base64-encodes the bytes, and POSTs key and source as form fields to the url you give it. The endpoint is Chevereto's v1 upload API - typically https://your-host.com/api/1/upload. It then parses the JSON response and returns a JSON string of per-image metadata.

Inputs and outputs

• image (IMAGE) - what to upload. A batch means one HTTP request per image.
• url (STRING) - your Chevereto upload API endpoint. Full URL, including /api/1/upload.
• key (STRING) - your API v1 key, from the Chevereto dashboard.
• Output: STRING - a JSON blob of metadata for each uploaded image: name, extension, size, width, height, date, md5.

Install

It ships in a pack, so install the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/knuknX/ComfyUI-Image-Tools

Restart ComfyUI, or install Image Tools via ComfyUI Manager. It only needs requests and torchvision, both already present.

Where people get burned

• The returned JSON has no image URL in it. This is the quirk to know: the metadata list the node hands you (name, dimensions, md5…) deliberately omits the direct link. The full response - which does contain the URL - only goes to the ComfyUI console log (upload image: ... lines). If you want the shareable link as data, you'll have to grab it from the console or feed the full response through a JSON node yourself.
• Your key is plain text in the workflow. The API key sits in the node, which means it's embedded in the workflow JSON, which gets baked into saved PNGs. Share a workflow image and you've shared your key. Treat it like a password - rotate it if anything leaky ever happens.
• Any URL, no hand-holding. The node posts your key to whatever url you type, so only ever point it at your own host. And if the endpoint is unreachable or the response isn't parseable JSON, the node errors with a traceback - the console is your best witness for what the server actually said.
• Batch = N uploads. A batch of images becomes that many sequential HTTP requests, each its own upload on the Chevereto side. Fine for a handful, chunky for a hundred.

Verdict: a niche but real automation win for people who self-host Chevereto. If that's you, it saves the manual drag-and-drop on every render; if it's not you, this node is the pack's most skippable member.