Workflow Design • Visual Programming • Batch Processing

Node-Based Workflows: Visual Programming for Batch Image Processing

Last Updated: November 27, 2025

FlowBatch uses a node-based interface for building batch image processing workflows. Instead of configuring a linear sequence of operations, you visually connect processing nodes to create flexible pipelines that can branch, filter, and output to multiple destinations.

What Are Node-Based Workflows?

A node-based workflow is a visual representation of a processing pipeline. Each operation is a "node" that you place on a canvas, and you connect nodes with edges to define how data flows through the system.

Example: A Simple Resize Workflow

[Input Folder] → [Resize to 1920x1080] → [Output Folder]

This approach is common in professional media software: Blender uses it for compositing and geometry, Unreal Engine uses it for materials and blueprints, and DaVinci Resolve uses it for color grading. FlowBatch applies the same paradigm to batch image processing.

Available Node Types

FlowBatch provides these node types for building workflows:

Input Node

Defines where files come from. Configure the source folder, whether to include subfolders, and filter by file type (images, videos, or custom extensions).

Resize Node

Changes image dimensions. Options include: exact dimensions, fit to width, fit to height, percentage scaling. Supports multiple algorithms (Lanczos, Bicubic, etc.) and background color for letterboxing.

Convert Node

Changes file format and compression. Supports JPG, PNG, WebP, and more. Configure quality level (1-100%) and whether to strip metadata.

Filter Node

Routes files based on conditions. Filter by file extension, file size, image dimensions, or filename patterns. Has two outputs: files that match go one way, files that don't match go another.

Watermark Node

Adds text overlays to images. Configure text content, position, font size, color, and opacity.

Output Node

Defines where processed files are saved. Configure destination folder, file naming patterns, and how to handle filename conflicts.

Why Use a Node-Based Interface?

Branching: One Input, Multiple Outputs

Traditional batch processors run a fixed sequence on every file. Node-based workflows allow one input to branch into multiple processing paths, each with different settings.

Example: Social Media Multi-Format

[Input] ─┬→ [Resize 1080×1920] → [Output TikTok]
         ├→ [Resize 1080×1080] → [Output Instagram]
         └→ [Resize 1920×1080] → [Output YouTube]

One input folder produces three different output formats in a single run. With traditional tools, you would need to run the batch three times with different settings.

Conditional Logic: Different Processing for Different Files

The Filter node enables conditional routing based on file properties. Files matching the condition go one way; files that don't match go another.

Example: Process Only HEIC Files

[Input] → [Filter: extension = heic] ─┬→ (pass) → [Convert to JPG] → [Output]
                                      └→ (fail) → (not processed)

This is how the HEIC to JPG preset works: it filters for HEIC files and only converts those, leaving other file types untouched.

Visual Understanding

Node graphs are self-documenting. You can look at a workflow and immediately understand what it does, how data flows, and where outputs go. This makes complex workflows easier to build, debug, and share.

Text-based configuration:

Resize to 1920x1080, then convert to WebP at 85%, but also create a 400px thumbnail as JPG, unless the file is larger than 10MB, in which case...

Node-based:

Visual graph shows exactly what happens at each step and where branches occur.

Workflow Examples

Web Responsive Images

Generate multiple image sizes for responsive web design:

[Input] → [Convert to WebP] ─┬→ [Resize 400px] → [Output _sm.webp]
                             ├→ [Resize 800px] → [Output _md.webp]
                             └→ [Resize 1200px] → [Output _lg.webp]

Thumbnail Generation

Create small preview images with optimized file size:

[Input (recursive)] → [Resize 640×360] → [Convert to JPG 75%] → [Output _thumb.jpg]

Client Proofing with Watermark

Resize photos and add a watermark for client review:

[Input] → [Resize 2000px width] → [Watermark "PROOF"] → [Output]

Factory Presets vs Custom Workflows

FlowBatch includes factory presets for common workflows. These are pre-built node graphs that you can use immediately:

  • HEIC to JPG: Converts iPhone photos to universal JPG format
  • Social Media Multi-Format: Exports to TikTok, Instagram, and YouTube sizes
  • Web Responsive Images: Generates small/medium/large WebP variants
  • Thumbnail Generator: Creates 640x360 preview images

You can also build custom workflows by dragging nodes onto the canvas and connecting them. In the free version, you can create and use custom workflows during a session. The licensed version adds the ability to save custom workflows as presets for reuse.

Free vs Licensed

Free Version

  • Full node-based editor
  • All node types available
  • All factory presets
  • Unlimited batch processing
  • Create custom workflows (session only)

Licensed Version

  • +Everything in Free
  • +Save custom presets
  • +Watch Mode (auto-process new files)
  • +Priority support

Summary

The node-based workflow editor is FlowBatch's core interface. It provides:

  • • Visual representation of processing pipelines
  • • Branching to create multiple outputs from one input
  • • Conditional logic with filter nodes
  • • Factory presets for common tasks
  • • Flexibility to build custom workflows

For simple tasks, load a factory preset and go. For complex requirements, build a custom workflow by connecting nodes on the canvas.

Keywords: node-based workflow, visual batch processing, image processing pipeline, batch image editor, visual programming, workflow automation, image resize batch, format conversion, conditional image processing