RenderPix icon

RenderPix

Convert HTML to pixel-perfect images and capture URL screenshots

Actions3

Render Batch

AI-generated

Summary

Renders every incoming item's HTML to an image in one parallel POST to RenderPix's /v1/batch endpoint, returning one output item per rendered image (or per-item error).

Inputs

  • html (required) — Raw HTML to render. Evaluated per input item, so expressions can build a different image for each item. Inline styles are recommended since external CSS may not load.
  • vars — Key/value pairs used to replace {{key}} placeholders in the HTML. Evaluated per item; entries with an empty key are skipped.
  • width — Viewport width in pixels (default 1280). Read once from the first item and applied to all batch items.
  • height — Viewport height in pixels (default 720). Read once from the first item and applied to all items.
  • format — Output format: PNG (default), JPEG or WebP. Read once from the first item.
  • quality — Compression quality 1–100 (default 90). Shown and sent only for JPEG/WebP.
  • scale — Device pixel ratio: 1×, 2× or 3×. Applies to all items.
  • advancedOptions — Collection with CSS Selector, Full Page and Wait Until. These are displayed for this operation, but the batch request source does not send them, so they have no effect on batch renders.
  • returnAs — How each image is returned: Binary File (default), Base64 String (imageBase64 in JSON), or Data URL (imageUrl in JSON).
  • binaryPropertyName — Binary property name for the image when returning as binary (default 'data').

Output shape

A list of items, one per batch result. Successes have json with success: true, index, format, width, height and duration_ms, plus the image as binary, imageBase64, or imageUrl depending on Return As. Failed renders have json { success: false, index, error }.

Each output is paired to its input item via the result index. Batch size limits per plan: Starter 10 items, Pro/Scale 50. Requires RenderPix API credentials (optional custom baseUrl). If the whole request fails, the node throws, or with Continue On Fail it emits a single error item { success: false, error, statusCode } paired to item 0. Unlike Render HTML, no usageRemaining or renderTime headers are reported.

Examples

Example 1: Generate personalized social cards for a list of users in a single API call

HTML template with {{name}} placeholder; vars key 'name' with value expression {{$json.name}}; width 1200, height 630; format PNG; Return As Binary File.

Example 2: Produce compressed WebP thumbnails and embed them in an HTTP payload

HTML from {{$json.html}}; format WebP, quality 80; scale 2×; Return As Data URL.

Links

Discussion