Chip in

Several tools, one pass

On a service every step is another upload. Here the files never move.

People do the same thing repeatedly. Every card of photos gets the location stripped, then cropped, then shrunk for the web — three tools, and normally three trips through the site with a download and a re-upload between each. A pipeline is that order saved once and run over a whole folder, with the files staying here between steps.

How it works

  • Choose the tools and the order they run in.
  • Add your files, or a whole folder of them.
  • Each step takes what the last one produced.
  • Save the order and it is one click next time.

Why it is cheap here and not elsewhere

  • The output of each step is already in memory.
  • On a service every step is another upload and download.
  • That cost is why batch chaining is usually a paid feature.
  • Here the work is the only thing that costs anything.

Questions

How do I batch process a folder of images?

Build the order of tools once, add the folder, and run it. Each file goes through every step in turn, and the results come back together or as a zip.

What if a step cannot handle what the last one made?

It stops and says which step and why — "step 2, Compress Video, cannot take .png" — rather than failing vaguely partway through a folder. Converting to a format the next tool accepts is usually the fix.

Can a step produce more than one file?

Yes, and everything after it runs over all of them. Splitting a video into parts and then compressing each is a single pipeline.

Are my pipelines saved anywhere I do not control?

They are stored in your browser, on your device, the same as your other settings. Clearing your browser data removes them, and nothing is sent anywhere.