An Action records a sequence; Batch applies it to many files. Reliable automation needs consistent inputs, deterministic steps, and protection against overwriting sources.
Suitable tasks
- Resize and convert profiles across a set.
- Add output sharpening.
- Apply a standard canvas, border, or identification layer.
- Save JPEG or PSD versions to a destination folder.
- Normalize filenames.
Record a stable Action
- Create a clearly named Set and Action.
- Use a representative test file.
- Record menu commands instead of canvas-coordinate clicks where possible.
- Add a Stop only where a manual decision is required.
- Test on copies of several different files.
Batch settings
| Setting | Purpose |
|---|---|
| Set/Action | The sequence to run |
| Source | Folder, open files, Bridge, or another source |
| Destination | Target folder, Save and Close, or None |
| Override Open/Save As | Uses Batch-selected files and destination |
| Errors | Stops or writes a log for later review |
Safety rules
- Never test against the only folder containing originals.
- Separate input and output folders.
- Avoid duplicate filenames and preserve correct extensions.
- Do not suppress profile warnings without a color policy.
- Inspect samples from the beginning, middle, and end.
When to use Image Processor
Image Processor is convenient for JPEG, PSD, or TIFF conversion, dimension limits, and an optional Action. Batch offers more control over sources, destinations, naming, and recorded Open/Save commands.
Automation amplifies correct and incorrect steps alike; a small test set is mandatory.
Practice exercise
Create an Action that converts to sRGB, resizes the long edge to 1600 px, adds gentle sharpening, and saves JPEG. Run it on ten copies and inspect three samples.
No comments yet. Be the first to share your thoughts.