Skip to content
Octo × Actions and batch PT Request an assessment

Octo for actions and batch processing in Photoshop

Six hundred photos, one reviewed action, no file overwritten. The one who releases the batch is you.

Photoshop processes whole folders with recorded actions, through Batch, droplets, the Image Processor and variables. Octo inventories the actions, writes the output profiles and the naming pattern, calls the action from a script with several outputs without overwriting anything and checks the folder by content. The photo, the retouching and the release stay with people.

Current version27.11September 2026 update, according to Adobe's help
Actions per cloud request10in the Photoshop API, according to the documentation
Documented command linenonein the pages read; the batch runs with Photoshop open
Sources15listed at the end of the page
01

What Octo does with your batch.

Six possible deliverables, drawn from the research. None of them saves over the original, all of them check the result by content, and all of them go to review by whoever answers for the image.

Action sheet

Each action opened step by step: dialog turned on, recorded path, a plugin found on a single workstation, owner and review date. Actions without an owner are retired.

Deliverable: ficha_acoes.csv reviewed with the retouching team

Versioned output profiles

Web, catalog and print, with long side, quality, ICC profile and file size range. The script and the check read the same file.

Deliverable: perfis_saida.json with history

A script that calls the action

The action does the retouching; the script decides name, destination and sizes, closes the original without saving and logs each file.

Deliverable: processar_lote.jsx and registro_lote.csv

Pieces from a spreadsheet

Variables in the template and a data set checked before import: column names, quotes in the price, photo path, file name.

Deliverable: lote_variaveis.csv, checked

Checks by content

JPEG, PNG, TIFF and PSD dimensions, embedded ICC profile, file size, naming pattern, what is missing and what is extra.

Deliverable: conferencia.csv and a manifest with sha256

Source left untouched

The input folder is read-only; the queue works on copies with sha256, in parts that redo themselves.

Deliverable: fila_lote.sh and fila.csv
02

Eight arms, one checked batch.

The same Octo cycle, applied to actions and batch processing. Each arm has a narrow role; the ones who approve the image, the action and the delivery are people.

  1. Discovery

    Surveys what already runs

    Which batches go out every week, with which actions, on which Photoshop version and on how many workstations.

  2. Data

    Writes the sheet, profiles and spreadsheets

    Action sheet, output profiles, naming pattern and data sets in versioned files.

  3. Security

    Protects the source and the data

    Read-only input, separate output, nothing overwritten, photos of people and spreadsheets with names flagged (LGPD, Brazil's data protection law).

  4. Architecture

    Chooses the path

    Batch, droplet, Image Processor, variables, script or cloud, depending on the task and the volume.

  5. Development

    Writes the script, queue and check

    A script that calls the action, a queue for the input folder and the check, with the source of each rule noted.

  6. Review

    Checks by content

    Dimensions, ICC profile, file size, names, missing and extra files. "The batch finished" is not a check.

  7. Release

    Prepares the delivery

    Checked folder and manifest. Delivery to the e-commerce site or the client is approved by a person.

  8. Documentation

    Records what applies to your environment

    Actions and versions, profiles, who approved each batch and what changed from one version of the action to the next.

Octo closes the original without saving and does not overwrite files. It does not approve photos, does not change actions without review and does not hold anyone's license.

03

Every task, its own path.

The criteria Octo uses to choose, with the documented limit of each path.

TaskPathNotes
Same action on a folder, one destinationBatchAction with no dialogs and no recorded path
Studio input folderDroplet with a queueA droplet keeps the destination from when it was created
JPEG for web and TIFF for archiveImage ProcessorOptions to check in the installed version
Several outputs with the client's namingScript with app.doActionThe script decides name and destination and doesn't overwrite
Series of pieces from a spreadsheetVariables and data setsSpreadsheet checked before import
Turning a reviewed action into code"Copy As JavaScript" and batchPlayDeveloper mode; see the scripts page
Large volume without a workstationPhotoshop API, execute-actionsUp to 10 actions and one image per request
04

From batching by hand to a checked batch.

Three steps. Each one only makes sense after the previous one has shown results on your team.

A proposal, not a promise

1 Today

Sheet and check

Octo opens the actions and checks the folder that already goes out, without changing how you process.

  • Actions with dialogs and recorded paths
  • Missing and extra files against the originals
  • Manifest with sha256
Gain: fewer photos sent back by the e-commerce site
2 Next

Profiles and script

Written profiles, a naming pattern and the script calling the reviewed action with several outputs.

  • Nothing overwritten
  • A log of every file
  • Retoucher present and releasing
Gain: no more renaming by hand
3 Later

Queue and spreadsheets

Input folder in a checked queue and series of pieces from a checked spreadsheet.

  • Parts that redo themselves
  • Data sets with no swapped prices
  • Cloud only for actions already tested
Gain: the day's batch with nobody on watch
05

Confirmed by a source.

Every point below has a source published by the vendor, by the project or by the responsible agency. The sources are in the next section.

7

points with a published source, each with its reference shown alongside.

ConfirmedActions become code through the Actions panel
With developer mode, "Copy As JavaScript" copies the steps as batchPlay calls; commands that change the document run in executeAsModal.Source: developer.adobe.com, batchPlay and executeAsModal
ConfirmedCloud actions have limits
Up to 10 actions per request, one input image, up to 25 outputs, inline ActionJSON up to 50 KB.Source: developer.adobe.com, Photoshop API, Actions Migration
ConfirmedUXP script run from an action
A .psjs script (Photoshop 23.5 or newer) runs from File > Scripts > Browse, by dragging the file or from an action.Source: developer.adobe.com, UXP Scripting in Photoshop
ConfirmedBatch options
Source, destination, names and error logging; "Save and Close" writes over the originals.Source: Adobe help, Batch and droplet processing options (Feb 23, 2026)
ConfirmedDroplets across systems
EXE extension when creating; a Windows droplet is dragged onto the Photoshop icon on macOS to be updated.Source: Adobe help, Create a droplet from an action (Feb 23, 2026)
ConfirmedImage Processor options
JPEG (quality 0 to 12), PSD and TIFF with LZW, resize to fit, sRGB, ICC profile and action; each format in its own subfolder, without overwriting.Source: Adobe help, Convert files with the Image Processor (Feb 23, 2026)
ConfirmedFile name from the spreadsheet
Export generates one PSD per data set, with the base name plus the data set name; the first column can provide the data set name on import.Source: Adobe help, Create data-driven graphics and Import variable data sets (October 2026)
06

What Octo does, and what stays with you.

Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.

Octo prepares

Surveys, calculates, organizes and produces the documents: processed files, proofs, reports and spreadsheets.

Deliverable: material ready to check

Your team checks

The client or the art director checks what Octo delivered before approving. If something doesn't add up, it goes back to Octo with the correction.

Step: checked by the person who approves

Who approves

Octo does not approve the artwork. Artwork carries no legal signature: approval of the artwork and the proof stays with the client or the art director.

Approval: client or art director
07

Sources.

Adobe developer pages (UXP, batchPlay, executeAsModal, manifest, migration, Photoshop API), Photoshop help pages and an Adobe community post, consulted on Oct 31, 2026.

Your Photoshop batch, with a reviewed action and a checked folder.

The assessment starts with the sheet of the actions that already run and a check of an output folder that already exists. You get what is missing, what is extra, what fell outside the profile and the questions only your team can answer, and you decide with that in hand.