How to save to storage

Every workflow in PixelFiddler needs a destination for its processed images. The Save to Storage node defines where your finished images end up — whether that is a single folder, multiple folders, or entirely different storage locations. This guide walks you through configuring one or more save destinations so your images land exactly where you need them.

What the Save to Storage node does

The Save to Storage node takes processed images from your workflow and writes them to a storage location of your choice. Think of it as the final stop in your image processing pipeline — it is always the last node in a workflow branch, meaning nothing comes after it.

Every workflow requires at least one Save to Storage node. Without it, your processed images have nowhere to go and the workflow cannot run.

Note

The Save to Storage node is a terminal node. It cannot have any outgoing connections. If you need to send images to multiple places, you will use multiple Save to Storage nodes (more on that below).

Configuring a Save to Storage node

When you add a Save to Storage node to your workflow, there are three settings to configure.

1. Target storage

Choose which storage location your processed images should be saved to. This can be any storage connected to your PixelFiddler space — it does not have to be the same storage your workflow watches for new uploads.

For example, you might watch an S3 bucket called “raw-uploads” for new images but save the processed results to a hosted storage called “production-images.”

2. Filename template

Set the output filename for each processed image. You have full control over naming.

• Keep the original name — Use {orig_name} to preserve the filename from the source image
• Add a suffix — Use {orig_name}-processed or {orig_name}-amazon to distinguish processed files from originals
• Use a custom name — Type any name you want, though this works best when processing one image at a time

Here are a few practical examples:

Template	Original file	Output file
{orig_name}	summer-dress.jpg	summer-dress.jpg
{orig_name}-processed	summer-dress.jpg	summer-dress-processed.jpg
{orig_name}-2000x2000	summer-dress.jpg	summer-dress-2000x2000.jpg
{orig_name}-amazon	summer-dress.jpg	summer-dress-amazon.jpg

Tip

Include processing details in your filenames. A name like {orig_name}-2000x2000 tells you at a glance what dimensions the image was resized to, making it much easier to manage your files later.

3. Target directory

Optionally specify a folder path within the target storage where the images should be saved.

• Use the folder picker to browse your storage and select an existing directory
• Leave this field empty to save images to the root of the storage

Saving to multiple destinations

This is where workflows get really powerful. You can send the same processed image to several different locations at once — different folders, different storage locations, or both.

How it works

To save to multiple destinations, place a Broadcast Router node before your Save to Storage nodes. The Broadcast Router duplicates the image stream and sends it down every connected path simultaneously.

Here is what the setup looks like:

1. Your processing nodes (resize, format, etc.) feed into a Broadcast Router
2. The Broadcast Router connects to two or more Save to Storage nodes
3. Each Save to Storage node is configured with its own target storage, filename template, and directory

Example: saving for Amazon and Shopify

Suppose you sell on both Amazon and Shopify, and each marketplace has different image requirements. After processing your product photos, you want copies in two separate folders.

Set up your workflow like this:

1. Add a Broadcast Router after your processing nodes
2. Connect it to two Save to Storage nodes
3. Configure the first Save to Storage:
   • Target storage — your production storage
   • Filename template — {orig_name}-amazon
   • Target directory — amazon-ready
4. Configure the second Save to Storage:
   • Target storage — your production storage (or a different storage entirely)
   • Filename template — {orig_name}-shopify
   • Target directory — shopify-ready

Now every image that passes through your workflow is automatically saved to both locations with marketplace-specific filenames.

Tip

You are not limited to two destinations. Add as many Save to Storage nodes after the Broadcast Router as you need — one for each marketplace, team, or campaign.

Common use cases

Separate raw files from processed files

Keep your original uploads in one storage and save processed images to a different storage or folder. This prevents accidental overwrites and makes it clear which images are ready to use.

Organize by marketplace

If you sell on Amazon, Shopify, eBay, and Etsy, create a separate output folder for each. Each Save to Storage node can use a marketplace-specific directory like amazon-ready, shopify-ready, or etsy-ready.

Route to different teams

Save images to different storage locations based on who needs them. Marketing gets a copy in their storage, the web team gets a copy in theirs, and the print team gets a copy in a third location.

Campaign-based organization

When running seasonal campaigns or promotions, use the target directory to keep images organized — for example, spring-2026/processed or black-friday/hero-images.

Best practices

Naming and organization tips

• Use descriptive directory names — Names like processed, amazon-ready, or 2000x2000-white-bg tell you exactly what is inside without opening the folder
• Include processing info in filenames — Templates like {orig_name}-2000x2000 or {orig_name}-webp help you identify files at a glance
• Keep raw files separate from processed files — Store originals and outputs in different storage locations or directories so you always have clean originals to fall back on
• Be consistent across workflows — Adopt a naming convention and stick with it across all your workflows so your team always knows where to find things

Caution

If you save processed images to the same storage and directory that your workflow watches, you may trigger an infinite loop — the workflow detects the newly saved image as a new upload and processes it again. Always save to a different location than the one your workflow monitors.

Next steps

Now that you know how to control where your processed images are saved, explore these related topics:

• Format-based routing — Route images to different processing paths based on their file format
• Execution history — Monitor your workflow runs and troubleshoot any issues
• Operations reference — See all the image processing operations available in your workflows