Simple Web Browser:
WebViewerNode loads an image from a web address or a file in the application's temporary directory and prepares it for use in an image workflow. It converts the image to RGB, placing transparent areas over black, and separately retains the image's alpha channel. This lets you use the visible image and its transparency information in later steps. If no image is specified or loading fails, the node returns small empty placeholders instead of a loaded image.
Simple Web Browser Input Parameters:
unique_id
A hidden identifier supplied by the application to identify this node instance. You do not normally set it yourself. The source does not use its value when loading or converting the image. No default, minimum, maximum, or selectable options are specified.
image_url
A hidden text value that tells the node which image to load. An address beginning with http:// or https:// is downloaded; any other value is treated as a filename, with only its final filename component used to look for a file in the application's temporary directory. The default is an empty string. If the value is empty or contains only spaces, the node returns placeholder outputs. The source specifies no minimum or maximum text length and no selectable options. Because this input is hidden, how you supply or change it depends on the surrounding workflow or interface.
Simple Web Browser Output Parameters:
image
The loaded image as an RGB image output, with color values scaled between 0 and 1. Transparent and partly transparent pixels are blended against black, so transparent areas appear black in this output. The output retains the loaded image's dimensions. If the source is blank or loading fails, the node instead returns a 1 × 1 black placeholder image.
mask
The loaded image's alpha channel as a single-channel mask, with values from 0 to 1: 0 means fully transparent, 1 means fully opaque, and values between them represent partial transparency. This is the source image's opacity information, so check what a downstream node expects before using it as an editing mask. If the source is blank or loading fails, the node returns a 1 × 1 mask filled with 0.
Simple Web Browser Usage Tips:
- Supply a direct image address beginning with
http://orhttps://when loading from the web. The node makes one download request with a 30-second timeout; an address for a webpage may not contain an image the node can open. - For a temporary file, make sure the image is already in the application's temporary directory. The node uses only the final filename component of the supplied value; it does not load an arbitrary local path.
- Use an image with transparency when you need meaningful variation in
mask. For an image without transparency, converting it to RGBA produces a fully opaque mask. - Check both outputs after changing the source. A blank value or a caught loading error produces 1 × 1 placeholders, which can be easy to mistake for a valid but tiny image.
- Keep the image at a practical resolution for your workflow. The node loads the full image and creates separate image and mask arrays; the source provides no resizing setting.
Simple Web Browser Common Errors and Solutions:
WebBrowser Node: Failed to load image. Error: File not found in temp directory: ...
- Explanation: The supplied value did not begin with
http://orhttps://, and the node could not find its final filename component in the application's temporary directory. - Solution: Put the image in that temporary directory and supply its filename, or provide a direct
http://orhttps://image address. A path to a file elsewhere will not make the node load it from that location.
WebBrowser Node: Failed to load image. Error: ...
- Explanation: This is the node's general loading-error message. The text after
Error:gives the underlying reason, such as a download failure, HTTP error, inaccessible file, or content that the image library cannot open. The node returns placeholder outputs for these failures. - Solution: Read the detail after
Error:. Confirm that the address or temporary file exists, is accessible, and contains an image the application can open.
HTTP error, such as 404 Not Found or 403 Forbidden
- Explanation: A web server refused the request or did not have the requested resource. The node raises an error for unsuccessful HTTP responses and reports it through its general loading-error message.
- Solution: Open the address independently to confirm it points directly to an accessible image. Correct an outdated address or use an image source that permits the request.
Request timed out
- Explanation: The image download did not finish within the node's 30-second request timeout. The node reports the request error and returns placeholders.
- Solution: Check the connection and image address, then try a reachable source or a file already placed in the temporary directory.
Image cannot be identified or opened
- Explanation: The downloaded content or temporary file was not recognized as an image by the image library. For example, an address may have returned an HTML page rather than image data.
- Solution: Check that the source contains a valid image and that a web address points to the image itself, not a page displaying it.
No error message, but the outputs are 1 × 1
- Explanation: An empty or whitespace-only
image_urlreturns placeholders without attempting to load an image. Caught loading errors also return 1 × 1 placeholders, but print an error message. - Solution: Confirm that the hidden
image_urlvalue is populated by your workflow, then check the application log for a loading-error message.
