Output Image HTTP

1 VersionOutput

Encodes each Image as PNG or JPEG and ships it over any subset of three live egress modes — HTTP POST/PUT, binary WebSocket broadcast, or an MJPEG stream — with optional per-frame metadata carried as headers or a paired WebSocket frame.

How it fits

Typical backends

Frames annotated by visualize are POSTed to a webhook as encoded snapshots.

Inbound images from input_image_http are processed and streamed back to browser clients as binary WebSocket previews.

Caveats

I/O contractAn mjpeg entry in transports serves a persistent multipart/x-mixed-replace response per client and does not POST to url; set image_format to jpg for canonical Motion JPEG.
Hard constrainttransports is fixed at startup and accepts only the http, websocket, and mjpeg modes (run together); image_format accepts only png or jpg, with JPEG always dropping alpha and PNG keeping it when preserve_alpha is set.
I/O contractmetadata_keys names the optional variadic inputs that follow the image; an unnamed extra input is exposed under an index-based name and shipped via the configured metadata headers or paired WebSocket frame.
FallbackHTTP delivery is asynchronous with bounded exponential-backoff retries; when the queue fills, fail_on_error decides whether the oldest request is dropped or the call fails. An http entry with an empty url silently skips egress while other transports keep publishing.
State lifetimeOnly url can be changed at runtime; all other keys are captured once at startup.

Versions

2c306d3clatestdefault
Automated release
7/31/2026