How to Batch Recolor Images (Without Opening Each One)

A rebrand lands, or a dark mode ships, and suddenly forty icons need the same colour change. Doing it by hand is not hard — it is just forty repetitions of something boring, with forty chances to paste a slightly different hex.

There are three real ways to do it in bulk. Which one is right depends less on your technical comfort than on what kind of colour change you need, so that is worth settling first.

Not every recolor can be batched

This is the part most guides skip, and it is the reason batch jobs go wrong.

A batch applies one instruction to many different files. That works only if the instruction means the same thing for every file. Three kinds do:

• Recolour everything to one colour. "Make all of these white" is unambiguous regardless of what each file currently looks like. This is the safest batch operation and the most common.
• Swap one named colour for another. "Find #E63946 and replace it with #0066FF" is well-defined because you specified the source colour rather than asking the tool to work it out.
• Shift the hue. "Rotate every colour 40 degrees" applies uniformly, and because it preserves shading it is the one that works on photographs.

What does not batch is anything that depends on the individual image: "replace the dominant colour", "change the background colour", "recolour the second-largest region". The dominant colour in file A is not the dominant colour in file B, so the same instruction quietly does something different — or nothing — to each one, and you will not notice until you inspect all forty.

Option 1: a browser batch tool

The lowest-friction route if you are not already living in Photoshop or a terminal.

Our batch recolor tool takes up to 30 files at once, applies one of the three recipes above to all of them, and returns a ZIP with your original filenames intact.

1. Drop in your files

   Up to 30 PNG, JPG, WebP or SVG files. Everything runs on your own machine in the browser — nothing is uploaded — so a folder of unreleased client logos stays where it is.

2. Set one recipe

   Choose recolour, swap or hue shift, then set the colour. Click any thumbnail to see that specific file before and after, which is how you catch a recipe that works on flat logos but ruins the one photograph you forgot was in the folder.

3. Apply to all

   Run it across the set. A file that cannot be processed — a corrupt PNG, something enormous — is marked with the reason and skipped; the other 29 finish normally.

4. Check the free preview, then download

   The preview ZIP contains every result at low resolution and costs nothing. Checking thirty thumbnails takes a moment and is the only reliable way to catch a recipe that misfired on a few files before you pay for the full-resolution archive.

Two details worth knowing. SVG files stay vector (and it is worth keeping them that way) under the recolour-to-one-colour recipe — the fill and stroke values are rewritten inside the file — but the hue and swap recipes work on pixels, so an SVG through those comes back as a PNG. The tool labels which files that applies to before you download. And you are only charged for files that produced a result; skipped and failed files are free and listed in a _skipped.txt inside the archive.

The 30-file ceiling is a memory limit, not an arbitrary one: the whole batch is held in your browser while it works. For more than that, run it in groups or use one of the options below.

Option 2: a Photoshop action

If you already own Photoshop, this handles unlimited files and any operation Photoshop can do — including ones the browser tool cannot.

1. Record the action

   Open one representative file. Window → Actions → New Action → Record. Perform the recolour (a Hue/Saturation adjustment layer with Colorize, or a Solid Color fill layer clipped to the artwork), then Save As and Close. Stop recording.

2. Run it over the folder

   File → Automate → Batch. Choose your action, the source folder, and a destination folder. Tick “Override Action Open Commands” so it uses each file rather than reopening the one you recorded with.

3. Verify on the whole output

   Open the destination folder in Bridge or a thumbnail view and scan every result. Actions fail silently on files whose layer structure differs from your recording.

The catch is setup time and brittleness: an action recorded against a flattened PNG often misbehaves on a layered PSD. It is worth it for a job you will repeat, less so for a one-off.

Option 3: ImageMagick

For developers, ImageMagick is the most flexible option, and the right one if this needs to happen in CI or on hundreds of files.

# Recolor every PNG to a single brand color, preserving transparency
for f in *.png; do
  magick "$f" -fill '#0066FF' -colorize 100 "recolored/$f"
done

# Swap one specific color for another, with a fuzz tolerance for anti-aliased edges
for f in *.png; do
  magick "$f" -fuzz 20% -fill '#0066FF' -opaque '#E63946' "recolored/$f"
done

# Rotate hue across a set of photographs
for f in *.jpg; do
  magick "$f" -modulate 100,100,140 "recolored/$f"
done

The -fuzz value is the equivalent of the tolerance slider elsewhere, and it matters for the same reason: without it, -opaque matches only pixels that are exactly the source colour and leaves a fringe of near-matches around every edge — the same edge-fringing problem that shows up after a background removal.

ImageMagick's own colour-modification examples are worth reading before you commit to a recipe; mogrify can also replace the shell loops above when you are editing files in place. Free, scriptable, no file limit. The cost is that you are working blind — there is no preview, so run it on a copy and inspect the output before trusting it.

Which to use

• A one-off job of a few dozen files → the browser tool. No setup, and you can see each result.
• A repeating job, and you own Photoshop → an action. Setup pays back on the second run.
• Hundreds of files, or it needs to be automated → ImageMagick.

Before you run any of them

• Work on a copy. All three write new files, but a mistyped destination path has ruined plenty of asset folders.
• Test on the three most different files in the set, not the first three. The odd one out is what breaks a batch.
• Keep the originals. A recolour is not reversible in the way people assume, and you will want the source when the brand colour changes again.
• Check filename collisions. Two files called logo.png from different folders will overwrite each other in a flat output directory unless your tool handles it.