Getting started
Rules Engine Widgets
Base64 → Image
7 min
overview the base64 → image node converts base64‑encoded image data into a usable image output (such as a file or data url) use it when an upstream service returns an image as a base64 string and you need a real image object for download, display, or storage when to use use this node when an api or ai model returns an image in base64 format you want to display an image in a ui, save it to storage, or pass a file to another node you need to standardize format (e g , always convert to png or jpeg) you are post processing generated images before uploading them (e g , to cloud storage or social platforms) node configuration 1\ base64 input field base64 input (top input field) bind this to the base64 string from a previous node, e g {{ nodes generateimage data image base64 }} you can use a single base64 string, or an array element if you’re processing arrays (see array processing below) ensure the string is pure base64 or a standard data uri; invalid/partial data will cause conversion errors 2\ format field format (dropdown) choose the output image format common options png , jpeg/jpg , etc (options depend on workspace version) this controls how the decoded image is encoded internally use png for lossless images or transparent backgrounds; use jpeg for photos where smaller file size is preferred 3\ output type field output (dropdown – e g , data url) defines how the converted image is exposed to downstream nodes data url – returns a data\ image/ ;base64, url suitable for direct embedding in html/json (if your workspace offers other options like file object , binary , or buffer , pick the one expected by the next node, such as storage or upload nodes ) choose the output type that best matches how you plan to use the image (embed vs upload vs store) 4\ array processing (optional) section array processing when the base64 input is part of an array , you can process all images – apply the conversion to every element in the input array image index (for arrays) – specify an index to process a single element (e g , 0 for the first image) this is useful if you receive multiple base64 images at once and want to convert them all only care about a specific index in an array of images 5\ description (optional) field description use this to document what this conversion is doing in your scenario (e g , “convert ai generated base64 to png for supabase upload”) how it works (execution flow) the node receives a base64 string (or an array entry) from a previous node it decodes the base64 into raw image data it re encodes the image into the selected format (e g , png) it emits the result in the selected output type (e g , data url or file like object) downstream nodes can then upload the image to storage, attach it in emails or messages, render it in uis or dashboards if the base64 input is invalid or the format is unsupported, the node raises an error and you’ll see details in the run logs step by step usage add the node drag base64 → image from utility → data conversion into your scenario bind base64 input in the base64 input field, map the base64 string coming from your upstream node choose output format set format to png , jpeg , or your preferred type select output type choose data url or another output mode that matches your downstream node’s expectations (optional) configure array processing if your input is an array, decide whether to process all images or a specific index run and connect outputs execute the scenario and inspect the output pass the resulting image data to storage/upload nodes, or to any node that accepts image input