How to route by file format

PixelFiddler lets you build automation workflows that split images into separate processing paths. You can route images based on their file format (JPG, PNG, WebP) or broadcast a single image to multiple paths at once. This is especially useful when you sell on several platforms that each require different image specs.

This guide covers two router nodes: the File Format Router and the Broadcast Router.

File Format Router

The File Format Router inspects the format of each incoming image and sends it down a specific path based on that format. A JPG goes one way, a PNG goes another, and so on.

When to use it

Use the File Format Router when you need different processing for different file types. Common scenarios include:

• Converting JPGs to WebP for faster page loads while keeping PNGs intact for transparency
• Applying stronger compression to photo formats but preserving lossless quality for graphics
• Skipping certain formats entirely so they are not processed

How to set it up

Step 1: Add the router node

Open your automation workflow and drag a File Format Router node onto the canvas. Place it directly after your trigger node (for example, after an upload trigger or a folder watch trigger).

Step 2: Connect downstream nodes

Add the processing nodes you need — for example, two separate Transform Image nodes. Draw a connection from the File Format Router to each one.

Step 3: Assign formats to each connection

Click the File Format Router node to open its properties panel. You will see a list of your outgoing connections. Assign a file format to each one:

• Connection 1 — JPG: routes to a node that converts to WebP at high quality
• Connection 2 — PNG: routes to a node that resizes while preserving transparency

Tip

You can add as many connections as you need. If you sell products with a mix of photography (JPG) and graphics with transparent backgrounds (PNG), this setup lets you handle each type with the right settings automatically.

Step 4: Handle unmatched formats

Any image whose format does not match one of your assigned connections is dropped. It will not be processed or passed along. This is by design — it keeps your workflow clean and predictable.

Caution

If you upload a WebP file but have only configured paths for JPG and PNG, that WebP file will be skipped entirely. Make sure you add a connection for every format you expect to receive, or consider using the Broadcast Router instead if format does not matter.

Example: JPGs to WebP, PNGs resized with transparency

Imagine you run an online store that receives product photos as JPGs and logo overlays as PNGs. Here is how you would set up the File Format Router:

1. Trigger node watches your upload folder
2. File Format Router splits the incoming files
3. Path A (JPG): A Transform Image node converts the photo to WebP at quality 85 and resizes to 1200px wide — perfect for fast-loading product pages
4. Path B (PNG): A Transform Image node resizes the graphic to 800px wide while keeping the transparent background intact

The result: every image gets the treatment it needs without any manual sorting on your part.

Broadcast Router

The Broadcast Router works differently. Instead of inspecting the file format, it sends a copy of every incoming image to all connected paths at the same time. Every path runs independently.

When to use it

Use the Broadcast Router when you want multiple output versions from a single upload. This is ideal for sellers who list on several marketplaces, each with its own image requirements.

How to set it up

Step 1: Add the router node

Drag a Broadcast Router node onto your workflow canvas and connect it after your trigger.

Step 2: Connect multiple downstream nodes

Add a processing node for each output version you need. Connect the Broadcast Router to all of them.

Step 3: Label each connection

Click each connection line and give it a descriptive label. This makes your workflow easy to read at a glance:

• “Amazon” — resize to 2000x2000
• “Shopify” — resize to 1024x1024
• “Instagram” — resize to 1080x1080

Step 4: Configure each path

Click each downstream Transform Image node and set the dimensions, format, and quality that the target platform requires. Each path processes independently, so the settings on one path do not affect the others.

Note

Every path receives a fresh copy of the original image. The processing on one path (like heavy compression for Instagram) does not degrade the image on another path (like the high-resolution version for Amazon).

Example: One upload, three marketplace-ready images

You photograph a product once and upload it to PixelFiddler. The Broadcast Router takes care of the rest:

1. Trigger node detects the new upload
2. Broadcast Router sends the image to three paths simultaneously
3. Path A (Amazon): Resize to 2000x2000, convert to JPEG at quality 90
4. Path B (Shopify): Resize to 1024x1024, convert to WebP at quality 85
5. Path C (Instagram): Resize to 1080x1080, convert to JPEG at quality 80

One upload, three platform-ready images — no manual resizing, no switching between tools.

Tip

You can combine the Broadcast Router with a File Format Router downstream. For example, broadcast to two paths, then use a File Format Router on one of those paths to handle JPGs and PNGs differently within that branch.

Comparing the two routers

	File Format Router	Broadcast Router
Routes based on	Input file format	Sends to all paths
Each image goes to	One matching path	All paths simultaneously
Unmatched files	Dropped (not processed)	Not applicable — all files pass through
Best for	Different processing per format	Multiple output versions from one input
Typical use case	JPGs converted to WebP, PNGs keep transparency	One photo resized for Amazon, Shopify, and Instagram

Which one should I pick?

• Choose the File Format Router if your images arrive in mixed formats and each format needs its own treatment. For example, you want to compress photos aggressively but leave transparent graphics untouched.
• Choose the Broadcast Router if every image needs to be turned into several versions regardless of its format. For example, you need a large version for your website, a medium version for your marketplace listing, and a square crop for social media.
• Use both together when you need to create multiple versions and each version needs format-aware handling. Place the Broadcast Router first to split into paths, then add a File Format Router inside any path that requires format-specific logic.

Next steps

Now that you know how to route images through your workflow, explore these related guides:

Save to Storage Learn how to save processed images back to your storage

Operations reference See all available processing operations for your workflow nodes

Resize on upload Automatically resize images the moment they are uploaded